Klaiber

Setting up in OvGME was easy. I have two focuses in my OvGME. One is going to the DCS Saved Games folder: X:\Users\[name]\Saved Games\DCS.openbeta. The other is going to the actual game (what I've called DCS Game): X:\Eagle Dynamics\DCS World Openbeta. The actual game focus is the one you need. First, you create a folder called DLSS 3.6.0, and place that in the OvGME folder that's prepped for the DCS Game. Inside that DLSS 3.6.0 folder, create a folder called bin-mt. Inside that, put the new nvngx_dlss.dll file. Then, in OvGME, select the DCS Game focus. And enable the new DLSS 3.6.0 folder. It should work.

Thanks Ferd! I set this up with my OvGME. I'll let you know if it works!

There were definitely some changes. But overall they were understandable. Minor spoilers:

Was this good? I'm aware of the true story. Am curious if they did it justice.

Thanks @Vonrd! Looks great.

Fixed, with clean link. The original URL is below the YouTube video.

It would definitely be nice!

Sorry @Raptor, just sitting down now. I'll definitely be online tomorrow.

Yeah, the MiG-23 is very important for REDFOR. The first Soviet look-down/shoot-down radar system. It'll be a game changer on servers like Engima's. The MiG-17 is primarily a gunfighter. No missiles in early models. Missiles only in later models. MiG-17PF and beyond. The MiG-19 is transitional - mostly gunfighter, again with a limited missile capability. However, rate-fighting maneuverable gunfighters, using the right tactics, can be used to devastating effectiveness.

His overview of WW1 is fantastic.

Oh yes. We're very excited for the MiG-23. And the MiG-17 as well: https://stormbirds.blog/2024/01/01/red-star-simulations-mig-17-update/

Oh, I blame Meta. 100%. All Meta cares about is the Metaverse and stopping the hemorrhage of money. They can't quit the project, and they can't make it profitable. So every other game developer with VR features is forced to be reactive.

So, me shutting off the auto-update won't stop v63? Honestly, if they box the lot of us, I guess we can pick up Minecraft for the next 3 to 4 weeks...

My headset is still on v62 for my Quest 2. I've turned off auto updates in the headset's OS, to try and stave this off. However, if they force the update, this won't work.

Just saw it today. Was amazing.

You may have a conflict. Check your control settings under axis and make sure that nothing else is attached to the throttle. If that's not it, check to see what the key command for the throttle is within the regular controls. And see if it conflicts with something.

Present.

It's great to see her refloating!

Same.

Yeah, it seems a lot smoother for me. Visuals are a tad bit better. We'd have to test the disappearing dot thing in VR.

Hi @Diesel, Welcome! Thanks for checking out our squadron! I'll send you an email to the address you registered to the forums with. Looking forward to talking with you more soon!

Gaming means that the ASP reticle moves to the target. Realistic means the ASP reticle stays in the center. Honestly, everyone should be on realistic, as it's preferable. But, at the end of the day, it's personal choice. NOTE: they've reversed the check box. So... I originally had it checked to "Realistic." After the update, when I checked the Special tab, it was now checked to "Gaming." So, I had to uncheck it go back to the settings I originally had. TLDR - everyone will just need to confirm what they have after this update.

For the MiG-21, Brit and I were glad to see: Special options: changed default ASP reticle state from GAMING to REALISTIC (unchecked). For GAMING state, the user needs to check this option. Hopefully, this should eliminate confusion.

I guess this is also the integration patch, merging Open Beta with standard.