Cheese16

I believe the mosquito suffers from this as well. I know it did work in the huey when i first played Paradise lost a few years ago. Not sure when it broke but it is pretty terrible

I feel like this was mostly existing modules and dynamic campaign marketing concepts that definitely didn't look like gameplay footage. Also no Razbam, speaks volumes. It also feels like a seriously reduced focus on third party modules on the whole aside from Heatblur. Fulda Gap/Berlin looks pretty sick though. Ugra just keeps hitting. After all the focus on F6F and WW2 Marianas last year, it feels a bit like ED are sort of hiding from it now. This is the thing I'm really excited for and after this I feel like we're going to be waiting a long time unfortunately. After the swath of half baked launches this year, I would have thought ED would want to inspire a bit of confidence in their customers rather than making more lofty promises. Also starting dev in 2025 releasing in 2026 for 2 FF modules? Does anyone seriously buy this? That is so unrealistic for ED I'm kind of shocked they're saying it. If we can do an F-35 how can we not do a UH-60 or any number of other things that have been shot down because of "lack of documentation?" If pilot testimony is all it takes now, it seems like we could do just about anything. Also why the F-35 and not an F-22? Or more Redfor aircraft. Obviously I'm not the only one saying this but the community has been begging for more redfor for years, but nah let's just remake FC3 at full fidelity and turn Full fidelity modules into FC3 for some quick cash.

A month and a half and still proofreading. Hmm.

@BIGNEWY @NineLine this has been as issue for so long. Still a problem im the current build. I hate to be that guy and tag you guys but people have been reporting this forever. A bit frustrating that it hasn't been fixed yet.

I know this hasn't been updated in a while but to anyone wondering, it does still work. I just started using it last week and it is an absolute godsend. This really should be stickied somewhere. It is basically a necessity for using 3-position toggles.

This was fixed for me in a VD update shortly after I reported it in their discord and they banned me after denying the problem was on their end. Go figure.

Chinook gets an early access manual and we still don't have a manual for the Hind. okay.

As others have stated, it really depends on the equipment. I used a Valve index up till around Feb. And thought the new dots were awful. They were way too big and disappeared way too early, so objects in the middle ground would effectively dissappear. It made anything between 3-10 miles completely invisible and anything over 10 miles impossible to miss. I could lock up a su27 at 20miles, watch it close in and just disappear but keep the lock until it was on top of me. Now after switching to a Quest 3 everything is almost invisible until they're under 3 miles. The spotting dot almost doesn't exist. Ground targets are also much harder to see. It would be really nice to just have a slider for this

This was fixed for me a long time ago and seems to have returned with the most recent update. It seems to be cause by Axis not being centered while in the controls menu. Using collapsed view doesn't seem to change anything on my end.

This is still an issue after the most recent update. Oculus and VD both had updates this week as well that had no impact. It still only impacts DCS and judging by posts elsewhere I'm still not the only one experiencing it.

Okay, so it still isn't completely fixed, but its a lot better. Nvidia settings were all default already. I think what really did it was updating .Net Framework to version 4.8. Logs are no longer throwing tons of OpenXR errors, so thats something. Its gone from flickering every few seconds to maybe once every 5 minutes, which is still pretty annoying, but much better. I'm not really sure what else to try again. I checked everything in that thread and the only thing I was able to do was update Windows and .Net. I'll test it a bit more over the coming days but I may just stick with SteamVR for the time being, unfortunately.

I have been testing without it, it doesn't seem to be that.

Seems there a few interesting solutions in their worth trying. I'm pretty sure everything in Nvidia should be default already but I'll double check. Might have to try reinstalling .Net framework as well. It's rare but I do occasionally see .net errors when launching simshaker. I was under the impression that it was caused by running multiple instances but maybe not. Thanks, silverdevil. I'll check a few of these out and report back.

Okay so after a fresh install some things have changed. I tested OpenXR, Oculus, and Steam VR again on a fresh, virgin install. No modules, no old Save games folder, nothing. The game now appears to work fine in SteamVR now, which is nice. But it still flickers in Oculus and OpenXR. OpenXR is by far the worst, basically unplayable. Oculus is not much better. Still isolated to DCS. I would prefer to use OpenXR but at least now I can play. I looked through the logs and it seems to be throwing a lot of errors with OpenXR. Here the latest two from this fresh install. The '.old' log was with Openxr. It did work, but continued to flicker constantly. dcs.log dcs.log.old

Starting with a fresh save file did not help, unfortunately. Here is the log file. I am currently doing a full clean install, so we'll see how that goes. dcs.log