fearlessfrog

It seems the cloud patterns are seeded randomly at the start of each mission @Nodak, making it hard to do a re-run and get the same result each time.

I had some trees in my test image here ..but they don't show any difference in before/after with the left/right view sent to the headset. I just thought it worth mentioning that there was data from outside the cockpit as well. Not sure why that would offend. Apologies if so.

There are trees in the test image, are they not good trees? So to confirm, you don't see any improvement in the cockpit, just in the outside view alone? What headset do you use? Maybe this is an Aero Varjo update thing?

Sure, as there are physical displays and lenses involved. But surely the changes can't be so tiny that there's not a single pixel difference between two 4K before and after images? That doesn't need the mirror to be exactly like the brain perceives things, just different in before/after. Move that swipe back and forth and see.. https://github.com/fearlessfrog/dcs-vrdirectx-compare/commit/25046e4a8d6e14363605ef78b87ae62d8ce00507 If the explanation is 'it is so tiny in color saturation you can't see it even mathematically in the VR mirror' or 'You need to be not on the ground' then it moves it more into VR homeopathy I think. Anyway, please do test away as the whole area is really interesting.

Yep, it's possible for sure. If you are redoing your drivers and can capture this with a VR mirror (I think you mentioned it earlier in this topic) then that would be ideal. Holla if you want an image compare tool etc. as happy to help.

You'd admit though that the VR headset doesn't actually have a little helicopter in it with a mini Caucasus region stuffed in there though, right? It's showing your left and right eyes two separate images, and the difference between them creates an impression of depth. The VR mirror is a direct copy of the buffers given to the two displays in the headset. Not being rude, but where do you think the 3D image then comes from? I know I sound a bit facetious here, but I'm trying to find some common ground. I don't mean any offence just curious on how you arrived at that. Is your hardware the same? Maybe it's a difference in that, e.g. headset or something? EDIT: Ah, see your edit - you have something good but don't want to help others have the same, or are at all curious on how it works. No worries, sorry for the bother.

As this is just for fun.. Win10, Nvidia 3080Ti, HP Reverb G2, OXR via oc-acc - you can use the 'Swipe' or 'Onion Skin' tools at the bottom to see the difference between the first 'off' and 'on' images. I rebooted between them and used Supmua's imported profile. For me personally I don't see any 3D perspective difference here. DCS open beta latest, Apache cold start, with some random differences in clouds maybe? https://github.com/fearlessfrog/dcs-vrdirectx-compare/commit/25046e4a8d6e14363605ef78b87ae62d8ce00507 I am not claiming that others aren't seeing stuff, just trying to quantify the change for me personally.

The VR mirror shows the left and right eye images. A screenshot of it before / after the profile change would then differ enough to show how the 3D effect for you is different? I think I understand where you are coming from now. Thanks for the original tip, and I hope people enjoy the improvements they see.

You seem to have misunderstood what I am saying. I never mentioned a placebo effect or people not seeing a change. I just said that the reason you are seeing the change isn't anything to do with using a V-Rally Nvidia 3D Glasses 1998 released 2D game profile settings. It's more likely that you are just inadvertently fixed your previous profile setting through this process. Running nvinspector and doing the 'apply' has maybe updated/overwritten previous values that were broke for you? I don't mind/care/object (delete as applicable) that people are enjoying this, good on them, but others don't want just a 'feeling' based explanation akin to something like 'VR homeopathy'. There's a lot of that going on in the world already and sometimes it's worth some discussion on the 'why'. If anyone can grab a static scene using the VR mirror and upload a before / after image then the differences should be obvious with a compare. For me the process didn't work, so I can't do that (I'm a Capricorn if that helps).

Hey don't shoot the messenger here folks but I'm fairly sure none of these nvidia profile settings have any impact on VR with DCS or any app. What's probably happening is that applying a profile change in inspector is then going back to all profile all defaults, and for some that's improving the experience. So I'm not discounting it might be better or different for people, just that these values do anything VR related at all and the 'reset' profile is what's happening. Even the profile that people are having success with of 'VRdirectx' is a bit of a misunderstanding. 'VRdirectx' the exe appname of a title called 'V-Rally: Edition 99' from 1998 and for the Nvidia 3D Vision specs (the polarized lens ones, that introduced a pseudo 3D effect using depth buffers in old 2D games during that 3D TV fashion time we had). https://www.mobygames.com/game/v-rally-edition-99. So the 'V R' here is meaning 'V-Rally', so dust off your 3DFX Voodoo cards! I checked with Microsoft's mbucchia (one of the authors of OXR Toolkit a lot of us use with DCS) and his thoughts were: Anyway, just wanted to pass that on if people get annoyed they don't see a difference with this.

I'm enjoying this campaign and the Viggen very much. I'm having trouble contacting my flight to attack their target on Mission 3 (the RB4 ships one). Here's what I've tried: - Checked Easy Comms is off. - Can successfully talk to ATC via the A/G button depress, and can taxi out, get good radio comms (F22 PTT etc). - Successfully manually tune the radio using the '-' button and the dials, in that I can talk to other ATCs fine. - I press '1' on the top row for 'Special 1' as that was mentioned in the briefing as my flight frequency. I never get a response from my flight, so wondering what I'm doing wrong? I opened the mission in the editor and it seems that the preset for Special 1 is different to the flights '124 AM' frequency defined for the flight. I tried both manually (using the '-' button) but no luck. What else to try? Can anyone else talk to their flight in this mission?

Just tried this and it looks great. Thank you @Devrim It seems the radio and QFE instrument figures are broken though? I get a QFE reading of 8992 and can't dial it down to a good value? Installed the Viggen update on 29th Dec 2021, so not sure if was ok before that. EDIT: Ah, I see it's been noticed and there is a workaround and an update planned - cool!

Hotfix likely next week sounds great. Thanks. Happy Xmas @Cobra847 and the rest of the team, plus to all those here in DCS land.

Ah this would explain why the training missions I tried don't work. I thought I was doing something wrong navigation-wise. Any chance it could a DLL 'meet me in the alley' fix, rather than having to wait till New Year for a ED hotfix?

Mine worked from since I got the Reverb, so at least 9 months. Then about 5 weeks ago, always crashes. It's really weird and I'm definitely in the minority of it happening, but no luck in tracking down what is causing it. Could be hardware I guess, some tolerance etc.

I still can't run reprojection on WMR with SteamVR. I did a reddit post and it seems it's a few games that trigger the crash. The WMR team didn't respond as yet and the SteamVR did post a 'Try nvidia driver version 457.30?' (it didn't help). After re-installing Win10 yesterday I've pretty much given up. I'll run DCS without reprojection, it's not great but it's not unusable. So weird how there doesn't seem to be a common thing that causes it. I guess I'll just wait it out for new SteamVR (which I think is the culprit) releases and try them as they come out. The best clue on the issue is in here that I raised at the Steam forum: https://steamcommunity.com/app/250820/discussions/3/3172198151252196351/ The Steam vrcompositor.txt logs show: Sun May 09 2021 19:06:17.173 - Error: Aborting WaitForPresent after 1.000000 seconds! TimeSinceLastVSync: 1128.204346(64132) Sun May 09 2021 19:06:18.293 - Error: Aborting WaitForPresent after 1.000000 seconds! TimeSinceLastVSync: 2248.324951(64132) Sun May 09 2021 19:06:18.400 - Render thread ending Sun May 09 2021 19:06:18.400 - Signal thread ending Sun May 09 2021 19:06:18.409 - VR compositor shutting down ..so some sort of hang, perhaps caused by WMR reprojection crashing out.

Just to revisit this and perhaps hopefully help others that have this same issue. My SteamVR reprojection crashes were caused by enabling Nvidia G-SYNC on my 4k BenQ EW3270U 60Hz monitor. I've passed the bug on to the WMR team, and while it could be most easily triggered by DCS, it doesn't seem like a DCS specific issue.

My comment was more about what was doing the reprojecting, but if we're talking about the files to edit then since about build 1.2.5 it should be ok to ignore the old WMR settings file if using the SteamVR UI for settings. The Steam metabase and the WMR for SteamVR dash app is now looked at first, followed by that file; while before it was the other way around.

FWIW, the Motion Smoothing is within the WMR compositor, so SteamVR is just being used as a front-end to enable the WMR motion smoothing setting. The settings used to be in a text file within the WMR for SteamVR config (which like you said, we disable or comment out), but now it uses the setting on the SteamVR side or per-app SteamVR setting to set the mode for the WMR compositor underneath. More info on that change here: https://docs.microsoft.com/en-us/windows/mixed-reality/enthusiast-guide/using-steamvr-with-windows-mixed-reality#enabling-motion-reprojection-for-steamvr-apps So only the Vive and Index uses the SteamVR motion smoothing, and the WMR devices uses theirs within their driver. WMR's algorithm has got better the last year or so. On the OpenXR side (which DCS doesn't support as yet) the Motion Smoothing can now actually kick in at 1/4 refresh rate, allowing something like MSFS to run at 22 FPS but you still get 90 Hz in the headset. Having used both the OpenVR with an Index and WMR for SteamVR with a Reverb I'd say the Index is a little smoother at a lower kick-in rate. WMR for SteamVR needs about 55 FPS to work comfortably, while the OpenVR side is still smooth closer to 45 FPS, so Valve did a good job on the overhead side (or WMR is a little too cautious). Once working ok, both seem pretty smooth to me, with the Index having an advantage of more choices around usable refresh rates (I never found 60Hz comfortable on the Reverb).

I don't think so. Updated to patch today and blue AI in the Hornets still struggle. No red losses in that Instant Action 8v8 BVR. No 120, 7 or 9 hits recorded. In multiplayer it's fine, as like @BIGNEWY said we can nurse the 120 along and guide it. This is more an AI vs AI sort of thing for now. Track attached. 8v8redwedding2.trk

@BIGNEWY Do you need another track for this one? I put mine here but happy to upload another one or more if it'll help.

Here you go. The instant action 8v8 track, so hopefully I did that right. I just left it alone and let it play out, all default. Initial distance about 20nm. 12 AIM-120B's fired, no hits. 6 R-73 hits, 2 R-77's hits. All 8 Blue killed, no Reds losses of their 8. Tried changing the default mission to not fire weapons until within 10nm, same result. Changed the mission, so that blue and red locations/speeds are swapped, so it's not starting positions. Tried changing to F-16's and then F-15's and more or less same result. The F-15C's did get a single kill. Changed the 120B's to C's and gave them 8 each, no kills. So this is more about single player and the AI and the use of the AIM-120's, it feels a bit off - or is this just how it is? 8v8redwedding.trk

Yes, I found the same in 2.7. https://forums.mudspike.com/t/dcs-2-7-aim-120-experiment/12394 I ran the Instant Action / 8v8 about 10 times now and it was never even close. I reversed the positions/speed of the mission (so sort of swapped red/blue teams) but same result. I also tried AIM-120C's instead but no luck. I tried making the AI wait to fire till closer but they still always miss. Is it worth doing a track? The steps to recreate are: 1. Run Instant Action / Hornet / 8v8 BVR on DCS 2.7 2. Watch blue missile miss, except for maybe a -9 at the end. BVR doesn't have to be 'balanced' but that seems a bit extreme, as it makes single player mission quite hard when playing blue.

A wishlist item: If the VR performance shader changes in here: ..can't be added to the product, then the next best thing would be some IC special rule that could be added to make them pass a MP Servers IC check. The shaders make a big performance impact in VR, and the IC friendly versions of the mods are less efficient. This wishlist item could help resolve that. Thanks!

+1