PicklePicklePickle

Ok, that might be it. I believe I can see 'him' typing coordinates in the TID repeater, so maybe if I look at these I can tell if he is typing the same coordinates from the original INS alignment. Not sure how the INS alignment would know the parking location is wrong...if the coordinates are wrong I would just expect the INS alignment to be incorrect, not stall.

Been there, done that. Made no difference in my system, but thanks for pointing it out. I have tried enabling motion smoothing(I believe = SteamVR's reprojection) but it just seems to add new 'wavy' artifacts on top of the existing stutters/ghosting, so overall worse experience.

Just wanted to say, same problem here. With any reasonably good looking settings, likes to peak right around 45fps although I use PD 1.0. This is with reprojection turned off. it always stutters randomly when I bank and look out the side of the cockpit. I have tried absolutely everything I have found except modding DCS. Also, even in the 'bursts of smoothness' between stutters, if I bank at just the right rate I see doubling of features in the terrain. HP Reverb G2 set to 90Hz. Specs: Xeon W-10885 up to 5.3GHz, 128GB, 1TB Samsung 980Pro SSD, RTX3090 eGPU

Thanks everyone for the useful input. I think one reason it has been confusing, is that in my tuning with all reprojection settings turned off, 45fps seems to be where it likes to peak and it is very hard to get it go over that. When I start moving the airplane it goes below 45, and sometimes I see it flash 46 or 47fps, but for example when the free flight cockpit comes up and the window is being displayed, it is right at 45. Because of this, and the fact that fpsVR shows non-zero reprojection ratio, I thought it must have been enabled but it seems to be not the case. if I reduce all the settings to the lowest(and PD=0.5, 20% resolution in steam VR) I still don't get 90fps, I get something like 60's, and I don't get why because fpsVR is green and the 'frametime' is low enough for 90 yet it doesn't achieve it. My system is unusual, so maybe this is because of the eGPU 22Gbps bottle beck(specs below) I will try setting it to 'Auto' in WMR. When I tried the reprojection before the new artifacts(occlusion artifacts?) where very distracting so I turned it off. It's not so bad at 45fps, if it weren't for the micro-stuttering when banking and looking out the side. There are streams of frames where it is perfectly smooth, but then it randomly stutters so you see the terrain jump. I also see ghosting(doubling of terrain features) when banking at a specific rate and looking out the side, but this is less distracting than the stuttering. I tried the hotplug change and everything I could find but no luck on this. Xeon W-10885M 2.4GHz-5.3GHz (Thinkpad P17) 128GB of RAM 2x Samsung Evo 980Pro (DCS is on system drive) RTX3090 via eGPU RTX5000 built-in but disabled during DCS

Thanks for the replies...yes it is when I have to repair(i always catch some shrapnel ) and shut down. I tried leaving the power and air on after seeing a mention of this being required in Chuck's guide, and the same problem occurs. The alignment gets to 64-66 and it stops. I can only get it to work by asking Jester to do the 'NOW' option which is mostly useless. Maybe it is because I landed at a different airfield than I took off from? Or maybe it is a bug.

Hello, Whenever I start a mission, the INS alignment through Jester works fine. However, if land again to rearm, after engine start it seems Jester starts INS alignment without me asking. Often, the alignment gets very close to the end and then gets stuck there. This seems to happen if I let Jester start the alignment automatically, or if I ask for the fine alignment via the menu. I am forced to select the 'INS NOW' option which breaks the hud for dropping bombs, among other things. Is this a bug or am I missing some part of the real procedure here? When I land I always set the parking brake first, which I know can interrupt the INS alignment. Thanks!

Thanks for that hint! I did not know you could use OpenVRSettingsUX.exe, breaking out the right controller is a pain. However, fpsVR still shows a non-zero reprojection ratio. I've tried disabling it in OpenVRSettingsUX, and i've also tried setting it to use the SteamVRSetting and disabling it there. Clearly when I enable reprojection I can see new artifacts, so the setting is working. It must be that this is a problem with fpsVR, and it shows a non-zero reprojection ratio even if reprojection is disabled. I found a note by one of the developers here, however it seems to imply that reprojection ratio will not take into account the WMR motion reprojection, so still not sure why it is non-zero: fpsVR Q&A :: fpsVR General Discussions (steamcommunity.com) "Yes, It should work with WMR(not tested on a wide range of testers), "Reprojection Ratio" counter will not take into account reprojected frames made with "Motion Reprojection"(WMR feature), because it is not a part of SteamVR."

Hello, When I use fpsVR with the standalone DCS and the HP Reverb G2 (on an RTX3090), I always see a value for 'Reprojection Value', usually close to 50% even though I have disabled it. I have done the following to disable it: Disabled it in WMR options using the right controller menu in SteamVR home Disabled Motion Smoothing in the DCS Application-Specific setting confirmed that it is disabled in default.vrsettings file It seems that if I do these, then the reprojection ratio should be 0 in fpsVR and I should just see the 'native' fps, stutters and all. Can anyone explain this, or correct my thinking if i'm misunderstanding something? Thanks!

Thanks, that's what I thought as well. I started with DCS_Updater.exe because when I looked up how to add DCS to SteamVR I read someone else added it that way. However I then also added DCS.exe and it still has no effect. I tried changing the application-specific render resolution dramatically in steam VR for both DCS_Updater.exe and DCS.exe and nothing changes. Only the global setting has effect. So I haven't been able to play with the reprojection and motion smoothing to see if it fixes anything. I'm launching DCS from the Steam menu, so I don't see how it doesn't associate the two, maybe it's a bug.

Thanks for all the replies and different perspectives. I actually just received an upgraded machine unrelated to DCS, so luckily I got to try DCS on the new system with a clean OS. The specs are 128GB of RAM, Xeon W-10885M which boosts up to 5.3Ghz, 2x 2TB SSD and the RTX3090 eGPU. I benchmarked the new W-10885M CPU with CPU-Z and single thread it gives a score of 565. This seems to be pretty close to the top end i9-10900K based on the CPU-Z reference page: https://valid.x86.fr/bench/1 But I don't know how trustworthy this benchmark is. Anyway, there is a noticeable but not huge improvement. I can crank up the detail a little more and get the same FPS as I got on the E-2186M machine. I did notice that now fpsVR doesn't say the CPU(or GPU) are maxxed out i.e. the plots are not going red, but it is still not getting past 45fps, once in a while it'll show 46fps but that's high over water. Once I start moving it drops to the 30's. It is very possible that the difference in my system between those that posted 90fps experience like bignewy is twofold: 1.Bignewy has i9-10900K which I believe can run at a sustained higher clock rate than the W-10885M I just tested 2.I have the 22Gbps bottle neck via Thunderbolt 3 to the eGPU, which could be a bottle neck if the RTX3090 were moved to a motherboard I did also confirm, that disabling "CPU Power Management" in the BIOS also gives back a few FPS, it seems DCS prefers a consistent clock rate than a variable clock rate, even if the boosted clock rate can momentarily go higher. Of course, based on the great performance I've seen of other modern VR apps, the core issue is DCS not being optimized for modern hardware so can't wait for that! One thing I can't explain: I added DCS World(DCS_Updater.exe) to Steam VR and I start it from the steam tray menu, however the DCSWorld 'Application Specific Settings' in steam VR have no effect. For example, I can set the app-specific render resolution to 500% and it changes nothing. The global setting works of course. I also added DCS.exe and had the same problem.

I checked the clock with CPU-Z while DCS is running and it fluctuates between 3.8GHz and 4.8GHz. However, today I experimented with turning some settings on/off in the BIOS. Hyperthreading or speedstep didn't have any effect, but turning off 'CPU Power Management' did. It makes the CPU clock at 4.2GHz consistently, and it gives me about 7 fps more. The other potential bottleneck(although fpsVR says it is the CPU) is that I am running the RTX3090 as eGPU. I checked with CUDA-Z and my system can max out Host2Device bandwidth at 22Gbps over thunderbolt 3, but I do not know if DCS actually maxes this out such that it would benefit from more than 22Gbps. I haven't found any tool that lets me monitor the actual thunderbolt bandwidth while DCS is running.

DCS VR newcomer here. After flying the Heatblur F-14(masterpiece!) in 2D, I got an HP Reverb G2 and a RTX3090 just to run this. My machine has SSD's and 128GB of RAM. I tried other games like Alyx and everything seems to run pegged at 90Hz on ultra settings. Tuning DCS has been frustrating. I have done:: Gamebar/mode off, disable FS optimizations, DCS to high priority, GameDVR regmod, rebuild shaders and bignewy's settings. None of them seemed to change anything, except when I rebuilt the shaders for the first time after replacing the graphics card which didn't increase fps but did make the fps more consistent towards the higher end of the range I was getting. After days of experimenting with every setting under the sun, the best I can get with good image quality(being able to read the F-14 altimeter thousands) is 25-35fps, and it seems it is doing the 45fps reprojection thing because it seldom spikes above 45 when I try progressively reducing the settings. The only times it goes 90fps is in the main menu with really low settings or the DCS loading screens. Out of frustration I tried setting everything to 'potatoe' as low as every setting goes, including PD 0.5. This ungodly pixelated mess still doesn't hit 90fps and fpsVR says it is CPU limited at around 50-55fps. I have a Xeon E-2186M, so I am concluding that a big part of being able to reach the quoted 90fps is having a very fast CPU, as in my case I have everything else maxed out(GPU, RAM, SSD). This seems obvious in retrospect but just to underline what others have said about CPU.