Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by soundslikerust

  1. Yes, turn off mirrors. It's known issue, its performance killer:smilewink:
  2. HTC Vive steamvr reprojection doesn't work properly. I.e. Ka-50, caucasus map, high settings (>11ms frame time), instant action, first mission. When on pause look at console and try to move your head left/right and forward and back - its stuttering like never before:helpsmilie: Maybe its tied to shadows it feels little worse when flat shadows are set i'm not sure. When looking outside (F2) (still >11ms) it seams working better.
  3. just making it instant will help a little and is quite easy to do - we would instant zoom in and out without moving head while zooming. It's essential for WWII spotting/identifying targets!
  4. Yes it's a fish eye from different FOV i think, it's preatty bad..:helpsmilie:
  5. UI Layer settings -> toggle VR zoom - works as slow animation in VR making incredible nausea. Please make it instant zoom and instant zoom-out after key release. Otherwise to be competitive in multiplayer VR users will have to:
  6. Text does not fit in Frame rendering stats tool (ctrl+pause|break) : GREAT WORK GUYS WITH 2.5 RELEASE!:thumbup:
  7. I see you're using Oculus. Can you run DCS with steamvr or you run it with oculus binaries? (of course i'm not asking about installing DCS on steam - just using steamvr binary for starting VR game I heard that some games use it for oculus). I use steam tool to see frame render times for CPU and rendertimes for GPU. You can find it in the steamvr settings. If not you have to find similar tool in oculus environment.
  8. I can't render 90Hz on lowest setting because of CPU with 1080ti waiting for it. Can't measure 8700k but between my 6600k 4.7GHz and 6600k 4.0GHz there was less than 1ms of difference and all cores was about 40-50% utilized. We're looking at DCS - there is more than 24ms CPU overhead in VR to render 90Hz on high settings and 11ms time frame... in other words more than 24 times this 0.7 GHz. I would love to see CPU frame time below 11ms on high settings on 5.5GHz but I have no delusions. It would have to be 10GHz based on my measurements. Or some optimizations but looking at optimization progress from 2016 tests - 2 years ago i'm bettin 10GHz intel will be first there... 2 years ago in this analysis some users found that there is minor impact of todays GPUs for stuttering problems. My measurements show the same. If you can please measure your 8700K - we would see how much better 8th generation CPU is better from 6th. I will link it on forums. I wouldn't count on miracles tho...
  9. I don't think so, you should look into https://forums.eagle.ru/showthread.php?p=3372283#post3372283
  10. Happy to help, Gathering reputation if it's worth a rep :music_whistling:
  11. Started new thread about CPU frame times in DCS here https://forums.eagle.ru/showthread.php?p=3372283#post3372283. o7
  12. I just strated some tests with new DCS versions but looking at todays real botleneck - CPU frame time here https://forums.eagle.ru/showthread.php?p=3372283#post3372283
  13. EDIT: Updated Facts and added DCSv2.5 bench. o7 I want to continue huge work done here but also focus not on fps but on frame latency. Like most of you already know frame latency/frame render times are much more important than pure average fps. With all stuttering and inconsistencies of DCS engine and DCS maps it's frame render time most important statistics. For those who play DCS with Vsync because they don't like stuttering or play in VR it's even more important. For VR every frame has to be pushed by CPU in 11ms time window (90Hz) and for 60Hz monitor it has to be prepared in 16ms window. If not - this particular frame won't be rendered and fps will be cut in half to 45fps(VR) and 30fps(60Hz monitor vsync). Of course i'm omitting g-sync etc. Facts to be aware of: 1. Fast frame render times and good frame consistency is what people perceive as a sense of flying and flying speed. That's why BMS is regared as very good at it - it's just old as hell and has very low frame latencies on modern hardware. 2. In case of VR or Vsync you can have CPU utilization at 40% and GPU utilization 100% and be CPU bottlenecked. It just means your CPU can't push all the data for a frame in 11ms - it doesn't have to be utilized 100% for that. It just will not make it in time. 3. People tend to think that if CPU is 100% utilized on every core Game engine is well optimized - it's the opposite when it's done with work on 30% utilization and waiting for new task it's much better optimized. 4. Yes DCS Game Engine (mark difference between game engine and graphics engine) is CPU bound not GPU bound (less truth in new v2.5 in non VR scenario). Of course you can throw at it 5x supersamplng, 8x MSAA, 5x DSR and much more and you will push the GPU to it's limits (hence 100% GPU utilization in the point 2 above). But when you set lowest settings and start mission you can be restricted by your CPU power because those 11ms and 16ms restriction and it will bottleneck your system. 5. It's highly possible you will have average 70fps with those frame drops and stuttering because fps measurement is just a statistic - temporary fps or average fps but just a statistic. Useless in case of stuttering, flight feeling, fluidity and all of what I focus on here. 6. VR asynchronous time warp/asynchronous reprojection help much in case of dropping to 45fps but will break flight feeleing and in case of infrequent drops it will be unpleasant stuttering of game objects (not your view). 7. In VR if you drop to 45fps your head will still move with 90fps(see above) but ground and all objects inside game will move 45 fps (every second frame) - hence frame jumps and stuttering. Most of it when you fly fast and look sideways (not in front of you) at the ground. 8. Even if you don't use Vsync or VR all of above affects your fps quality (BMS example above) 9. After all tests I lowered my CPU speed from 4.7GHz to 4.0GHz to see what diffrence it will make. I've got about 0.5-1ms more on every test maximum in v1.5.8 tests. 10. You should turn off any affinity bullshit from autoexec.cfg (if you edited that). It can ruin CPU frame time consistency (increase frame time variation). Leave it at default auto (all cores). 11. While testing I changed process priority to HIGH for DCS.exe, vrcompositor.exe, vrserver.exe to decrease frame time variation. I don't recommend setting it to real time because it could impact input latencies or make game unstable (I crashed couple times). But all in all helps coz Windows 10 wants to do every unimportant action while I want to squeeze every ms from rig :doh:. I'm not utilizing CPU 100%, just want to be sure DCS will be first in line. If you use oculus remember that setting DCS.exe higher without oculus rendering pipeline processes can make DCS slower not faster. 12. testing GPU and CPU frame times is the only proper way to tell why those frames you have don't give you expected flight quality. Only way to tell if you should have new hardware. Only way to know if this new CPU is worth the money or not. 13. Someone asked me important question Why do I turn off terrain shadows and cockpit global illumination in prefered settings if it had no impact to performance? It has impact on performance - just not on CPU frame render times. First you need to take care of CPU if it makes in time with frame data than You want to max out your GPU potential but not overload it and make it in frame time. All in all i can't have 11ms in VR so I'm choosing lower than 22ms variant for both CPU and lower than 22ms for GPU. 14. I wanted to know is if it's possible to use DCS without stuttering in 90Hz in VR with current existing hardware. If it's possible - I leave this question to you. *I measured the impact of the DCS graphics settings on CPU frame render times VERY roughly with Steam frame statistics tool while running DCS in VR. Every game graphics setting was tested with ALL others turned off or lowest possible. I've chosen two Su-25 missions which struggle to give good performance on my rig even on lowest settings. I tested simplest possible scenario standing on runway in VR in singleplayer. If this struggles with stable frame times and asynchronous time warp/asynchronous reprojection kicks in than more complicated air battle or multiplayer wont work with stable 90fps. Measurement was done in cockpit (simulation was of course started by clicking start mission). Intel speed step turned OFF and all of possible sys settings to high performance. My CPU is 4.7Ghz watercooled and it's always 4.7GHz without any boost/ jumps or anything. My Rig is in my footnote. With hardware I have i'm not GPU limited but CPU limited. I hope my work will be useful to you. I will update it with 2.5 stats. DCS - in VR NVIDIA 386.69 Simple analysis: DCS - in VR NVIDIA 386.69 Simple analysis: DCS - in VR NVIDIA 386.69 DCS - in VR NVIDIA 386.69 DCS preferred settings for VR
  14. That's why your GPU is utilized 100% - Run a Vr with static time for every frame, get it to 4k and it will change to cpu bound. CPU can be utilized 30% and be a bottleneck at the same time just because game engine can't push frame fast enough. You forgot what is really important here - not your average fps but a frame time. With all stuttering and inconsistencies of DCS engine and DCS maps... No matter what you do there will always be places in DCS where frame times spike above 11ms wchich will crush your useless average 144fps. I have the same card as you - frame times and latency are the most important problem to solve. Vulkan can change everything in case of draw calls. Let's hope that it will get stable frame time in less than 10ms no matter where and when. It would be great. Latency is what people perceive as a sense of flying and speed. That's why BMS is regared as good at it - it's old as hell and have very low frame latencies. o7
  15. Every video on 2.5 i saw has strange green water shader is it a bug? EDIT: example
  16. Watch out for new NVIDIA drivers, 375,86 WHQL, killed my performance to 20% http://www.guru3d.com/news-story/nvidia-geforce-375-86-whql-drivers-have-major-issues.html
  17. :joystick: Watch out for new NVIDIA drivers, 375,86 WHQL made my rig a potato with 20% nominal speed. http://www.google.pl/url?sa=t&rct=j&q=&esrc=s&source=web&cd=4&cad=rja&uact=8&ved=0ahUKEwjogauZq7DQAhUDlCwKHSQkBKQQFggmMAM&url=http%3A%2F%2Fwww.guru3d.com%2Fnews-story%2Fnvidia-geforce-375-86-whql-drivers-have-major-issues.html&usg=AFQjCNEzxKCcICozXQBr0A10xJC62GRIrw&sig2=GAX7qObg5B2pF0o8HJjrTg
  18. What in-game greaphics configuration do you use? Do you use rendertarget multiplayer? I have 1070 but can't say it's "great" when i fly over cities or use medium settings
  19. I have the same problems with FPS since the latest update
  20. I can fly around, look around with big cities, trees, buildings with 90 FPS. Then there are places like this one pictured on pause. Game is paused, i'm rotating my view/head towards ground... Could someone help me with this situation... ??? WTF:huh:
  21. ouch not nice, your background is fine, you wont know mine anytime soon because its not facebook. Our expertise is not a main problem here. Thanks for your opinion
  22. i salute you mate, really I appreciate knowledge, i've some background too but it seems ED proved you wrong already.
  • Create New...