yaga2

You seem to misunderstand the reported issue. Please re-read my post. EDIT: Maybe not. Just want to be clear that with it enabled, we have one set of issues, and with it disabled we have another set of issues.

There's not a difference in ECM effect. It was an issue. It still is an issue. As more FF aircraft get the ability to run ECM, the effect of the issue on gameplay increases. Apart from that, the more people that are aware this issue exists, the larger the issue becomes as the occurence of the problem naturally increases in the wild. Further more, when someone previously unaware of a problem learns about a problem, it's effectively a new problem from their perspective. Because for them, it is. Seems a lot of people suddenly found out. Perhaps partially due to publication pertaining to competitive events banning ECM use because of the bug, perhaps partially due to the ever increasing qty of ECM-using aircraft not subject to a 'warm-up' time to start jamming. Or perhaps a large volume of people en-masse just decided to start testing stuff coincidentally. Who can really say? Regardless of if this answers your question, it's fairly separate from anything relative the topic on hand: -ECM is not working as intended. -Given this, ECM can effect gameplay in dramatically negative (and again, unintentional) ways. -This issue will be felt more as ECM is added for more modules in its current state. Is there anything about that you disagree with?

I see! That explains it, then. Thanks for clearing that up. I'm specifically looking at the gun. Which .uwv are used by 'Cannon/Gun Fire'? I'm trying to see if I can maximize how brutal and violent it feels while firing.

There have been multiple posts about this on this forum as well as other community hubs, and ED, to my knowledge, hasn't directly acknowledged the problem to its full extent, despite the fact that it seems like a glaring issue for seemingly-all VR users/headsets that is immediately apparent upon spawning in-game and quite visually jarring. Under default DCS settings, objects like aircraft contrails and puffy-white-clouds (that's the technical name for em, I'm certain) only render in one eye beyond a distance threshold. Inside this threshold these appear to render for both eyes, but there's a very noticeable and large distance between where one eye begins to render the object and when both eyes render the object. For clouds and contrails, you can fix this by creating an autoexec.cfg file in: C:\Users\Username\Saved Games\DCS.openbeta\Config and adding this line to it: However, be warned, ED explicitly tells us not to do this: And they're correct to a degree. While using the shared parser will fix clouds and contrails, it will cause many lighting effects to render in only one eye. The most notable being cockpit flood lighting and lighting effects on object textures, the latter being most apparent at dawn and dusk (object will appear shinier in one eye than the other). In my opinion, this trade off is worth it in order to have contrails and clouds render in both eyes, but it is a trade-off and ED tells us not to do it. I don't mean to insinuate that ED is intentionally ignoring this problem or purposely shelving support for the VR experience, but I am a bit discouraged every time I see this topic posted here or elsewhere, and always without any reassurance that measures other than the standard "mention it to the team" are in place to solve it. The optimist in me hopes the 2.7 cloud-update will happen to include a fix, but I'm not basing that hope on anything concrete. In short, shared parser true or false, all you're doing is deciding if you'd rather have clouds and contrails, or important lighting effects render in only one eye. You can't have both, and neither option feels "good". It'd be a very appreciated fix across a sizable player-base. Let's all cross our fingers for luck and pray to the DCS gods for our eventual deliverance from this issue.

I'm attempting to edit .uwv files, but I'm having trouble determining which effect uses which .uwv. The SSA manual states: For me, placing the mouse cursor over these check boxes does not display a tool tip. This is true for all effects check boxes. Any idea why this might be? Thanks!

I've got a MP track from a BFPG session showing lots of instances of this happening. Unfortunately it is 182mb, and the max file size for upload here is now 5mb. Looking through my other tracks, I see very few that are even close to being within this size restriction. How does this work? Am I missing something? Edit: Google Drive download for this track: https://drive.google.com/file/d/1DoLR-_ZXcgSXEb3_hPKrjHOA4jdD8fDn/view?usp=sharing