Gunnars Driver

I have 90 forv lot more time when looking up in the sky. This was a test to see if OP system was able to produce 90fps, when GPU and CPU framtime is low enough. As fpsVR not do count other software that may consume time thus the total fram time could be more than shown in fpsVR, it should be a good indicator i something else is disturbing. I just flew a own multiplayer mission as the host and fot the over sea part and all high altitude parts, I had 90fps. I enjoy 90fps as more smooth than reprojection at 45. So for me auto is the natural option. BTW, In my case I get 90fps as soon as GPU/CPU comes below 11.1 -just tested it, to be sure. I do only need to get down to 11.1, not lower. And it happens at the same time, it do not take time to change either.

The first setting off course had made effect earlier but the change to auto did not seem to have effect. I Think we where well below 11.1ms ( dont remember the exakt numbers) with the nose pointing up and seeing only blue sky.

I thought so also, but it didnt seem to make any difference. One possibility is that there is more than one default.settings, and we did change the wrong one. The FPS was fixed to 45fps even when having both GPU and CPU fram time well below the 11.1ms limit, Flying around and looking straight up still hit 45fps. The setting was “motionvector“ and after changing to “auto” still only 45fps. I also saw posts earlier in this forum where they say that changing settings had no effect. Do you know what happens if you dont have the “Beta” activated? At vr4dcs it say “you must have the Beta installed before proceeding” Looks like it says that without the Beta selected/installed you couldnt change these settings ?

So, dukman83 and I did some tests last night. Settings tuned down, DCS run smooth. Tuned up to my settings but SS still at 100, also smooth gaming in F18 quick mission. GPU frame times similar to mine. CPU frame times, a few ms higher for dukman( like 9-10 for me and 11-13 for dukman). Afterwards dukman played multiplayer and after a while the CPU frametime did rocket up to ~40ms. Despite this, fpsVR seems to have reported CPU Maxthread 40%. FpsVR only counts the processorload / processortiming connected to DCS, so there might be some other processes that loads the core that DCS use. Still left to check the bios settings, that the 9900KS is doing 5Ghz on all cores all the time. Also to check that no other software loads the CPU cores that DCS uses. In this case, reenabling HT might be good to get more cores to spread other processes on. Dukman has the Steam version of DCS and it seems like the changes in the default.settings file actually not do affect reprojection. Anyone know if steam have any override or own setting for this?

Thanks. Off course, I willing to learn from others and their settings to make my gaming experience better if possible.

I havent done any mods at all, no shader mod, no Lasso etc and I rund the 9900KS at 5.2Gghz with HT on(as I use the computer to a lot other software that actually benifit from HT). Still interrested in your settings, I might learn from them. I did shoot a short Movie from F18->free flight->Kaukasus: turned around, descened and passed the North bridge end South Batumi on heading 030, altitude 250feet. Enganged ATT-mode on AP and looked straight ahead and to the sides. This will show my fps, GPU and CPU timings. "My DCS-settings" with SS120%. It would be very nice to see the same from you. Of course, as 60fps youtubevideo can not reproject 45 or 90fps correct, it wont be a smooth video. The stutter seen can be interpretated as the same all the time, due to 45/90fps on 60fps Movie. fpsVR is in view also. If I do this run in SS150, the gaming isnt smooth anymore. Even if fpsVR shows loads below 22.2ms

Im interrested in your complete settings. Nvidia CP, steamVR and DCS. Preferably print screen pics for easy copying to my settings. Confirm that your SteamVR reports 100% = 2204 x 2160 pixels, and 150% = 2700 x 2644 pixels? There have been different numbers for 150%, because of this, the question. Folloving the Thuds guide at VR4dcs.com guide and steamVR in Beta should give these numbers. If using the other/older version 188% = native and then 150% is quite low. 2700*2644 times two screens isnt that low. If I make the calculation correct it sums up to 5400*2644. I will help OP online to try to fix the problem. If OP have a problem and I try to tell him that he should lower the SS due to bad fps, we shouldnt tell him that SS150% is not a problem. Because it could be part of the problem, we do not know that yet. So, generally it should be a bad idea to tell OP that 150% is no problem at this time.

Yes, it might be either a difference in computer performance or a matter of personal preferences*. —> This makes my case; for the matter of this thread 150% is/can be a quite high setting and therefore we should not tell the OP that its a low setting that cant give you problems. I have learned from 20 years of Home Cinema hobby that there is a big difference in how people percept the stutter of movie not running in perfect frame rate. I am above average sensitive to non smooth gaming, or non smooth movies. Probably a result of 20 years of home theater PC tuning :doh: Anyway, the settings also matters. I wouldnt like to lower the settings and try to make a low settings picture sharper with SS.

I have the same CPU, GPU and same amount of ram. Also dual nVME m2’s. After the setting test shown above I reverted to my normal settings( including SS 120%) I had smooth gaming and never below 45fps. When rising it to 150% I get a lot of stutter and it isnt a smooth experience any more at least at low level flight. I notice stutter even when fpsVR and/or dcs shows 45 fps. This in the same F-18 mission ready on the ramp. Multiplayer etc is harder so for me 150% is a clear nogo. My 9900KS and RTX2080ti 11Gb (ASUS ROG STRIX OC) isnt up to deliver enough power at SS150%.

I did make some screenshots for reference. I did lower the CPU Clock to 5.1, just saw that you dukman seems to run at 5.0Ghz, not much of a difference so I didnt retake them. Settings: SteamVR at 100%, rendering resolution 2204*2160: [/img] Framte rates and processor loads: F18 Ready on the ramp caukasus: This is just after boot, flying give me GPU frame time around 9ms and CPU around 8-9. After flyging for a few minutes the average fps is closing towards 90fps. [/img] Not fun at all to fly like this, and it is not the meaning either. It it to check wheter it is possible to get the CPU load and CPU frame times down. If not, there is something we need to fix. After check, and possible problem fixed, the settings should be a lot higher :-)

The guys i play with did use skype earlier and I did never notice a problem. We changed to Discord a couple of years ago so for the last years I dont know. Good tip though: All possible issues should be looked into, to be able to find the issue and get it running.

I havent used affinity mask/shaders mod as I get fine fps and decent picture( readable instruments and high or ultra in the distance setting). I did consider it but a friend tried it (using Oculus Rift) and he had no or almost no gain. I was told that you have to re-do the shader mod after each update. No/low gain and ‘lot of work’ made it a nogo for me. I also wouldnt like to risk to trash a very good working setup. I think DCS should get the shader mod implemented by Eagle Dynamics, it seems like an easy way to lower the demands for VR. I can lower settings to get 90fps for more % of the time, but as reprojection work as good as it does, I mainly use the settings to ”never” go below 45fps = means I have smooth gaming all the time. I think you should lower the setting just to see that the CPU isnt loaded too much for comparable settings/comparable hardware( ie processor times below 11ms possible). This to find out if it is only too high or wrong settings or if there is a major c**k up in your DCS installation or somewhere else. When fixed or when knowing there is no problem, you should work with the settings to find your personal setting level, ie the compromise between high fps and picture quality you want. You can not get constant 90fps with high settings - it is not possible. For me, the goal is to always stay at or above 45fps(never see it drop below). This ensures smooth gaming. Reprojection- I use the automatic setting, this give me 90fps when the computer has the power for this and 45 fps when it dont. I dont really see any other numbers(except for the brief transition between 90 and 45). The fixed 90 or 45 is a receipt for the automatic switch. I could help via discord or skype to try make the correct settings and make sure reprojection work as it should. Arriving at home tonight and I will be off work for one week so I think I have the time.

I have not changed any settings for processor cores( stock DCS setting ). I use hyperthreading, as DCS isnt the only software I run. Virtually most other benefit from HT. I havent messed with project lasso. I havent messed with shaders mod. All of these (except not disable HT) isnt done because I get performance good enough to enjoy gaming and I am happy as is.

Nope. There has to be something wrong, if you did lower all settings and it still dont get decent fps and cpu frame times. Here is two videos, I shot these for another forum member that has stutter problems. First I made videos with my normal settings( at 90 fps and sometimes 45 reprojection). Those do nit come up smooth at youtube due to that filming 90fps with 60 will cause unsmooth playback. In these, I did set the reverb to 60fps, smooth gaming mostly, It may be some reprojection causing 30 fps reprojected wich I find to unsmooth for enjoyable gaming. My normal settings (90fps and reprojection when needed) feels smoother. Shot with gopro trough one of the lenses in the Reverb: Shot with nvidias tool (captures the desktop display): We have similar hardware an got similar points on the VRMark. We should get similar frames per second if we have the same setup on steamVR and in DCS etc if everything work as it should. I didnt update to 2.5.6 BTW, because of all the problems. As most already sad, roll back to 2.5.5.

A good plan! I think one main goal should be to see if you by lowering the settings can get down to decent CPU frame times that’s comparable with other ppl with similar hardware( I think you should be able to drop it down to around 10ms). If this isnt possible, there might be a problem in either DCS or maybe Steam VR software. As VRMark use part of the same software(Steam), it then might point out DCS. This should result in either needing to do a new install of for example DCS or steamVR software etc, or if no such problems, start from the ”bottom” with low settings and work yourself up increasing settings step by step until you meet the limit between your hardware and your own personal reference for what you think is a playable level of smooth gaming / enough picture quality. We know that we cant put all settings to max +high SS and still have 90fps/45fps all the time. [Edit]I think it would be interresting to see the load on each core of the CPU during DCS gaming. You fint it via the Task Manager and system recources or somethinh like that(not at home so...). Heres a post with this shown for my computer, I think that pic is when I used Oculus. With Reverb I get higher GPU load and a bit lower CPU load. The load is on the highest numbered physical CPU core in the system by default in DCS. Some load will be on the next highest core(I think its mainly the sound processing). We excpect to see a similar pattern in your system if everything is as it should. By the way, you havent mixtured with project lasso or in anyway hampered the standard DCS threads-to-core-settings? https://forums.eagle.ru/showpost.php?p=4163309&postcount=288

Exactly. The Reverb is prepared with a outlet for other headset speakers so a change to better audio is very easy to do. I havent done yet but as I dont find the reverbs sound top notch I think it is a good easy mod.

Thats a good start! The VRMark test shows that your hardware, windows and drivers run as they should. No probs there. ( Traveling, using phone so I didnt managed to really see the other pic.

With the settings presented in OP at least my 9900KS/2080ti takes a noticable hit from SS150%. I say that still you should make sure the hardware and windows works as it should. Steam have a free version of VRmark( https://store.steampowered.com/app/464170/VRMark/ ). I think you only can run the orange room for free, but it will show if something is major ****** up. I get around 14300p with 9900KS@5.2 and the 2080ti a bit overclocked. I think it was around 13700 with CPU@5ghz and 2080ti at stock speed. You should get somewhere around this value. If the result is much lower there might be a graphic driver problem, or something like that. I still, for test, suggest lowering the SS to 100%. Increasing the preload radius to max, reducxing the tree visibility and cluttder grass to a quite low value. Also, terrain textures to low, lower visibility range to lowewr than ultra. Shadows takes some performance so Id say ”flat” for the test. Smoke and chimney to lowest and anisotropic filtering to off or 2x. About fpsVR: We dont see all stuff that load your CPU, but if you get a very high number on frame time on fpsVR, it has something to do with the DCS and/or VR software. Cause other tasks dont get into the fpsVR counting. Im away from home but with my settings I hade reached around 10.7Gb in the videocards RAM and for some gaming around 26-27 Gb of RAM, still with no problem at all and smoot gaming: %5Bimg%5D[/img] For VR + DCS you can not just put every setting high and think it will run smooth even with the best hardware. If not trying with low settings that we know should work fine, you might end up newer seeing the real problem. Im a also a bit suspicious about some of the override settings in nvidia control panel. Some stuff might load the CPU, despite you dont think it should.

If you like to have the frame rate mostly over 45fps, 150% SS is quite high, even with that hardware and 2.5.5. Suggest to make sure the H/W+windows works as it should and after that use low settings to see that the framrate is close to what we other get.

I have close to the same hardware: 9900KS@5.2 2080ti overclocked 32Gb@3200. Two 970 sticks, one for OS and one as game drive. I would start with checking the computer itself, it may concern hardware or BIOS settings and also trouble with drivers for GPU etc. Easiest way to check it all might be a test like 3d mark or something like it. Next thing(when hardware+windows & drivers are secured, I’d lower the settings to se that it can run ok on low settings. If it cant, DCS might be broken. Supersampling takes a lot of power so just should start with 100%. Pre load radius in DCS should be maxed out, it makes the work easier(not the other way around). [Edit] I havent disabled hyperthreading as I use the computer for other demanding purposes where its good. I have quite good fps. We could help with making reference tests like 3d mark or something like that.

Is that the one RAF made a video about? (Maintenance error and hard pressure due to upcomming excercise, if I recall it correctly ?) I’ve been shown that vid’ a couple of times in my AF.

This is a absolute valid reason for using other than 1:1 ratio. Earlier in the thread the ability to look straight behind was given as the reason, in the context of not being able to look as far back as IRL, which isnt really true. And when in a dogfight you do not fly mach 1.X so pulling G will give you a descent alfa. This moves the following aircraft from straight behind to a up behind position. The turning radius will move the follower further in the same line, and when you add a bit of roll when trying to evade you have the follower far away from straight behind and you do not need to twist the neck 180 degrees.

Recording of one frame rate with another that is not a multiple of the former will induce un-smoothness. The lower the frame rate and the smaller the difference between these to framerates the worse the not smooth movie will result. I tried filming 90fps vr with 120hz gopro and it made it better than regular 60fps but there still is introduced non-smoothness that isnt there when looking in the VR for yourself. I made a test and did set the Reverb to 60fps and recorded this, and result was perfectly smooth movie as long as the frame rate was kept at 60(enough computer power to keep 60). Suggest using this tecnique when showing a ”non stuttering VR setup for example on youtube.

Seems like you use similar settings as I do. Not exactly same but rather close. I recently raised the supersampling to 120%, I could to this without any noticable drop in frame rate when using reprojection( still almost never below 45). I have bo ghosting and no stuttering at all. The raise to 120% gave me clearer/sharper cockpit instruments etc. I found 150% to do very goid things for sharpness but it was an a cost innframe rate so it wasnt possible for me at current settings. One tip, when I started testing SS above 100% I made the settings both on the general steamVR setting and also on the per application specific. This multiplied the SS, 150 on both resulted in 225%, and low frame rates. Feels like a bug, and important to know when testing settings.

VKB looks ok if you raise them, no brakes though. Not a problem for skid helos, if you only are into that.