Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: doomed on October 04, 2009, 10:35:40 AM
-
Hi i don't want to get into the entire thing again but since the .8 patchi have had bad screen stutters that make the game unplayable almost
Ive uninstalled re installed updated drivers got older ones done hi rez no hi rez turned all settings off and on bla bla bla and nothing changes at all as far as the stutters and frame rate issues go.
Its been a while and no update to fix it or address it. Is something being worked on or should i just cancel my account because i really don't have much fun when i can play for crap because of the stutters.I really enjoy AH but this is getting old fast,my machine is not "top of the line' but is very very good and has no trouble playing any other game including extream graphic hungry games. :furious
-
A DXDIAG output would be helpful.
I am going to take a real wild guess here and say your computer might have a multi-core AMD CPU and an NVidia video card. Just testing a theory, at the moment.
-
:aok
-
Still need the DXDIAG output.
-
A DXDIAG output would be helpful.
I am going to take a real wild guess here and say your computer might have a multi-core AMD CPU and an NVidia video card. Just testing a theory, at the moment.
Paying close attention although I don't have stutters but I do have the above.
-
Not all of that combination is affected.
-
Sorry i dont know how to do the dxilog thing but i do have duel core and nvidea 9800
-
I have an intel duel core with nvidia 9800 card and have some stuttering.
SKWing19
-
All that can be done, without a DXDIAG output (http://bbs.hitechcreations.com/smf/index.php/topic,71591.msg3215282.html#msg3215282), is just "guessing".
-
DXDIAG - Go to start button, run, type dxdiag, hit enter. It will then throw up the info required. Once thats done, you can save it as a text file, and you need to post the first 1/3rd on here for Skuzzy, or email it to him on the support email.
hth,
Wurzel
-
------------------
System Information
------------------
Time of this report: 10/4/2009, 11:16:55
Machine name: REDWINGS1
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.090206-1234)
Language: English (Regional Setting: English)
System Manufacturer: EVGA__
System Model: 132-YW-E178-FTW
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: Intel(R) Core(TM)2 Duo CPU E8500 @ 3.16GHz (2 CPUs)
Memory: 2302MB RAM
Page File: 201MB used, 3995MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.5512 32bit Unicode
------------
DxDiag Notes
------------
DirectX Files Tab: No problems found.
Display Tab 1: The file nv4_disp.dll is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer.
Sound Tab 1: The file ctaud2k.sys is not digitally signed, which means that it has not been tested by Microsoft's Windows Hardware Quality Labs (WHQL). You may be able to get a WHQL logo'd driver from the hardware manufacturer.
Music Tab: No problems found.
Input Tab: No problems found.
Network Tab: No problems found.
--------------------
DirectX Debug Levels
--------------------
Direct3D: 0/4 (n/a)
DirectDraw: 0/4 (retail)
DirectInput: 0/5 (n/a)
DirectMusic: 0/5 (n/a)
DirectPlay: 0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow: 0/6 (retail)
---------------
Display Devices
---------------
Card name: NVIDIA GeForce 9800 GT
Manufacturer: NVIDIA
Chip type: GeForce 9800 GT
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0605&SUBSYS_0BD219F1&REV_A2
Display Memory: 1024.0 MB
Current Mode: 1920 x 1200 (32 bit) (60Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: nv4_disp.dll
Driver Version: 6.14.0011.9062 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 8/17/2009 00:57:00, 5845760 bytes
WHQL Logo'd: No
WHQL Date Stamp: None
VDD: n/a
Mini VDD: nv4_mini.sys
Mini VDD Date: 8/17/2009 00:57:00, 7729568 bytes
Device Identifier: {D7B71E3E-4545-11CF-2759-D92B03C2CB35}
Vendor ID: 0x10DE
Device ID: 0x0605
SubSys ID: 0x0BD219F1
Revision ID: 0x00A2
Revision ID: 0x00A2
Video Accel: ModeMPEG2_C ModeMPEG2_D
Deinterlace Caps: {6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YUY2,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{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
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(UYVY,YUY2) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{335AA36E-7884-43A4-9C91-7F87FAF3E37E}: Format(In/Out)=(YV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_BOBVerticalSt retch
{6CB69578-7617-4637-91E5-1C02DB810285}: Format(In/Out)=(NV12,0x3231564e) Frames(Prev/Fwd/Back)=(0,0,0) Caps=VideoProcess_YUV2RGB VideoProcess_StretchX VideoProcess_StretchY DeinterlaceTech_PixelAdaptive
{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
-------------
Sound Devices
-------------
Description: SB X-Fi Audio [0001]
Default Sound Playback: Yes
Default Voice Playback: Yes
Hardware ID: PCI\VEN_1102&DEV_000B&SUBSYS_00431102&REV_03
Manufacturer ID: 1
Product ID: 100
Type: WDM
Driver Name: ctaud2k.sys
Driver Version: 6.00.0001.1346 (English)
Driver Attributes: Final Retail
WHQL Logo'd: No
Date and Size: 2/19/2009 18:45:16, 535320 bytes
Other Files:
Driver Provider: Creative
HW Accel Level: Standard
Cap Flags: 0xF5F
Min/Max Sample Rate: 1, 192000
Static/Strm HW Mix Bufs: 128, 128
Static/Strm HW 3D Bufs: 128, 128
HW Memory: 0
Voice Management: No
EAX(tm) 2.0 Listen/Src: No, No
I3DL2(tm) Listen/Src: No, No
Sensaura(tm) ZoomFX(tm): No
Registry: OK
Sound Test Result: Not run
---------------------
Sound Capture Devices
---------------------
Description: SB X-Fi Audio [0001]
Default Sound Capture: Yes
Default Voice Capture: Yes
Driver Name: ctaud2k.sys
Driver Version: 6.00.0001.1346 (English)
Driver Attributes: Final Retail
Date and Size: 2/19/2009 18:45:16, 535320 bytes
Cap Flags: 0x41
Format Flags: 0xFFF
-----------
DirectMusic
-----------
DLS Path: C:\WINDOWS\SYSTEM32\drivers\GM.DLS
DLS Version: 1.00.0016.0002
Acceleration: n/a
Ports: Microsoft Synthesizer, Software (Not Kernel Mode), Output, DLS, Internal, Default Port
SB X-Fi Audio [0001], Software (Kernel Mode), Output, DLS, Internal
Microsoft MIDI Mapper [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB X-Fi Synth B [0001] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
SB X-Fi Synth A [0001] [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
Microsoft GS Wavetable SW Synth [Emulated], Hardware (Not Kernel Mode), Output, No DLS, Internal
Registry: OK
Test Result: Not run
-------------------
DirectInput Devices
-------------------
Device Name: Mouse
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: Keyboard
Attached: 1
Controller ID: n/a
Vendor/Product ID: n/a
FF Driver: n/a
Device Name: Comfort Curve Keyboard 2000
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x045E, 0x00DD
FF Driver: n/a
Device Name: CH Control Manager Device 1
Attached: 1
Controller ID: 0x0
Vendor/Product ID: 0x068E, 0xC010
FF Driver: n/a
Device Name: CH Control Manager Device 2
Attached: 1
Controller ID: 0x1
Vendor/Product ID: 0x068E, 0xC011
FF Driver: n/a
Device Name: CH Control Manager Device 3
Attached: 1
Controller ID: 0x2
Vendor/Product ID: 0x068E, 0xC012
FF Driver: n/a
Poll w/ Interrupt: No
Registry: OK
-----------
USB Devices
-----------
+ USB Root Hub
| Vendor/Product ID: 0x10DE, 0x036C
| Matching Device ID: usb\root_hub
| Service: usbhub
| Driver: usbhub.sys, 4/13/2008 12:45:37, 59520 bytes
| Driver: usbd.sys, 8/4/2004 06:00:00, 4736 bytes
----------------
Gameport Devices
----------------
------------
PS/2 Devices
------------
+ HID Keyboard Device
| Vendor/Product ID: 0x045E, 0x00DD
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
| Driver: kbdhid.sys, 4/13/2008 12:39:48, 14592 bytes
| Driver: kbdclass.sys, 4/13/2008 12:39:47, 24576 bytes
|
+ HID Keyboard Device
| Vendor/Product ID: 0x068E, 0xC000
| Matching Device ID: hid_device_system_keyboard
| Service: kbdhid
| Driver: kbdhid.sys, 4/13/2008 12:39:48, 14592 bytes
| Driver: kbdclass.sys, 4/13/2008 12:39:47, 24576 bytes
|
+ Terminal Server Keyboard Driver
| Matching Device ID: root\rdp_kbd
| Upper Filters: kbdclass
| Service: TermDD
| Driver: termdd.sys, 4/13/2008 18:13:20, 40840 bytes
| Driver: kbdclass.sys, 4/13/2008 12:39:47, 24576 bytes
|
+ Logitech USB TrackMan Wheel
| Vendor/Product ID: 0x046D, 0xC404
| Matching Device ID: hid\vid_046d&pid_c404
| Service: mouhid
| Driver: mouclass.sys, 4/13/2008 12:39:47, 23040 bytes
| Driver: mouhid.sys, 8/4/2004 06:00:00, 12160 bytes
|
+ HID-compliant mouse
| Vendor/Product ID: 0x068E, 0xC001
| Matching Device ID: hid_device_system_mouse
| Service: mouhid
| Driver: mouclass.sys, 4/13/2008 12:39:47, 23040 bytes
| Driver: mouhid.sys, 8/4/2004 06:00:00, 12160 bytes
|
+ Terminal Server Mouse Driver
| Matching Device ID: root\rdp_mou
| Upper Filters: mouclass
| Service: TermDD
| Driver: termdd.sys, 4/13/2008 18:13:20, 40840 bytes
| Driver: mouclass.sys, 4/13/2008 12:39:47, 23040 bytes
-
If you need more let me know
SKWing19
-
Skuzzy, I've had the same problem...posted dxdiag repeatedly...no resolution. Fortunately I know enough on how to tweak my system so the stuttering is minimal most of the time.
One question that no one has deemed worth answering, and I'm going to ask again, does the game still do the pre-load stuff like it did in 2.13? The options for preloading textures and skins doesn't exist in the main video settings area anymore...that was the most notable change. Can't say that the preload is still happening because with 2.13 my system was using over 122MB of video memory with high steady frame rates in all situations and no stuttering, now I'm lucky if it uses 100MB with detailed water on...ver 2.15 average is 88MB+, frame rates from 74 to 40, and every 30 seconds a noticeable video stutter occurs regardless of altitude...really low level (< 1000ft) the stutter is more pronounced.
System information...again:
------------------
System Information
------------------
Time of this report: 9/5/2009, 08:47:13
Machine name: XXX
Operating System: Windows XP Professional (5.1, Build 2600) Service Pack 3 (2600.xpsp_sp3_gdr.090206-1234)
Language: English (Regional Setting: English)
System Manufacturer: XFX68L
System Model: XFX Nforce 680i LT
BIOS: Phoenix - AwardBIOS v6.00PG
Processor: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz (2 CPUs)
Memory: 2558MB RAM
Page File: 528MB used, 2896MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
DX Setup Parameters: Not found
DxDiag Version: 5.03.2600.5512 32bit Unicode
---------------
Display Devices
---------------
Card name: NVIDIA GeForce 9500 GT
Manufacturer: NVIDIA
Chip type: GeForce 9500 GT
DAC type: Integrated RAMDAC
Device Key: Enum\PCI\VEN_10DE&DEV_0643&SUBSYS_400A1682&REV_A1
Display Memory: 512.0 MB
Current Mode: 1280 x 800 (32 bit) (60Hz)
Monitor: Plug and Play Monitor
Monitor Max Res: 1600,1200
Driver Name: nv4_disp.dll
Driver Version: 6.14.0011.9062 (English)
DDI Version: 9 (or higher)
Driver Attributes: Final Retail
Driver Date/Size: 8/17/2009 00:57:00, 5845760 bytes
WHQL Logo'd: n/a
WHQL Date Stamp: n/a
VDD: n/a
Mini VDD: nv4_mini.sys
Mini VDD Date: 8/17/2009 00:57:00, 7729568 bytes
Device Identifier: {D7B71E3E-4503-11CF-5456-016000C2CB35}
Vendor ID: 0x10DE
Device ID: 0x0643
SubSys ID: 0x400A1682
Revision ID: 0x00A1
Revision ID: 0x00A1
Video Accel: ModeMPEG2_C ModeMPEG2_D
-
Gyrene you have your resoluation set very low. Can it run the game in native resolution for your monitor?
Wing19 is your Soundblaster X-Fi a Gamer Xtreme by any chance? I suspect shared IRQs and audio processing pushed to the CPU is causing the problem. Moving to faster video cards is not going to fix that but getting a better sound card would at least help.
-
Chalange
it is a Sound Blaster X-fi Titanium, and what would be a better card?
How can I change IRQ settings I have tried looking on the internet and the set up for my motherboard. Cant seem to change anything.
any help would be appreciated
-
I'm having the same issue. Tonight it got really bad. Lost UDP, and it would seem to be a connection issue.
Trace Route:
Tracing route to 206.16.60.41 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 6 ms 7 ms 10.240.160.57
3 7 ms 7 ms 5 ms dstswr2-vlan2.rh.nbrgnj.cv.net [67.83.246.162]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 10 ms 14 ms 10 ms ae-33-89.car3.NewYork1.Level3.net [4.68.16.133]
9 15 ms 11 ms 9 ms 192.205.33.93
10 56 ms 58 ms 56 ms cr2.n54ny.ip.att.net [12.122.130.130]
11 57 ms 56 ms 55 ms cr2.wswdc.ip.att.net [12.122.3.38]
12 55 ms 55 ms 55 ms cr1.attga.ip.att.net [12.122.1.173]
13 57 ms 56 ms 55 ms cr2.dlstx.ip.att.net [12.122.28.174]
14 54 ms 55 ms 55 ms gar23.dlstx.ip.att.net [12.122.138.153]
15 56 ms 57 ms 56 ms 12-122-254-154.attens.net [12.122.254.154]
16 256 ms 210 ms 203 ms mdf001c7613r0003-gig-12-1.dal1.attens.net [63.24
1.193.22]
17 57 ms 57 ms 63 ms 206.16.60.41
Trace complete.
Ping Plotter kept coming up the same way on the 4-7 hops.
Last 5 or 6 days it's been happening. This is the first time I've ever had an issue with lag/connection/UDP and such.
-
it is a Sound Blaster X-fi Titanium, and what would be a better card?
As much as I dont like Creative and especially the X-Fi that Titanium is supposed to be a good card. I dont agree that it is in every case. The problem is related to the use of nvidia chipsets and ESPECIALLY with SLI systems along side the X-Fi cards. From Creatives website:
"Very lengthy handling of Interrupt Service Routines (ISR) and Deferred Procedure Calls (DPC) by the graphics driver on nForce motherboards (Asus, MSI, and Gigabyte are some motherboard vendors that use this chipset), particularly when nVidia SLI graphics are used."
That said the Auzentech cards (also a X-Fi) dont seem to suffer with this problem and so rather than push the blame on nvidia I have to say that the blame lies with brand 'C' and somewhere within their drivers but I am not tech savy enough to say for sure but I know what works in my experience and that is what I am reporting to you. I decided to go with the HT Omega line and I have had very good success with the Striker 7.1 card even on Vista.
I dont want the burden of your upgrade on me though if it doesnt work for you. Please bear that in mind. I hope you can RMA that X-Fi.
-
Gyrene, what in-game settings ("Video Settings", and "Options->Graphic Detail->Advanced") do you have the game configured for?
-
Wing19 I thought about your situation some more and I want to suggest you pull the Titanium and try AH with onboard sound (as much as that sounds like a bad idea). I believe you will still get hesitations (I have the sister board to your MB and mine did have hesitations when I used onboard sound) but the stutters should decrease a great deal. Also you want to make sure you are using SLI correctly and NOT using nHancer but instead using the nvidia control panel application and properly. By that I mean enhancing the AH application and allowing the primary card to take care of the rendering of frames and using the slave card to do the post-processing like this:
http://i447.photobucket.com/albums/qq197/Chalenge08/Image1.jpg
http://i447.photobucket.com/albums/qq197/Chalenge08/Image2.jpg
Reboot if SLI was not already active. Next you should set your global settings and AHII profile settings as follows (in picture 1 above choose the option just above 'Set SLI...' and on the Global Settings tab:
http://i447.photobucket.com/albums/qq197/Chalenge08/Image3.jpg
and then on the game settings tab it should look like this:
http://i447.photobucket.com/albums/qq197/Chalenge08/Image4.jpg
Your system should make good use of that. In AH you want Anti-aliasing set to the first notch and you should be able to have all other features on but shadows may limit your frame rate if set to 4096 (I recommend 2048).
-
Gyrene, what in-game settings ("Video Settings", and "Options->Graphic Detail->Advanced") do you have the game configured for?
This is after the last bit of changes I made...an hour or so of experimenting:
(http://i33.tinypic.com/2ibg6l5.jpg)
(http://i36.tinypic.com/2ldan8j.jpg)
*NOTE: turning on detailed water actually lessened the stutter effect but the frame rates are unstable...starting out in tower frame rates are zero then as objects render (30 to 60 seconds) they jump to 74-75. ISP speed is generally steady around 18mb down and 1.5mb up.
Gyrene you have your resoluation set very low. Can it run the game in native resolution for your monitor?
Tried that, but the frame rates bottom out...I'm thinking I may have to find a faster video card with a 256bit interface instead of the 128bit on the current card...maybe more pixel pipelines too...I just don't want to end up having to upgrade my PSU as well since it's a new 700w modular and cost a pretty penny.
-
And what happens when you turn off "Detailed Terrain"?
I really cannot see the video card you have in your computer being able to keep up when things get busy in the game, when running with the "Detailed Terrain" option enabled.
-
I am not up on the *500 line of nvidia sticking mostly to the *800 or *900 cards (now *95s). Skuzzy says it may have trouble so you will want to get all you can from it. Of course I always want to run in native resolution but in your situation it may not be possible.
BUT... your refresh rate reports 60Hz and yet you say you are hitting 75fps? That shouldnt happen unless you have nvidia control panel (NCP) set to Force Off vsync (not recommended). If you have vsync on in AH (and your screenshot indicates you do) and NCP is set for application setting or Force On (by my settings it should be but I use SLI) then you most likely have a driver issue that needs to be cleared up by an uninstall and a good cleaning program (I use Driver Cleaner). Afterwards install the latest driver from your cards manufacturer and you should be good.
My way of thinking on FPS is not the biggest number I can get but to insure smooth video rendering without stutters. The only possible reason I could think of to need more than say 38 fps (give or take about where I lose the ability to see any difference) would be if Skuzzy tells us it matters. For instance if you take the amount of ammo a fifty or thirty caliber weapon fires in one second and spread that out over say 75 frames. If those frames dont render do the bullets hit? If they do hit then it doesnt matter. If they dont hit then we want the most we can get. I dont think it matters but I am open to more information on that one and obviously it would cause me to change my tune.
-
And what happens when you turn off "Detailed Terrain"?
I really cannot see the video card you have in your computer being able to keep up when things get busy in the game, when running with the "Detailed Terrain" option enabled.
I hate to say it Skuzzy but there's no way. This game should not require a higher end video card than what I have to run detailed terrain, especially after being able to run it throughout the 2.14 series of improvements with detailed terrain no with significant hits on the frame rates until patch 7. Detailed water I can understand...that wasn't turned on until this past Thursday trying to eliminate the stuttering effect.
It's an XFX 9500GT 600MHz core 512MB DDR3 (2000MHz memory clock) 128bit interface...my old P4 with the 7300GT gets the same results with the same settings, and that one I can somewhat understand turning detailed terrain off to maintain frame rates...but I had 3 systems to test on through 2.14 patch 6 and the stuttering effect was consistent with them all...tweaking settings throughout each one until the effect was minimized and the only one that absolutely would not run detailed terrain on at 60-75 frames steady was the ATI 9600pro.
Since 2.15 I have been getting 60-75 frames with vertical sync set to application controlled on both systems with Nvidia cards regardless of the driver version. When the frame rates start fluctuating during air battles, I do get "rubber bullets" at the 50 fps and below marks. I noticed Nvidia just released a new driver today (noting increased performance in some very high video rendering games) so I'll do a clean install later this evening and test it.
-
If you have vsync set ON and your frame rate exceeds your refresh rate (your dxdiag says 60 Hz so 60 fps) then there is something going wrong. You would be best served to uninstall your drivers clean your system of all video drivers and then reinstall fresh with drivers from the manufacturer of your video card (not nvidia).
According to the research I did today (admittedly rushed) the 9500 GT is the equal to an 8600 or about 1/4 the card (32 versus 112 processor streams whatever that is) the 9800 would be (at about half the price). I would go with what Skuzzy said.
-
Chalenge,
I have tried onboard sound, single card and the settings on you posts still have stutters. The stutters I have are not bad but annoying and there seems to be no pattern. The setting you provided me with, I cant seem to get my frame rates any higher than about 20. I have not set global settings, does this really make a difference?
-
Global settings can... maybe. Did you uninstall the cards and clean the drivers (sound card AND video) and then reinstall fresh drivers for both? Please make sure you get the drivers from the video card manufacturer.
You are using a graphics setting above your monitors maximum resolution though (1600x1200 Max recommended). Sorry I missed that earlier. Also dont try to use shadow resolutions above 2048 or turn them off altogether until you are running smoothly.
Your MB is slightly better than the 780i that I have. You have XP and I have Vista. I have 8 GB and I think you have 4 GB (shouldnt matter unless you mixed RAM to get 3 GB or something). You have the E8500 and I have the E8400. I have 8800 GTs and you have the 9800s.
In theory you should do better than my system that I took those settings from.
-
Global settings can... maybe. Did you uninstall the cards and clean the drivers (sound card AND video) and then reinstall fresh drivers for both? Please make sure you get the drivers from the video card manufacturer.
You are using a graphics setting above your monitors maximum resolution though (1600x1200 Max recommended). Sorry I missed that earlier. Also dont try to use shadow resolutions above 2048 or turn them off altogether until you are running smoothly.
Your MB is slightly better than the 780i that I have. You have XP and I have Vista. I have 8 GB and I think you have 4 GB (shouldnt matter unless you mixed RAM to get 3 GB or something). You have the E8500 and I have the E8400. I have 8800 GTs and you have the 9800s.
In theory you should do better than my system that I took those settings from.
I will try new settings in global and I have cleaned all drivers with a fresh driver install
The resolution matches my monitor
I will mess around with it and post results
Thank you
-
gyrene, if you are not willing to try things I suggest and let me know the results, there is not much I can do to help.
I also happened to notice, at the time of your DXDIAG, Windows was experiencing a very high amount of page file usage. Is that normal for your computer?
-
gyrene, if you are not willing to try things I suggest and let me know the results, there is not much I can do to help.
I also happened to notice, at the time of your DXDIAG, Windows was experiencing a very high amount of page file usage. Is that normal for your computer?
It's not that I'm not willing to try what you recommend...fact is that with every single patch update since 2.14 was released I have followed the recommendations made to other people in these forums and spent numerous hours tweaking my system beyond recommendations in order to get the best results possible on my system. I've done everything short of completely reloading my system from scratch...which I may end up doing just to get a cleaner configuration. And I was fairly successful through most of the changes introduced...when I wasn't I just sat back and waited for a patch to be released.
To answer your question, with 2.15 there has been no difference in performance with detailed terrain turned off or on...even when the texture size is dropped to 128.
That 527MB paging file size isn't the normal...I ran that dxdiag with some apps open that aren't normally running...I generally have a 270MB paging file running when I go into the game...down from the 380MB that I had running with 2.14 patch 5.
-
If it makes no difference with "Detailed Terrain" on or off, is it safe to assume you have not changed any of the defaults in the NVidia control panel for the video card?
-
If it makes no difference with "Detailed Terrain" on or off, is it safe to assume you have not changed any of the defaults in the NVidia control panel for the video card?
Actually I have made changes in the Nvidia control panel. Everything that has been recommended to be set to application controlled is set to either "global setting-application controlled" or "forced on". At one point I had it tweaked so much that it caused more problems so I reset it to default and started over. I haven't tested the newest Nvidia driver that was released on 10/5 yet...but it's on the list of things to try.
I have contemplated the purchase of a new video card in the 9800GT line up...but I'm not convinced that's going to resolve the issues. True that logically a faster interface (256 bit vs 128 bit), higher number of pixel pipelines (112 vs 32) and a faster GPU should produce better results...but people with better video cards than the 9500GT have been reporting various problems with each patch since 2.14 was released.
Just out of curiosity, has the stuttering effect (slow object/texture rendering) and fluctuating frame rates been reproducible on your systems? You know, on a system that isn't loaded with top of the line hardware and processes trimmed down to the point below what the average home use would have.
-
1st I didn't read the whole thread.
gyrene do you have stutter on and off line ?.
-
1st I didn't read the whole thread.
gyrene do you have stutter on and off line ?.
You're thinking internet connectivity issue...nope, I have a 20 mbps cable connection that is consistently fast to Texas. The stuttering effect happens even in offline mode.
-
That's the problem gyrene and why I am asking so many questions. I cannot duplicate it. My work system only has a 7600GT video card, so I cannot run with the "Detailed Terrain" option enabled as it bogs the system too much.
At home, I run with all the bells and whistles on and it runs smooth as silk, but it is an ATI card so no apples to apples there either.
Most players report the game runs better and smoother than the previous version. I have a handful of folks who are having stutter issues, and it is proving very difficult to nail down why.
-
You're thinking internet connectivity issue...nope, I have a 20 mbps cable connection that is consistently fast to Texas. The stuttering effect happens even in offline mode.
ok,try to reduce the resolution + texture size until you see no stutter .
If you still have stutter we will have to try something else as will not be video car dependant.
-
ok,try to reduce the resolution + texture size until you see no stutter .
If you still have stutter we will have to try something else as will not be video car dependant.
You mean like 1024x768 at 128 textures? Done...no difference. I appreciate the suggestions but to save you the trouble of thinking about something else to suggest...I have done everything short of erasing my hard drive and doing a fresh rebuild and or buying a new video card. Since 2.14 was originally released I have gone from 1440x900 1024 textures with hires pack and custom sounds to my current configuration (1280x920 256 textures no custom sounds). Each patch has created a different set of challenges that I could either adjust out or had to wait for another update.
With the last version of 2.13 my video card showed in excess of 126MB of memory being used, at 512 textures...no version of 2.14 has exceeded 100MB regardless. I'm of the opinion that the stuttering effect is a slowed down rendering process caused by textures/objects not getting cached effectively as they are rendered. The underlying issue with the stuttering might be avoided if some artifacts were preloaded into memory like 2.13 did...as the game started you could see everything that was being cached into memory and by the time you hit the tower there wasn't anything to cache...that's just from my observations with the lower memory usage to the way I see things rendered on the screen.
-
dont waste your money on the 9800 nvidea its what i have with 1 gig on board mem and the works.. i still get the stutters on or offline since that .8 patch just like you, regardless of any settings or resolutions or configurations or drivers new or old. It pretty much plays exactly the same...shrug...
-
And yet, Hitech has a 9800 in his computer, as does Waffle and neither of them have stutter issues. I really do not think it is the video card, itself, but it could be a combination of things causing this.
-
doomed: Did you ever post a DXDIAG? That is the number one best thing you can do in order to get help with stutters.
-
Weird how some have studders and some don't, even with crappier cards I still cannot solve my issues. good luck Gyrene!! :salute
-
And yet, Hitech has a 9800 in his computer, as does Waffle and neither of them have stutter issues. I really do not think it is the video card, itself, but it could be a combination of things causing this.
I agree Skuzzy. It's not any one part...every patch has created a variety of issues for different people across the board...low end to high end...the one constant has been the stuttering effect and the WSOD. But people who have experienced the stuttering have seen it at different patch levels...one patch is good...the next isn't...and to varying degrees. I know there is more than a small hand full who have or are experiencing it...the ones who haven't reported it, either don't frequent the forums or they have minimized the effect on their systems so it's playable. Obviously the worst cases get reported.
This is the guts of my system:
Mobo: XFX nForce 680i LT SLI Socket 775 Motherboard - OEM
Video Card: XFX PVT95GYDQ3 GeForce 9500 GT 512MB 128-bit GDDR3 PCI Express 2.0 x16 HDCP Ready SLI Supported Video Card - Retail
Processor: Intel Core 2 Duo E6600 2.4GHz 4MB L2 Cache LGA 775 1066 MHz FSB
PSU: Thermaltake ToughPower Modular W0116 Power supply - 750 Watt
RAM: 1x4 GB PC2 DDR2 800 (PC26400)
I'm sure eventually it will get ironed out...it's just another part of the improvement process.
-
As your previous post showed it's not video card related and your CPU is good enough I suggest you to update the nForce chipset driver and get ride of the nvidia firewall
If you can also try with an external sound card it would be interesting, to narrow the origin of your troubles.
-
By any chance is the video IRQ being shared with another device? Or maybe the sound chip IRQ? How about the network card/chip IRQ? The physical IRQ, not the virtual one.
-
get ride of the nvidia firewall
:huh Say what? Nvidia firewall? Haven't seen anything like that on my system.
If you can also try with an external sound card it would be interesting, to narrow the origin of your troubles.
The system has the Realtek 5.1 digital audio chipset on it. I suppose I could go to Bestbuy and grab a Soundblaster just to see if it makes a difference...if not I just take it back...LOL
By any chance is the video IRQ being shared with another device? Or maybe the sound chip IRQ? How about the network card/chip IRQ? The physical IRQ, not the virtual one.
Never thought about it Skuzzy. I'll check when I get home tonight and report back. Anything is possible with plug and pray.
-
check if you don't have the infamous "Network Access Manager" with "ActiveArmor" installed it's a real pain !
-
The system has the Realtek 5.1 digital audio chipset on it. I suppose I could go to Bestbuy and grab a Soundblaster just to see if it makes a difference...if not I just take it back...LOL
From the kettle to the fire so to speak...
-
Skuzzy the IRQ's are clear. Even looked at the DMA channels. Nothing is crossed.
I figured out the glitch with my frame rates...I didn't have the game resolution set the same as the monitor resolution. Didn't make sense but now I'm running between 60 and 57 frames. I think I have the issue with the stuttering almost figured out as far as my issue goes. As the frame rate fluctuates the object refresh rate fluctuates, which is the visible stuttering effect. Short small stutters happen when there is 1 or less than 1 fluctuation in the frame rate. Higher fluctuations in frame rate causes slower more pronounced stuttering until the frame rate returns to a stable or near stable state regardless of what it ends up being (i.e. high or low).
I updated my video driver and without any changes the stuttering effect was worse until I changed the in game resolution. It's playable now even though the stuttering effect is still there, it's more like little tiny twitches and my frame rates aren't going over my video refresh rates then bottoming out.
Straffo, no Network Acess Manager or otherwise.
-
Face palm! :headscratch:
-
This is still an existing issue. It's not as bad as in some previous revisions but still happens all the time, the fluctuation in the frame rates isn't a direct cause of the stuttering though it does contribute to the severity...and it doesn't matter if detailed terrain is on or off. With 512MB video memory available and only 87MB showing in game as being used with detailed terrain on...the question about memory usage and preloading textures comes to mind again.
-
The game automatically preloads textures. If it was a texture load problem, laptops with thier hideously slow 5400RPM hard drives would be stuttering all the time. I just spent 4 days watching a mess of laptops run the game as smooth as silk.
The ones that struggled all had 70+ (up to 95) processes running in the background.
-
Skuzzy, the newer 5400 rpm SATA drives in laptops (especially the high capacity drives) are fully capable of running the textures in AH as smoothly as 7200 rpm drives. Still, I'm not saying it's absolutely a texture load issue...however if it's not a texture load issue considering v2.13 used 100+ mb of video memory with 512 textures loaded and v2.16 is only using 80+ mb of video memory with 512 textures, then it has to be a rendering issue, maybe caused by chipsets or drivers.
Every single revision since 2.14.0 was released has had reports of stuttering to varying degrees regardless of ATI or Nvidia chipsets. With some tweaking most everyone has been able to minimize the effect so that it doesn't interfere with game play.
Without just dismissing the idea is it possible that considering the manner in which it manifests itself and increases with the amount (not size) of textures rendered, that the stuttering could be eliminated by making some changes to the way textures are preloaded in memory?
-
It is absolutely not a texture preload issue. A texture preload issue would impact everyone equally. The preload before, would load things that may never be needed.
The new graphics engine is more efficient. That is one reason why older computers are running the new version better than the old version while the new version looks better as well.
If you are getting stutters regardless of how the "Detailed Terrain" option is set, then it is something else not releated to rendering. It has to be.
5400RPM SATA drives are slow as snails. A 25% increase in the rotational latency and a reduction in the areal density, is going to slow things down. It cannot help but do so. It is painfully obvious if you put a 7200RPM drive next to the same computer with a 5400RPM drive.
-
The preload before, would load things that may never be needed.
The new graphics engine is more efficient. That is one reason why older computers are running the new version better than the old version while the new version looks better as well.
How is it possible for older computers to run the new version bettter when you have to dial down the in game graphics settings to get decent frame rates when it wasn't necessary with the 2.13 version? I seem to remember a massive outcry from people using older systems with older video cards when 2.14 was first released, and if that were the case then my P4 with the 7300GT should be able to get as good if not better in game performance with the same settings (512 textures, bumpmap and detailed terrain on, all other off).
Or are you referring to older systems with upgraded video cards? I could understand that since a P4 processor can handle the load, or should be able to and a simple video card upgrade could put enough hardware power into it to overcome any limitations.
If you are getting stutters regardless of how the "Detailed Terrain" option is set, then it is something else not releated to rendering. It has to be.
I'm not totally sure either way Skuzzy, that's why I'm asking. If I had access to the code I could find out for myself...but not going there...so I'm just tossing out the ideas based on my observations and knowledge of 3d rendering. Could it be a bottleneck problem with not enough pixel pipelines or maybe 128bit vs 256bit interface? There was one patch (5? or 6?) that the stuttering went away...and I didn't see anything in the release notes that showed a change that would account for it.
It's not going to be something big or necessarily obvious...could just be a small item that was thought to be "unnecessary". All I know is 2.13 ran totally awesome with 512 textures and all other options active on my 7300GT AGP but since 2.14 my much better 9500GT PCI-E 2.0 on a better hardware platform is having issues that never appeared in the previous version or on my older system...and I'm not the only one.
For me this isn't a huge deal for me...just an annoyance that I'm fairly certain can be resolved from the programming end.
5400RPM SATA drives are slow as snails. A 25% increase in the rotational latency and a reduction in the areal density, is going to slow things down. It cannot help but do so. It is painfully obvious if you put a 7200RPM drive next to the same computer with a 5400RPM drive.
Yeah that's true, I was more referring to data path flow....which the SATA standard is the same across the board regardless of drive speed. Seek and read/write times are going to be better on a 7200 rpm drive, but once you get to the point of data flow it would be the same.
-
The current version of the game is based on a new graphics engine. Everything is being differently. This benefited lower end systems of today as the way things are done now are in step with what they can do. The old version was doing things based on how a video card worked 5 years ago.
Bottom of the line video cards can run with "Bump Mapping" and "Detailed Water" and it will look better than the previous game version did when it was being run full tilt. Not only look better, but it will perform about 10 to 15% better as well.
2.13 cannot be compared to 2.16. They are very different. 2.16 places far more burden on the video card than 2.13 was capable of, in many areas. It is not surprising, nor expected, that many computers cannot run 2.16 with all the details enabled. The graphics engine in 2.16 will need to last 5 years. The 2.13 graphics engine was at the end of its 5 year life.
The data stream from the hard disk of a 5400RPM drive will not be able to sustain itself when compared to a 7200RPM drive. The SATA bus will outrun the 5400RPM drive, by quite a bit.
-
sorry to do a little hijacking here skuzzy, but if I understand correctly an older hd may cause mini warps or stuttering?. reason i ask that that i have been having the same problems as posted here and all my components are brand new, mobo, vc cpu (e8400) except for the older hd that I still use it's a about 5 years old.
semp
-
If you have some of the more 'paranoid' software that uses licensing processes (Corel uses Protexis and Autodesk uses Autodesk Licensing and Adobe uses FLEXnet...etc) you can build up quite a bit of latency in background processes. Couple that with known interference patterns like nvidia chipsets mixed with SB drivers and you have a disaster in the making. Its a wonder computers work at all!
-
Do not forget about iTunes. The background helper is very ill-behaved. Then there are many AV programs also. And anything from Adobe.
-
iTunes - not installed
Adobe Acrobat - disabled all quickstart/helper objects
Windows Update - disabled
MS Office - disabled all quick start objects
Windows default mouse driver
Avast - disable active protection before gaming
Saitek Cyborg profiler - active
Nvidia control panel - active
Gameboster - disables everything except Saitek profiler and network connectivity processes
Before going into the game paging file is down to 270MB...that is as low as it gets.
If the graphics engine of the game is hitting the graphics card the system background processes should not affect the graphical performance of the GPU.
-
<snip>
Before going into the game paging file is down to 270MB...that is as low as it gets.
If the graphics engine of the game is hitting the graphics card the system background processes should not affect the graphical performance of the GPU.
That page file seems a bit large to me. Should be around 150MB, but I have seen worse.
Not quite true about the graphics engine. The data still has to get to the graphics card. Anything on the CPU side can impact that.
-
The paging file is a bit larger than I would want for AH...most of it is the remaining Avast resident files...but with 2.14 patch 5 or 6 I ran with a bigger paging file and no issues. Wasn't that just before the change was made in the way the shadow textures were handled?
I'm down to 256 textures now because last night my frame rates went stupid and hit an all time low of 8 while I was on the deck trying to shoot another player down. Did it 3 separate times...not a big furball...maybe 1 or 2 other planes high that I could see in front of me...several behind me and 1 or 2 others firing at the same plane...on the deck at tree top level...as soon as I pulled the trigger the frame rates hit bottom...to get my frame rate back up, I had to point the nose up for about 30 seconds. I tried it with only bump map terrain turned on...same deal.
My system is above "recommended hardware specifications"...and I doubt the current recommended specifications would run AH with anything more than bump map terrain turned on at 1024x768 resolution and 128 textures...there are too many people running Nvidia video cards for it to be an Nvidia issue.
I know there is another update coming so I'm not going to jump on a bigger video card yet.