ShaunX

Exactly. If you select "Motion Vector" in the WMR for SteamVR settings then it's locked on for all your apps, if you select "SteamVR per app Setting" then you can set it individually for each app via the the SteamVR settings. That's the only difference.

For a WMR headset, the SteamVR settings just allow you finer and per-application control over WMR for SteamVR motion reprojection. It's not a different algorythm. The choice you have is between Auto, where it will only cut in if whenever you can't maintain 90FPS, or Motion Vector, where it constantly attempts to maintain 45FPS with reprojection. extract from Microsoft .. " Windows Mixed Reality for SteamVR has an experimental motion reprojection feature to make 90 FPS reprojection more smooth. When motion reprojection is enabled, all Steam VR games will render nominally at ½ frame rate (45 fps instead of 90 FPS) while Windows Mixed Reality for SteamVR uses motion vectors generated by the GPU to extrapolate the next frame. For SteamVR games that reliably hit 60 FPS+ on a given PC, this should result in a solid 90 FPS experience with occasional artifacts while maintaining a comfortable experience. The available motion reprojection modes are as follows: SteamVR per-app setting: Allows you to control motion reprojection through the SteamVR Settings UI. You can then open SteamVR Settings, go to Video > Per-Application Video Settings, and select an option for "Motion Smoothing." Auto: Enables motion reprojection to turn on automatically when a game is rendering too slowly to maintain 90 FPS. When a game begins to maintain 90 FPS or starts rendering at less than 45 FPS, motion reprojection will turn off. Asynchronous rotational reprojection is enabled always. Motion Vector: Forces the application to always run at half-framerate with motion vector reprojection. None: Disables motion reprojection. https://docs.microsoft.com/en-us/windows/mixed-reality/enthusiast-guide/using-steamvr-with-windows-mixed-reality " Personally, and following the DCS clouds release (and the fact I like to run with msaa x 2) I always have it fixed on at 45FPS.

Just a thought. Do you have motion smoothing set to "forced" or just "on" ? If it's just "on" then if frametimes go down enough as you gain altitude it'll try to flip from 45fps to 90fps and I guess that might cause your jelly hud somehow. Particularly if it then constantly flips between 45 and 90.

Had some visitors this week (VR & DCS virgins!). Sat them in my pit with the G2 and let them experience a track file I made of your "Sunset Cruise with RAF Tornados". Blew them away!

There is actaully a very accurate method of benchmarking in DCS for VR. I got this method from Speed-Of-Heat's's excellent 3090/G2 thread and use it all the time. It does require FPSVR. 1. Fly a simple mission, quite low over some mixed terrain for perhaps a minute or so. Save the Track file from the mission. That's your baseline file. 2. With your Headset on it's stand or hook (Not on your head). Launch FPSVR and DCS in VR mode. You MUST run this process from your PC screen so that your headset view doesn't change. Obviously press the VR recentre button so you have a centered view on your screen. 3. Make sure you turn motion smoothing/reprojection OFF (otherwise you'll just see mostly 45FPS in the results) 4. Launch the baseline trackfile in Replay. 5. As the replay starts click CTRL+F11. This initiates FPSVR capturing FPS and Framerates every fraction of a second. 6. When the track finishes, press CTRL+F11 again. FPSVR will write the results to a csv file. (The output folder is defined in FPSVR settings). For a minute long track, the file will have between 7000-10000 rows, a pretty decent sample. 7. Open the csv file in Excel. You'll need to trim off rows at the start and end of the file where the rate was settling and after the mission ended. It'll be obvious how many to remove by their values. 8. Use edit/replace to globally remove all the " characters from the file (otherwise calculations won't work) 9. Use =Average to take average of the FPS, GPU framerate and CPU framerate columns. And there's your benchmark results. I usually run the track file 3 times and take the average from the 3 runs. Now make your changes and rerun the process. I find this gives really accurate deltas between any changes I make, mods I add, or between DCS OB updates. It's a little cumbersome but once you've run a few times it's easy to repeat. If you're looking for an extreme stress test, obviously create a more complex mission/track file (or just fly Marianas )

I think "ticks" was just a reference to other apps/processes which you might be running and which might cause some framerate hits or stutters. I don't get this at all on the hud with motion reprojection fixed 45fps and fsr & Sharper Eye. That doesn't sound right. Are you possitive you have sharpen = 0.0 in FSR ? Are you on FSR 1.1 ? I actually only switch FSR on if I need it. If I'm practicing or just sight seeing it stays off. Yeah, forget 90FPS especially since the new clouds and if you want msaa x2. I'm always locked at 45fps. Without the lock I get too much ghosting looking sideways.

You have pretty much identical hardware to me (see my sig) and I fly with pretty similar mods, FSR 1.1, Sharper Eye and VR Shader Mod (clear water), though regarding shadows, in DCS I have shadows low and terrain object shadows flat, and then use "Mustangs Flat Shadow removal mod" to only retain cockpit shadows and "Shadows Reduced Framerate Impact" mods. I have Motion Smoothing forced on and hold 45FPS in all but the most demanding situations with high graphics settings. I would certainly never see a dip below 45FPS or experience stuttters on an empty PG map. Have you been through Speed-of-heat's 3090/G2 guide and applied all recommended hygiene changes ? I recently found that following a DCS OB update where I didn't empty fxo and metashaders2 folders before reapplying kegetys clear water that I noticably gained frametimes (even though it has been documented that you shouldn't need to do that). Maybe try removing all mods (I assume you're using OvGME?), run a full repair, clear fxo and Metashaders2, reapply mods and then run DCS to rebuild all the shaders. I would also suggest dropping SS to 80%, which is what I think most of us G2 users use. I can't tell a visual difference between 90 and 80%

@zaelu, @-Dagger-, As stated above, what you are looking for is entirely outside the scope of this particular app. Please re-read the description of what this app does. I'm sure your ideas may well be feasable but I'm afraid I have no intention to rewriting this app as an internet radio station player. If that is what you're looking for I suggest you start your own thread on that subject. Thanks.

What you're asking for would require an entirely different app.

Just upgraded to 2.7.6.13133 Unfortunately your trk file now nose dives again into the deck before it get the chance to level out to head out to sea. From what I've was able to capture before then, with the hotfix installed, looks like a small degradation from my hotfix runs in 2.7.5 above Averages from 3 runs GPU Frame Time: 11.05ms CPU Frame Time: 6.53ms I guess some of that may also be because the closing 10 seconds on the original are level flight with mostly sea and sky. Also notice that average GPU usage seems to have dropped from 92.5 to 90.9

still on 2.7.5 as I may as well wait for the next release today.. Thought I'd run your hotfix version against 2.7.5 to compare it against be above clear water regular version.. Regular Clear Water x 3 averages GPU Frame Time: 10.49ms CPU Frame Time: 6.43ms Hotfix Clear water x 3 averages GPU Frame Time: 10.56ms CPU Frame Time: 5.95ms So looks like good news and maybe even a tad less taxing on the old cpu ?

I set up key combinations in DCS for the UFC A/P function selector and then one for UFC option push button 1 and one for UFC option pushbutton 3 (1 is for attitude hold, 3 for barometric hold) I then use a Voice Attack keyboard macro for each combination, which firstly presses the A/P selector for .3 seconds, then the option button to engage it. I've assigned Attitude hold to China hat forward and baro hold to back. Autopilot release is already mapped to your nosewheel steering disengage button. Note that If you engage baro hold while flying close to level flight the A/P will level you out perfectly and hold that level attitude, even if you're asymetric. Not sure if that's true to life but it sure is useful

Join the club! Try Necksafer, originally developed for that other sim but works very well in DCS if you're using SteamVR https://forum.il2sturmovik.com/topic/67985-simple-tool-to-check-your-six/

Sorry, I'm confusing things. I always run with Kegetys and a couple of Mustangs mods for VR performance, so when I update the game I remove them first via OvGME, update the game, reinstall the mods and run the game. It then takes ages to rebuild the shaders for each terrain and resource specifically for kegetys. What I've noticed however, is if I don't clear fxo and metashader2 before that I gain GPU and CPU frametime. It may be soimething specific to shaders for Kegetys and Mustangs. If I then clear those folders and rerun the game, frametimes are restored when the shaders rebuild.

..even when you reinstall mods like Kegetys and some of Mustangs ?

Have you tried clearing out fxo and metashaders2 and allowing them to rebuild again? Definately slows me down if I don't do this with a DCS update.

Thanks, retested x 3 with that trk in 2.7.5 GPU Frame Time: 10.49ms CPU Frame Time: 6.43ms Slightly less performant perhaps due to your carefree aerobatics. You could have easily taken a Georgian village offline had you clipped those power lines

Having survived my culinary ordeal (no heels available for my size 12s unfortunately) I thought I'd take a baseline before downloading 2.7.6. to see if there's any performance loss with the hotfix. I actually resurected your original performance track.trk which I'd used immediately post 2.7. Admittedly it now nose dives into the trees but not for about 30 seconds which is enough to collect decent FPSVR stats. You may remember in your 3090 thread I managed to post averages GPU Frame Time: 9.73ms CPU Frame Time: 6.23ms Well to my horror, and with identical settings (Test 26) and mods - clear water,reduced frame rate, flat shadow removal, no FSR, no reshade, reprojection off I measured averages: GPU Frame Time: 11.7ms CPU Frame Time: 6.68ms Spent the rest of the day tinkering to no improvement. However, this morning I ran a full repair, deleted fxo and metashaders2 and shazam.. GPU Frame Time: 10.27ms CPU Frame Time: 6.04ms (I reckon I can account for the slight average GPU increase because your original trk ended with a 10 second level flight seawards rather than a nose dive !) So I'm wondering if I forgot to delete those following the last upgrade I did. Just goes to show it is still worth doing! Won't get the chance to upgrade to 2.7.6 for a few days now but will report back when I do.

That's all I'll be wearing

Say no more mate, and feel better soon. I have somehow been roped into doing the cooking for my wife and her cronies visiting us today, for an afternoon soirée which I am (thankfully) not invited to, so I should get a chance to do some testing in the servants quarters while they drink and all talk at each other at the same time

Thanks man! I haven't even had the chance to download 2.7.6 yet and you've already fixed this ! Any performance differences observed ?

If you already use Voice Attack, it also has functionality to easily assign keyboard sequences to all joystick buttons and switches, including assigning seperate functions to the engage and release of each switch. So it's very easy to assign on/off to 2 way latched throttle switches and function 1/off/function 2 to 3 ways. (It also support long/short press assignment) I use DCS setup for momentary buttons and Voice Attack for any latched switches on the throttle I want to assign for a particular aircraft, which works nicely as you can have a seperate VA profile for each aircraft and switch between them with a voice command.

The new Elecom trackball arrived from ebay today. Here's what you can do with a spot of hot glue. There's less than a square cm of contact between the trackball and the joystick and the bond is absolutely rigid. Easy to remove too and doesn't leave any residue when you peel it off. Trackball is much better than my old one and the 10 fully programable buttons and scroll wheel make this a winner for me. Thanks again @VFGiPJP

From what I've seen it certainly works in DCS, but not with enough accuracy yet, and there's no way to create dead zones around your physical HOTAS so you can inadvertently operate controls while using the HOTAS. I can see it being the perfect solution in some distant iteration. Checkout Youtube vids of VTOL VR which was designed to use it from the ground up.

VR sickness is temporary and just occurs because your brain is confused with your eyes telling it that you're rolling and the balance in your inner ear saying you're not. Your brain will work it out and compensate with practice. G2 for me, though some have moved recently to the Vive Pro 2 and highly rate it. The other thing to consider is that even with your rig you'll need to spend some time optimising to get the best experience, but plenty of folks on this forum will help you. Just beware though, once you go VR there's really no going back to pancake mode. VR: the class A drug of gaming