![]() |
#31
|
|||
|
|||
![]()
Still there with Cat 11.4 drivers.
Groan. ![]() |
#32
|
||||
|
||||
![]() Quote:
The software is using the engine differently. I'll post my data in a new thread as soon as I get home. Look at the AA scaling I mentioned. S! Gunny
__________________
Intel i7-3930K @ 4.00 MHz - ASUS Rampage IV EVGA 3072MB VRAM GTX 580 16GB RAM - Windows 7/64 Warthog and U2Nxt Cougar under t.a.r.g.e.t Last edited by TUSA/TX-Gunslinger; 04-29-2011 at 07:51 AM. |
#33
|
|||
|
|||
![]() ![]() Here the lines same here..Cat 11.4 drivers. Last edited by GOZR; 04-29-2011 at 04:44 AM. |
#34
|
|||
|
|||
![]()
S!
Gunny, strange how Tessellation can affect FPS when the game uses none. But you never know how these games work ![]() ![]() Anyways, fill the feedback form to AMD. It made a difference to IL-2 1946 as well ![]() |
#35
|
||||
|
||||
![]()
I was w-r-o-n-g
![]() 1. Tessellation as expected, had no effect on anything ![]() 2. So I started a long series of tests iterating Tessellation and Disabling ATI Tray Tools and Turning it back on. Here are the results: 8XAA in AP - Tessellation = 64X - ATITrayTools Running Frames, Time (ms), Min, Max, Avg 8787, 211340, 0, 96, 41.578 2 big pauses 8830, 211417, 7, 95, 41.766 2 stutters 8569, 211280, 0, 94, 40.558 pauses 8043, 211964, 0, 92, 37.945 8 stuttering periods 8578, 211848, 0, 91, 40.491 pauses 8XAA in AP - Tessellation = 64X - ATITrayTools Shutdown Frames, Time (ms), Min, Max, Avg 9114, 212280, 17, 98, 42.934 Smooth 8994, 212468, 16, 96, 42.331 Smooth 9093, 212634, 17, 96, 42.764 Smooth 9000, 212428, 15, 97, 42.367 Smooth 9007, 212326, 17, 97, 42.421 Smooth 8xAA in AP - Tessellation = OFF - ATITrayTools Shutdown 9012, 212089, 16, 97, 42.492 Smooth 8905, 212175, 17, 93, 41.970 Smooth 8784, 208758, 17, 95, 42.077 boringly smooth 8822, 212061, 16, 93, 41.601 Smooth 8XAA in AP - Tessellation = OFF - ATITrayTool Running 8754, 212337, 0, 96, 41.227 2 large pauses 8892, 212400, 18, 97, 41.864 smooth! 8839, 211994, 14, 93, 41.695 smooth 8414, 212259, 0, 93, 39.640 8614, 212233, 0, 95, 40.587 8605, 212233, 0, 92, 40.545 8562, 212274, 0, 89, 40.335 8688, 212419, 9, 91, 40.900 some jerkyness 8768, 212443, 16, 95, 41.272 smooth 8571, 212186, 0, 95, 40.394 As you can see, ATITrayTools has an effect on the FPS of my system, but in a bit of a random manner. I have no idea why. I have never setup anything in my ATITrayTools except to run the Graph output for the various functions. In case anyone's interested I conducted these tests in the following manner: 1. Start TrackIR, Thrustmaster Target software and Fraps to simulate real load. 2. Start CoD - select "The Black Death" track and after it loads select Play. 3. Let the first playback proceed until it's ended. 4. Restart "The Black Death" track 5. Start Fraps benchmark 5 seconds into track. This is the point where Bf-110 #3 transitions his tailwheel to cross the centerline of nearfield Bf-110 port propeller hub. 6. Observe each track and note pauses, stutters or micro stutters. 7. Stop benchmark after the Bf-110 dives. Track is 3 mins 40 secs long. 8. Repeat. Organize documentation and files. Anyway, I feel a little silly about the Tesselation - kind of did when I posted it. But, hopefully I made up for it ![]() I'm still running Cat 11-3, as I wanted to finsh this testing. I'll install 11-4 today and see what happens. BTW my settings for these test, except where indicated are: ![]() ![]() S! Gunny
__________________
Intel i7-3930K @ 4.00 MHz - ASUS Rampage IV EVGA 3072MB VRAM GTX 580 16GB RAM - Windows 7/64 Warthog and U2Nxt Cougar under t.a.r.g.e.t Last edited by TUSA/TX-Gunslinger; 04-29-2011 at 07:28 AM. |
#36
|
||||
|
||||
![]()
One last thing. Here's a screen capture I did during the earlier testing, obviously when ATITrayTool was active. You can see the cross-core load as the track is being played and you can observe the CPU load (yellow) and most importantly the 5870 GPU load (pink).
![]() At least these settings in Cat 11-3, have my GPU loaded to a greater extent. S! Gunny
__________________
Intel i7-3930K @ 4.00 MHz - ASUS Rampage IV EVGA 3072MB VRAM GTX 580 16GB RAM - Windows 7/64 Warthog and U2Nxt Cougar under t.a.r.g.e.t |
#37
|
||||
|
||||
![]()
Oh, I almost forgot - I don't have the blue line.
![]() S! Gunny
__________________
Intel i7-3930K @ 4.00 MHz - ASUS Rampage IV EVGA 3072MB VRAM GTX 580 16GB RAM - Windows 7/64 Warthog and U2Nxt Cougar under t.a.r.g.e.t |
#38
|
|||
|
|||
![]()
Comprehensive tests!
You don't have the blue lines because you have an Nvidia card. They seem to be a special feature only available to ATi users. Cheers, Nick PS - what utility did you use to produce the plot of CPU/GPU load? |
#39
|
|||
|
|||
![]()
S!
No worries Gunny ![]() ![]() I noted that I get less stutter if I set Building amount to Unlimited. Then they are all already on map thus no loading or popping up. Only thing is the LOD on them..with low setting they are like brown boxes and turn to houses within a radius of your plane(like in old IL-2) and that can cause stutter. Again if you set Very High detail to buildings sure no brownie huts but has an impact on FPS. For me most stutter is caused by SSAO. With it off I have a lot smoother experience with minimal effect on image. Really hard to tell the difference. FPS hit is 10-20fps and that can be a lot in certain scenarios. Also shadows cause some of the stutter as they seem to have at least 2 LOD's. One farther away and when you are close(within the "sphere of LOD") they turn more solid and less flickery. Shadows also have this strange anomaly that they "stretch" at certain angles and look like lines. So clearly something could be done to shadows, be it total rework or more options. Trees have same, farther away they look different and when again closer get more detailed. Gotta say I liked IL-2 original Forest=3 more than this and had basically NO effect on FPS. Actually was better than Forest=1-2. I use trees at Very High as I get less stutter with them that way. Grass. I find it the most useless feature and have it off. Sure it will add something when taking screenies from ground etc. but when flying just a resource strain IMO adding nothing to the experience as the grass appears also within this "sphere of LOD" around the plane. I wish Luthier would get in contact with AMD, at least their Driver Boss is on Twitter and for sure would be interested to get CoD to run on AMD hardware well. IMO flight sim genre is so small that favoring one brand is like shooting oneself in the leg by leaving out some players due certain features etc. I really do not care if a shooter game is optimized for one or another brand, I do not play them ![]() Anyways, back to testing again this weekend. Testing is the only thing I do with CoD as it offers very little for single player. But a good tool for testing ![]() |
#40
|
|||
|
|||
![]()
Hey Gunny,
Thanks for the extensive testing you have done, very interesting. (also whoever said you don´t suffer from the blue lines because you have an nvidia card should have his/her eyes checked). It would be interesting to know what settings you run your tests at graphic wise (everything high, mid, low, buildings unlimited etc) @GOZR Apart from the blue lines that is a gorgeous screenie, would you mind posting your system specs and graphic settings (especially AA, AF etc and whether you override them or not in CCC) you took the screenie at? So far it seems not all ATI cards suffer from the three blue lines bug, older Catalyst drivers seem to have helped some but there are people running the latest drivers who also not suffer from this annoying bug, maybe it has something to do with the VBios version or anything but that is just a wild guess. Only solution that works to solve the blue lines on the horizon bug in all cases is running the game in DX9 but that negatively impacts fps for me for some reason. On another note, my best results to get anti-aliasing working somewhat decent have been to set them to enhance application settings in CCC and 8x in CoD (although that seems to make little difference from running it at 2 times) |
![]() |
|
|