some1

A fundamental issue is that LODs are not switching evenly for both eyes. Meaning that at certain distances you can see a more detailed version of 3D model in one eye, and a lowpoly version in the other eye. This also applies to some effects like fire, explosions, etc. And I'm not talking about config tweaks, I don't have shared_parser enabled or any other mods and the issue is still there. It's like no one at ED really plays this game in VR. It's not that hard to notice.

No it isn't like that in real thing. Just read the bug reports on ADF functionality.

40% that never expires just for saying "don't tell me anybody is testing this thing, I won't believe you"? Somebody must have felt offended after I posted four or five bug reports withing half an hour just for one aircraft and found the first opportunity to send me on a forced holiday. I don't see any other reason, people make such comments here all the time. I also did not have any active warning points before that, so please don't spin it like I made multiple offences and this was just the last one.

You describe one type of bugs: hard to find, easy to reproduce, easy to fix. In all other categories, (Hard to reproduce - even with tracks, or hard to fix), your help is negligible compared to amount of work the devs need to put in order to solve the problem. But yeah, in the end we get a better product, so our motivations don't matter that much. Of course not! Officially it was for "I don't believe it was tested" comment in one of the reports, which surely qualifies for a ban here.

Don't kid yourself, I got 40% warn and a month long ban on this forum for reporting too many bugs and complaining about lack of proper QA on the developer's side. Bug reporting is mostly for your personal gain, as you have a chance of getting a better product in the end. A product for which you've usually paid in advance BTW. If the thread author wants to help ED, there are better ways to do that than sending more work their way. :)

It's quite possible that recoil has been removed from the rockets intentionally, and they simply forgot to adjust the autopilot accordingly. There was some debate whether rockets should push back the plane or not.

After recent changes to model/lighting there's something wrong with radar frame

Nah, it's a thankless job, often more frustrating than it's worth.

Yeah, overall they did a good job on the MiG, fixed most issues and even added some extra features post-beta-release. This may be the last "big" issue with the module, so sad to see it left that long without any attention.

This is not how shadows look in real life. And that amount of flickering will ruin any motion smoothing algorithm in VR. It's a problem with all helicopters in DCS since one of the graphics engine updates. But to make matters worse, the Hind has glass canopies instead of solid roof that shields from the sun, so the shadow flickering will be an almost constant thing.

Classic case of an armchair expert arguing with people who have real world experience. I spent a few days in a prop plane on a cross country flight and never noticed the propeller affecting my vision in any way. Recent DCS prop planes in VR look so bad, I feel fatigued after 5 minutes of looking at that flickering mess.

It is replicable in track replay for me, but simply not every time I start DCS. I also get this "intermediate" corruption more often than total whiteout. Which may be harder to notice and some people may have the issue not realising something is wrong. But once you know what to expect, it's easy to spot: Good: https://i.imgur.com/7KKGNAK.jpg Bad: https://i.imgur.com/pfPqbSQ.jpg

The only navigation system in the MiG-19 is nearly unusable since day one. Every aspect is bugged. There are problems with the artwork: https://forums.eagle.ru/showthread.php?t=234657 Problems with controls https://forums.eagle.ru/showthread.php?t=233607 https://forums.eagle.ru/showthread.php?t=263185 https://forums.eagle.ru/showthread.php?t=242058 And problems with actual operation according to real manuals https://forums.eagle.ru/showthread.php?t=233686 Does Razbam have any time estimate when these issues will get fixed, or just happily ran away with the money? 20 months to sort out basic issues like these sounds ridiculous, yet here we are.

I also checked on a different PC (a laptop with GTX1050) with a vanilla DCS install, having only Hornet, PG and the Harrier installed. 2 out of 5 DCS runs, I got the issue. Not the total whiteout, but the intermediate issue where the smoke doesn't blend correctly with the background. (https://i.imgur.com/pfPqbSQ.jpg)

Here are my settings, no reshade or any shader mods (or any mods I can remember). The issue seems to happen in both VR and 2D:

I played the attached track several times, restarting DCS with each attempt. Just start DCS, replay track, exit to desktop, start DCS, repeat... Not changing anything in the system, no shaders reset or anything. And I randomly get one of the three results: 1. everything looks fine. 2. medium garbage, but usable. 3. completely useless as soon as smoke gets in the view. Sorry if I sound annoyed, but this game breaking issue is still here despite being reported almost a year ago. flirWhiteout.trk

And the FLIR went completely south on me today. What a waste of time. I have a suspicion the smoke from Maverick launch can trigger the issue, just like the smoke from chimneys (which I have disabled).. but it's just a suspicion.

This is still an issue in various planes, today the display in A-10C went full white after Maverick got in the view (maybe smoke effect is a culprit?). When I restarted the game the image was better, but there are still weird white blobs instead of smoke from burning objects in both A-10 and F-18. IR: CCD:

Nope, the movement still stops randomly. It may be even worse in today's version.

DCS P-47 has broken cockpit shadows, errors in the artwork, engine temperatures make no sense and have zero effect on the performance and there are many other issues reported in this forum. I wouldn't put too much faith in Nick Grey's Quality Assurance. So far you have several pilots that commented that's not how it looks in real life, yet you still try to explain poor DCS graphics by some obscure phenomenon you've found on wikipedia, which requires certain conditions to happen. Like your eyeballs need to vibrate at multiples of object RPM - seriously? That absolutely does not explain why in DCS the prop looks like that all the time at every possible RPM.

A spinning propeller would "flicker" (obstruct the light source, reflect the sun on each blade, etc) at a frequency of: number of propellers X prop RPM. Which in case of P-47 would be around 4000 Hz. That's way, way above the flicker frequency that's perceptible to human eye (low hundreds) and also way above the frequencies for subjective stroboscopy you quoted from wikipedia. Unless you put the propeller of a working engine under an artificial lighting or try to record it on a camera, it won't appear as it does in DCS.

That is still above the frequency used by many "flicker free" light sources, and way above the numbers in that "Truly continuous illumination stroboscopy" quoted from wikipedia. I've never seen a propeller that flickers, stops and changes direction like the ones in DCS, neither from the inside or from the outside of the plane. That also applies to rotors and rotors shadows in helicopters.

The MFD's are still broken in the sun. That's TGP on the right one, good luck finding anything. Also note how the text on the right TGP (but not the cross) goes darker than sun reflection. That's not how real life works.

Yeah, that's what also got me wondering a bit. There was a paint like that on one of Polish MiGs (or several), but it's not very typical.

I use VR for combat sims like DCS, IL-2 or racing simulators (AC, ACC). Trackir for more relaxed stuff like FSX, P3D, ETS2.