![]() |
|
|||||||
| IL-2 Sturmovik: Cliffs of Dover Latest instalment in the acclaimed IL-2 Sturmovik series from award-winning developer Maddox Games. |
![]() |
|
|
Thread Tools | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Are you sure that when you look the ground you still remain at 60 fps ?
I get 60 when looking up, but about 20 when looking down... that´s "normal".
__________________
Win 7 64 Quad core 4Gb ram GTX 560 |
|
#2
|
|||
|
|||
|
no. i set the fps counter, when i want to do the test. and the minimum sticks to 50 or so.
also this is constant, not a happens once in a while. |
|
#3
|
|||
|
|||
|
I get 40-45 with looking down like that. The beta patch has improved the stuttering quite a bit. I imagine this will be a big problem with the Battle of Moscow flying an IL2. Maybe the snow instead of grass will improve the stuttering.
Ailantd I see you have a similar pc to me except you have a better graphics card .But I am getting twice the fps as you! What resolution are you running? do you use ingame AA or FXAA? Are you against lowering your res to 1360x turning off ingame AA and using FXAA? Cause you may be able to double your fps |
|
#4
|
|||
|
|||
|
Quote:
Didn't get a problem, can you confirm this happens both in and out of cockpit? |
|
#5
|
||||
|
||||
|
I have had a similar feeling but have to test it more. It sounds like what happens when you do multithreading that many seems to think is an easy task... The landscape object handling /texture loading etc is on it's own thread now (?) that does not run in sync with the main render thread? If you sync every frame the whole game will stutter so when the landscape thread cant keep up this is what could happen? The main render thread "pumps on" but the "landscape" is not able to keep up?
Just guessing...
__________________
i7 2600k @ 4.5 | GTX580 1.5GB (latest drivers) | P8Z77-V Pro MB | 8GB DDR3 1600 Mhz | SSD (OS) + Raptor 150 (Games) + 1TB WD (Extra) | X-Fi Fatality Pro (PCI) | Windows 7 x64 | TrackIR 4 | G940 Hotas |
|
#6
|
|||
|
|||
|
You mean Intel Hyper Threading ?
Yep, can be a problem, Hyper Threaded cores are not a physical core so they are slowest than a physical one (in short). But my guess in all this is that its the know issue of the grass and trees code not being optimized yet : Quote:
Last edited by Buchon; 05-09-2012 at 09:14 AM. |
|
#7
|
|||
|
|||
|
Quote:
|
|
#8
|
|||
|
|||
|
Quote:
Send your crash files guys ... |
![]() |
|
|