Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: TCFkas on June 13, 2006, 07:26:16 PM
-
Ok, the latest patch has thrown my FR into freeze hell. I have the NVIDIA GeForce 6200 with 256 meg. I have a Gig of Ram. When I am in clear blue skies FR gets to 71, but if something pops up on screen it drops into 40's and God forbid it smoke as now it drops into 20's. If screen gets real cluttered and drops below 20, standby for freeze up and the only way out is a reboot. I've updated the drivers and nada.
-
What drivers are you using?
-
Downloaded latest off of NVIDIA webiste last week. My NVIDIA folder is showing 66.93, 81.94 and 84.21. So, must be the 84.21 that's loaded now.
-
Ok, that was wrong. Found my NVIDIA folder in Control Panel, says Version 110.26. These came from the 84.21 released on March 17, 2006.
-
Originally posted by TCFkas
Ok, that was wrong. Found my NVIDIA folder in Control Panel, says Version 110.26. These came from the 84.21 released on March 17, 2006.
110.26 is the Nview Desktop version.
84.21 IS the driver version you have.
But you are correct with frame rates going to pot in this release. I'm experiencing the same thing with a 6800xt 512mb vid mem, 1 gig system ram.
Edit: I have no issues with flight frame rate. Mine are all GV related. And I've tried several different drivers. All with the same result. GV battles, especially near forests are not an option for me now. FR drops to 9.
-
Similar problem here. Got my inflight FR problem fixed by updating my nvidia drivers, but in gv battles I still get FRs <10 now. Never had such problems before 2.08. Gforce 6600GT (128MB), 1gig system memory.
-
Same problems here.
Display Devices
---------------
Card name: NVIDIA GeForce FX 5500
Manufacturer: NVIDIA
Chip type: GeForce FX 5500
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0326&SUBSYS_20341682&REV_A1
Display Memory: 256.0 MB
Current Mode: 1024 x 768 (32 bit) (60Hz)
Monitor: SyncMaster 930B(Analog)
Monitor Max Res: 1280,1024
Driver Name: nv4_disp.dll
Driver Version: 6.14.0010.6085 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 12/31/2001 12:04:30, 4130560 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: nv4_mini.sys
Mini VDD Date: 12/31/2001 12:04:30, 2167552 bytes
Device Identifier: {D7B71E3E-4066-11CF-F762-3E0000C2CB35}
Vendor ID: 0x10DE
Device ID: 0x0326
SubSys ID: 0x20341682
Revision ID: 0x00A1
Revision ID: 0x00A1
Video Accel: ModeMPEG2_A ModeMPEG2_B ModeMPEG2_C ModeMPEG2_D ModeWMV9_B ModeWMV9_A
Deinterlace Caps: {212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFilteri ng
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFilteri ng
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,UYVY) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFilteri ng
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x32315659) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{212DC722-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,2) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{212DC723-3235-44A4-BD29-E1652BBCC71C}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,1) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_MedianFilteri ng
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
Registry: OK
DDraw Status: Enabled
D3D Status: Enabled
AGP Status: Enabled
DDraw Test Result: Not run
D3D7 Test Result: Not run
D3D8 Test Result: Not run
D3D9 Test Result: Not run
BMnot
-
Ditto Same here....
------------------
System Information
------------------
Time of this report: 5/15/2006, 13:58:15
Machine name:Triumph
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.050301-1519)
Language: English (Regional Setting: English)
System Manufacturer: AWARD_
System Model: AWRDACPI
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: AMD Sempron(tm) Processor 3100+, MMX, 3DNow, ~2.1GHz
Memory: 1024MB RAM
Page File: 291MB used, 3734MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.2180 32bit Unicode
---------------
Display Devices
---------------
Card name: NVIDIA GeForce FX 5500
Manufacturer: NVIDIA
Chip type: GeForce FX 5500
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0326&SUBSYS_00000000&REV_A1
Display Memory: 256.0 MB
Current Mode: 1280 x 1024 (32 bit) (75Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: nv4_disp.dll
Driver Version: 6.14.0010.8198 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 12/10/2005 04:06:00, 3955456 bytes
-
With the 5000 series NVidia cards, you should be using the 61.77 drivers.
-
Originally posted by NHawk
110.26 is the Nview Desktop version.
Edit: I have no issues with flight frame rate. Mine are all GV related. And I've tried several different drivers. All with the same result. GV battles, especially near forests are not an option for me now. FR drops to 9.
I have the same problem but only when sighting from a tank main gun. Sweep it past a bunch of trees and the FR drops to 10-15 FPS.
P4 3.2g
6800GT 256mb latest drivers 4x AA, AH detail set to default
1g PC3200
-
A wipe/reinstall of the game helped a lot for me, altho I still have issues sometimes, mostly in a big furball close to the ground.
-
For 6xxx card users I am successfully running 91.28 drivers. I believe still in beta. I have noticed a performance advantage over the latest omega performance drivers. YMMV
sys specs
Processor: AMD Athlon(tm) 64 Processor 3000+, ~1.8GHz
Memory: 1024MB RAM PC 3200
Card name: NVIDIA GeForce 6600 GT
Mind you I run my system lean. I have only 14 processes in task manager once booted up
AH set up res 1200x1024
tex size 512
preload system mem
no preload skin
slideres 7/8 max
v sync enabled
Lowest I have gotten in flight is high teens . This was OTD in a furball with much on fire . ( Bomber and Field lit up)
Lowest in Gv low teens many gvs and trees furball going on over head.
I suspect I would get better frames if i went to default in certain situations. But they are infrequent so I don't bother to jump around.
Bronk
-
Just a thought, but are you guys pre-loading in system memory? I used to, but the Skuzzy says skins are up over a gig now, so pre-loading with only 1 gig of memory is going to cause mini freezes.
-
I preload textures, but not skins, would that matter?
BMnot
-
Skuzzy: the new patch has different graphic detail sliders. Is "Default" now the same as "Default" was before 2.08? My frame rates have also tanked for GV views despite having the sliders at "Default" in both versions. Perhaps the new "Default" is actually more detailed than before?
715
-
Guys
Newer is not always better with drivers. Bronk, I will trust you when you say you are getting a performance increase, but long term testing of most of the newer drivers has shown NO increase in performance for those of us with 6xxx series cards. The people mucking about with the drivers are making changes that directly affect the newer 7xxx series cards. Some of them actually HURT performance in the 6xxx series cards. For that reason, I can honestly say for all the drivers I have tried on my 6800 Ultra, I have not found any of the newer ones that work better than the 66.93 drivers. They arent all necessarily worse either, but not better. Which just tells me they have done NOTHING to any of these drivers since then that increases performace for the 6xxx series cards. This opinion has been reinforced by my communication with one of the guys at the DH website. They should know, if anyone outside Nvidia does.
-
Originally posted by TCFkas
Ok, the latest patch has thrown my FR into freeze hell. I have the NVIDIA GeForce 6200 with 256 meg. I have a Gig of Ram. When I am in clear blue skies FR gets to 71, but if something pops up on screen it drops into 40's and God forbid it smoke as now it drops into 20's. If screen gets real cluttered and drops below 20, standby for freeze up and the only way out is a reboot. I've updated the drivers and nada.
I also have the Nvidia GEForce 6200 with 256 meg and also a Gig of Ram. I also get FR up to 71 in clear skies. However, FR drops to mid-30s to 40s in a crowd with some slight screen freeze up. Whenever I get into a GV, and get near trees Fr suffers a massive drop. If I use zoom while in or near trees, my FR drops to single digits. I did not have these problems prior to Version 2:08 and subsequent patches. In Version 2:07, I could pre-load vid memory, system memory and skins but in Version 2:08 vid memory cannot be pre-loaded.
-
Again......to preload skins, and textures using the hires package it takes a minimum of 1.2 ghz of RAM to do so. So I would suggest if you do preload everything have at least 2 ghz of RAM. Stutters usually indicate something being loaded to or from memory.
Also it has been said many times in this forum make sure nothing is running in the background taking up resources.
A few good programs such as fsautostart can shutdown uneeded applications.
Also tracking cookies can be a problem. Again Adaware is a free download that can rid your system of these problems. If you want to do one better SpySweeper is an application that is more comprehensive and thorough then Adaware. SpySweeper however you must purchase. It is well worthwhile to do so.
-
Originally posted by Hajo
.....Also tracking cookies can be a problem. Again Adaware is a free download that can rid your system of these problems. If you want to do one better SpySweeper is an application that is more comprehensive and thorough then Adaware. SpySweeper however you must purchase. It is well worthwhile to do so.....
Cookies are subject to a number of misconceptions, mostly based on the erroneous notion that they are computer programs. In fact, cookies are simple pieces of data unable to perform any operation by themselves. In particular, they are neither spyware nor viruses, despite the detection of cookies from certain sites by many anti-spyware products.
-
Originally posted by NHawk
Cookies are subject to a number of misconceptions, mostly based on the erroneous notion that they are computer programs. In fact, cookies are simple pieces of data unable to perform any operation by themselves. In particular, they are neither spyware nor viruses, despite the detection of cookies from certain sites by many anti-spyware products.
Methinks you do not understand the difference between "cookies" and "tracking cookies".
To understand the tracking-cookie issue, you have to know something about cookies overall, and you have to know what spyware actually is.
Cookies are small text files that Web-site operators - and third-party companies that insert ads into Web sites - place on a user's computer. Many types of cookies are harmless or even helpful. For instance, a cookie might help a Web site remember your preferences for what news topics you chose to see. With your permission, it might store your login information, so you don't have to type it in each time you visit a particular site. "Remember Me" check boxes where you sign in to websites use this feature. Antispyware programs aren't designed to detect or remove these helpful cookies.
Tracking cookies shouldn't be confused with these other cookies. They have no user benefit except the vague promise that the ads you get as a result may be better tailored to your interests, because they record every website you visit, and deliver that information back to its originator the next time you visit their site, or an affiliated site.
Spyware - and a related category called adware - is computer code placed on a user's computer without his or her permission and without notification, or with notification so obscure it hardly merits the term. Once installed, spyware and adware alter the PC's behavior to suit the interests of outside parties rather than those of the owner or user.
Examples of spyware and adware include programs called "browser hijackers," which reset the home page or search engine your browser uses so it is diverted to the sites of the spyware and adware companies or their clients. Others record your activities and report them to outside parties. Still others push ads in your face, even when you aren't using the Web.
Some tracking-cookie purveyors say their cookies aren't really spyware because they aren't full-fledged programs and they aren't as outrageous as spyware programs such as "key loggers," which record and report every keystroke you enter.
They may not be true spyware, but they are not true Cookies either. They go beyond the limited, helpful functions of a true Cookie and record information you may not wish to share with others. If there was nothing wrong with them, anti-spyware programs would not be able to pick them out from normal Cookies and remove them (not all do, but there are several of the better ones that do).
-
Originally posted by StarOfAfrica2
Methinks you do not understand the difference between "cookies" and "tracking cookies".....
Trust me, I understand the difference. I was merely pointing out that they do nothing on their own. They do not slow down the operation of a computer. Unless of course you visit the web site and keep the browser open while it pops up ads. :)
-
Originally posted by Hajo
Again......to preload skins, and textures using the hires package it takes a minimum of 1.2 ghz of RAM to do so. So I would suggest if you do preload everything have at least 2 ghz of RAM. Stutters usually indicate something being loaded to or from memory.
Also tracking cookies can be a problem. Again Adaware is a free download that can rid your system of these problems. If you want to do one better SpySweeper is an application that is more comprehensive and thorough then Adaware. SpySweeper however you must purchase. It is well worthwhile to do so.
The point that I was making was that even with 1 Gig of ram and 256 meg of vid ram, I did not, repeat did not, have any FR problems at all. My FR problem as previously stated by me, did not occur until the installation of Version 2:08 and patches. I also have spyware programs which I use regularly. I posted here because others seem to have developed the same problem since Version 2:08 came out and I believe that it is something that Skuzzy or someone should consider.
Also as I pointed out in my earlier post, I could pre-load vid memory in Version 2:07 and I was using 85 megs of memory in flight with no problems whatsoever. Currently I am only using 32 megs of memory which was standard when I only had 128 megs of memorry.
In summary, Version 2:08 and patches did result in a degradation of performance for some of us. This is not a complaint but just a comment with the hope that HTC will research the problem to find out what caused the change.,
-
I got the same frame rate problems also. I didn't even know what frame rate was before, I didn't need to. Everything was just fine. I'm starting to realize that this game isn't so much about yo yo's and reversals and learning to fly, that's the easy stuff. It's more about the mighty silicone chip. And for me to learn hardware and software is about like a fourth grader teaching himself calculus. It's very discouraging.
-
Its really easier than it looks at first Clutz. Hang in there. :)