jimbop
03-31-2011, 11:57 AM
I hope this is of interest to someone… This is the sort of data I really wanted over the last few days so maybe it will be of interest to someone who still can't play. See my signature for specs; I consider this a mid-range machine.
Realism was set to full and below are the video settings I used (see Luthier’s Technical FAQ (http://forum.1cpublishing.eu/showthread.php?t=19819) about which settings to reduce for maximum FPS effect). Note that my graphics settings were also modified by an NVIDIA application profile which was all default except for:
- CUDA – GPUs = None (i.e. handled by CPU)
- Texture filtering – Anisotropic sample optimization = On
- Texture filtering – Quality = Performance
- Texture filtering – Trilinear optimization = On
- Vertical sync = Force on (I was getting bad screen tear).
http://s1.postimage.org/21m4m203o/video.jpg (http://postimage.org/image/21m4m203o/)
And here is a collage of my perfmon.exe, resmon.exe and EVGA Precision for GPU usage (core breakdown on the right):
http://s1.postimage.org/21m1azb44/collage.jpg (http://postimage.org/image/21m1azb44/)
My conclusions from this?
1. Multi-core is definitely working (no surprise (http://forum.1cpublishing.eu/showthread.php?t=19819)) and the i7 920 CPU, which is not really a fast CPU these days, just isn’t bothered by this game. Yes, some cores are more used that others but there is plenty of CPU to go around. And remember that the physics were entirely handled by the CPU. If you are having trouble with some cores not being used at all then ensure that your core parking is disabled.
2. Only a couple of GB RAM is being used but that’s no surprise and likely not a problem as the HDD isn’t going crazy.
3. The GPU is stressed. Completely.
And here’s my Fraps report from mid flight right over Dover (just before I crashed – on purpose of course, the overheated engine had nothing at all to do with it;)):
Frames: 1751
Time(ms): 28782
Min: 48
Max: 69
Avg: 60.837
What this framerate report doesn’t show is the micro-stutter which renders this otherwise perfectly acceptable framerate more or less unusable for dogfight over land. Smooth gameplay is absolutely essential in this sort of game since the tiniest error renders you rubbish (and that’s without the help of low FPS or stuttering which ruins precise control).
However, this shouldn’t be seen as a negative comment since apart from this the game is excellent. The quality on max compared with IL-2 is just staggering and the cockpits (which is where I spend all my time anyway) and other planes with the settings described above are just fantastic. Grass? Couldn’t care less. Same for trees, buildings and whatever other framerate-destroying nonsense interferes with my shooting the baddies down! And on this note, play over the channel has much less micro-stutter and is playable right now.
So in summary? My feedback after my first tinker with and English edition is very positive but:
1. Stutters over land make dogfight really hard but it will be just great when it is sorted out (which should happen pretty soon).
2. The devs really need to get multi-GPU and SLI/Crossfire working! Single GPU cards are unlikely to cut it on max.
Realism was set to full and below are the video settings I used (see Luthier’s Technical FAQ (http://forum.1cpublishing.eu/showthread.php?t=19819) about which settings to reduce for maximum FPS effect). Note that my graphics settings were also modified by an NVIDIA application profile which was all default except for:
- CUDA – GPUs = None (i.e. handled by CPU)
- Texture filtering – Anisotropic sample optimization = On
- Texture filtering – Quality = Performance
- Texture filtering – Trilinear optimization = On
- Vertical sync = Force on (I was getting bad screen tear).
http://s1.postimage.org/21m4m203o/video.jpg (http://postimage.org/image/21m4m203o/)
And here is a collage of my perfmon.exe, resmon.exe and EVGA Precision for GPU usage (core breakdown on the right):
http://s1.postimage.org/21m1azb44/collage.jpg (http://postimage.org/image/21m1azb44/)
My conclusions from this?
1. Multi-core is definitely working (no surprise (http://forum.1cpublishing.eu/showthread.php?t=19819)) and the i7 920 CPU, which is not really a fast CPU these days, just isn’t bothered by this game. Yes, some cores are more used that others but there is plenty of CPU to go around. And remember that the physics were entirely handled by the CPU. If you are having trouble with some cores not being used at all then ensure that your core parking is disabled.
2. Only a couple of GB RAM is being used but that’s no surprise and likely not a problem as the HDD isn’t going crazy.
3. The GPU is stressed. Completely.
And here’s my Fraps report from mid flight right over Dover (just before I crashed – on purpose of course, the overheated engine had nothing at all to do with it;)):
Frames: 1751
Time(ms): 28782
Min: 48
Max: 69
Avg: 60.837
What this framerate report doesn’t show is the micro-stutter which renders this otherwise perfectly acceptable framerate more or less unusable for dogfight over land. Smooth gameplay is absolutely essential in this sort of game since the tiniest error renders you rubbish (and that’s without the help of low FPS or stuttering which ruins precise control).
However, this shouldn’t be seen as a negative comment since apart from this the game is excellent. The quality on max compared with IL-2 is just staggering and the cockpits (which is where I spend all my time anyway) and other planes with the settings described above are just fantastic. Grass? Couldn’t care less. Same for trees, buildings and whatever other framerate-destroying nonsense interferes with my shooting the baddies down! And on this note, play over the channel has much less micro-stutter and is playable right now.
So in summary? My feedback after my first tinker with and English edition is very positive but:
1. Stutters over land make dogfight really hard but it will be just great when it is sorted out (which should happen pretty soon).
2. The devs really need to get multi-GPU and SLI/Crossfire working! Single GPU cards are unlikely to cut it on max.