some1

Headset optics are all focused at a single distance, no matter if they show you something close or far away. The focus distance is a few meters, so you need to wear glasses or insert lenses only if you're short sighted.

I'm specifically talking about daytime and how sunlight causes them to turn green (and dash to purple). How can you say there's no visible effect when my first two screenshot show otherwise. Actually, it doesn't occur if mission is set to overcast. So it makes me think that they tried to make them glow in response to the sun or something. Needles to say, that's not how fluorescence looks in real life. It doesn't make the whole cockpit glow "purple" or even the glow of the actual fluorescent parts is too faint to be noticeable in daylight.

Cockpit illumination activates immediately when the mission loads, even in cold&dark state with all power and circuit breakers off. There is no way to turn the illumination off, the instrument light brightness knob does not do anything. Immediately after mission loads (cold & dark) 5 seconds later (still cold & dark) EDIT: the same issue is also visible with D9 and Bf. Looks like something's wrong with code responsible for UV/radium glow at night. 5 seconds later 5 seconds later

No, the Spit cockpit was never really updated and the old textures don't look good in current DCS after all those PBR engine updates. Other, older WWII aircraft received updated cockpit textures at some point. They look fine to me, although the gauges are mostly 2D and lack the depth that more recent modules have.

No idea, never used the UI for that.

Yes, just rename the files and they will work on the new system.

You can use the input folder from the old system installation, but you have to change the names of all .diff.lua files manually from the old ID's to the new ID's. If you have many modules, there are programs that can do batch rename, that will help with the task.

It isn't. The default pages IIRC are programmable in data cartridge, something ED hasn't implemented yet. Yes, HSD page not being there by default in dogfight mode is a strange omission.

It's certainly not the high wing loading or lack of power that make the Fw-190 turn like a brick in DCS. Different wing profile maybe. Higher drag with high AoA maybe. Or a bug maybe. You can set up P-47 with more fuel to match exactly the wing loading of the Anton, 30% fuel on the Anton (GW 4000 kg) gives the same wing load as 78% on the Jug (GW 6100kg). At these weights, the aircraft also have the same power-to-weight ratio, assuming sea level and WEP (1700 HP vs 2600 HP). Yet the P-47 will still easily outturn Fw-190A, being able to sustain around 0.3-0.4 more G at both 300 and 400 km/h. The Jug will also be capable of sharper instantaneous turns and will bleed less speed when pulling hard on the stick. 2.4 vs 2.1 g at 300 IAS:

The issue quoted in the first post will most likely be fixed waaay before ED even starts OpenXR migration. Besides the developer talks mostly about additional memory footprint required by current implementation - reducing that may, or may not help in case of DCS. If you don't run out of GPU memory now, you won't see much improvement when they further reduce memory requirements. OpenXR may still improve and streamline DCS VR development in the long run, but it's not a magic bullet that some may think. For a WMR headset it functions as a yet another middleware, replacing the job of SteamVR. For a Steam or Oculus headset, it will be an additional middleware layer, added between DCS and headset API, instead of current native DCS implementation.

This is still broken in DCS 2.5.6.61527.1 Open Beta Are you guys aware, that for several months you have been selling broken campaigns that are unplayable because of this bug?

I keep this next to my throttle, works great for clicking stuff in the cockpit and navigating menus/desktop in VR. https://www.amazon.com/ELECOM-M-XT4DRBK-Wireless-Trackball-Left-Handed/dp/B016QCPRBM

Well, technically CBU97 container is unguided, but the bomblets themselves are guided submunition. Any dumb bomb from the Mk80 series will kill a tank in DCS, if you're lucky enough to score a direct hit. With Mk-84 you can even miss a few meters.

It has more to do with borked ground physics in DCS (not only for C-101), than the limitation of the actual system. In real life a free castoring wheel with a differential braking allows the aircraft to have even smaller turn radius than with the steerable front wheel, as the aicraft can basically pivot around its inner main wheel.

It should be possible to tune the ADF in every available mode (COMP, ANT, RAMKA). There is no mechanical lock that would prevent the tuning knob from turning. The real MiG-19 manual explicitly instructs to tune the radio in COMP. mode during system checks: The manual also does not contain any additional instructions that would advise pilot to change modes every time he needs to change frequency, like we currently have to do in Razbam's model. In real life, tuning ADF in ANT. mode may still be a preferred method, because it amplifies the audio signal, so it's easier for the pilot to find the station frequency and verify it's the correct one. Even more modern digital radios like the one below have such mode. But that does not prevent it from tuning directly in compass mode.

In the middle of the tuning window there should be a thin needle indicating the current frequency. It is visible on the real photos and also referenced in the real MiG-19 manual.

Does it count?

The last message from ED was "can't replicate". If it indeed doesn't happen with radar in STBY, that could explain why @NineLine did not see it.

Bumping this one, as the HUD tacan indicator still does not rotate as it should.

The bug reports linked in the first post were deleted without being addressed. I give up.

That is not true. I have a Polish MiG-19 manual, and one of the service instructions specifically says to check the radio tuning in Compass mode. I reported this a year or two ago, but can't find it right now. Razbam deleted old bug reports without addressing them.

The contrast adjustment is broken and does not adjust contrast. You can not achieve the same TGP image quality as in other planes with the same pod. Everything is explained in the 1st post. It wasn't always like that, the original TGP implementation for F-16 worked better. It got broken in one of the updates. Also the cursor disappears when you start messing with contrast, again, check the screenshots in the first post.

Yes, give up on DCS and come back in 2023. Maybe ED will fix this after we give them another two years. Some other suggestions, but none of them working 100% of the time, are here.

I think either 9L or BN said they reproduced it on their end. They could also start by going back to the version when the issue was first reported and see what has been changed around that time. Because it wasn't always like that, although the date of the first post in this thread (October 21, 2019) is not the date when it got borked, it happened even earlier and there are older threads about it. It's been broken for about two years. Sigh....

Still broken. Tried one of the 3rd party campaigns with FLIR equipped aircraft. Only wasted time. Yep, and from what ED is saying, the new IR system is not even close to release.