some1

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.

This is not a magic tweak that will fix everything, but I think that PD around 0.8 and Steam SS around 100-120% is a good balance for my 3080 in singleplayer. PD 0.5 is a bit extreme and you loose too much on image quality to make it up with SS. No matter how high you crank it in Steam, the image is still blurry and jagged. Ultimately you need to find a balance between PD high enough that the game outputs enough detail to produce nice visuals, and Steam resolution high enough to utilize those 4k screens on the Reverb.

Yes, unfortunately ED made it hard to replace single file, as they are all packed into a zip that contains all aircraft textures. So while Mnemonic mods are great for those who want to get more realistic effects in VR, they quickly get obsolete when ED changes anything, even on unrelated texture items. You can manually copy prop texture files from Mnemonic mods into the new texture zip shipped with the game. They are usually all called prop-something and have a single modification date inside a zip file. But you have to repeat that with every update for every aircraft. Not fun. Currently I lost hope ED will do something about it. People have been complaining about that for years, and the devs are still shoehorning those prop/helicopter effects into the unreleased modules that are currently teased on the videos.

Haven't seen such behaviour previously so often, but now the missiles have a tendency to turn 90 degrees off-path chasing countermeasures. In one short mission I had two out of four Aim-120s do vertical loops because of this: Tacview-20201221-220909-DCS-PG_intercept_F16.zip.acmi

With settings on High, this is more or less expected. You need to tweak the settings in game if you want more fps, or dial it for 45fps and turn reprojection on. The "flimmering" is also a known issue:

Next steps: * TMS up long to make TGP an SPI (only if it isn't already). * China hat forward long to slave Mav to SPI * Make Mav a SOI and adjust the lock if necessary.

Yeah, I meant the global setting. Per-game setting should work just for this game, although from what I read on the net, the setting does not make a difference. And when it does, it can even reduce FPS by one or two (may be just within measurement error). https://www.thefpsreview.com/2019/12/04/nvidia-geforce-driver-power-mode-settings-compared/

That's a ritual, by definition.

Never launched DCS that way over the last year with G1 or G2, and from other people experience in this thread, they did not either. It really does not require any extra rituals. Double click on the desktop DCS icon, and that's it.

Be aware that this will bump your GPU idle power consumption from 25W to around 100W. Also requires PC restart.

It isn't. The headset will switch to 6DOF in a few seconds, unless the lighting in your room is really bad.

Yeah, but that's the point: those who don't want to have pilot body uncheck this option. Those who do, keep it selected. That's what it's for, no need to reinvent the wheel. Currently Razbam aircraft behave differently than every other module in DCS.

More likely it doesn't initialise properly and thinks you've climbed from 0 to 30000 altitude in a second.

In 2D it can be worked around, but in VR the tooltip is always obstructing the actual weapon window.

Great job on the pilot model. One small issue is that Razbam aircraft ignore the DCS option to show pilot body by default. You always have to hit the key combination to show the model after the aircraft has been loaded. Same problem in the Mirage too.

Cycling TPOD CCD/IR display always resets the brightness or the IR image to the lowest (-7) setting.

Start the mission with the aircraft at 30k+, and the canopy will immediately begin to fog.

Yay, instead of dialling down reflections on the textures in the older modules, ED is pushing even more baked reflections in the latest productions. Why the backrest detail is even reflected in the instruments, shouldn't there be a pilot? Please at least make it optional like in the the Hornet/Viper. It looks completely out of place in VR or even with TrackIR.

I was about to complain about the same thing. Jester is notoriously loosing lock when transitioning to PSTT, at least in a training mission I created against single Su27 at 30k altitude.

Look sideways. It only flickers if you're looking at the menu screen that is loading.

In theory Vsync should not matter in VR because it's disabled there. But in case of DCS, if the option is left enabled in the game settings, then it severely affects frametimes on my system and cause a lot of stutters. This is with Vsync OFF: This is with Vsync ON: You can see a pattern of raising "spikes" in GPU frametimes, that repeats every few seconds. If there's not enough headroom left, it will cause drops below 45 FPS and massive stutter. This only happens for me if Vsync in DCS options is enabled and Vsync in nVidia control panel is left at its default "use the 3D application" setting. If the Vsync is globally forced in nVidia drivers for all games, then the checkbox in DCS does nothing and the performance is fine. So for me all worked nicely until I upgraded graphics card to 3080 and wiped clean GPU drivers, which reset nVidia profile to default setting. Since then I've been wondering why the performance in DCS is so bad despite better hardware. Turns out it wasn't the case of bad drivers or some recent DCS update, but a silly checkbox that shouldn't even affect anything.

For Reverb G1, Steam VR at 100% has a resolution of 2208x2164 per eye, which isn't native either. It also defaults to 150%, which is 2704x2652. They simply changed what is considered "default" and "100%". Neither is wrong.