FoxTwo

What mission? Tanker speed should be consistent. Looking at the F-14 training mission, I suspect it's broken.

Is it intended that the radio is non functional on battery or ground power? It only works if the engines are running. Seems like that's something that should work on ground power but I'm no expert.

In VR I'm getting some... weird texture or geometry pop... there's a white triangle that likes to pop up every now and again in the bottom corner of my eye - left or right - depending on where I'm looking. Usually noticeable over open water, at altitude (30k ft+). This has happened in multiple planes (F-14, FA-18 in the Caucasus, could be happening on other maps but I haven't verified.

Yeah I think what happened hear is that the previous SSA 'release' was marked as beta, so the settings were filed as beta, but this version is marked as release so... yeah. Anyway same thing happened to me, had to reimport settings. Not a huge deal, thanks for all your work.

ED acknowledge the issue on reddit.

ED literally just changed everything again in yesterday's open beta. What would you like HB to do about that?

Ok so I guess this is just an 18 month old issue that's already been reported. Nevermind then. https://forums.eagle.ru/showthread.php?t=227646

This thread has hit 18 months. Huh. Guess we're not getting a fix for this eh?

Pimax guys go on for days about the wider FoV but honestly when it comes down to it, the 8KX will be harder to drive, limited to 75Hz, and MAY just equal the clarity of the Reverb G1 with a price that's almost 4x as much once you factor in the cost of the deluxe audio and base stations/controllers. The value just isn't there for Pimax. If the G2 really does have better optics, audio AND tracking, at the price point it's hitting, I don't see how it's not going to be the headset of choice for basically everything. No one else has announced anything that's even close.

Truth of the matter is the way that ED implemented VR was probably a somewhat of a hack; render two cameras instead of one and bam, you're done. This is obvious with some of the lens effects, and the LODs. They probably can't fix it easily without breaking something else, or they have no way to tie camera position/rendering to anything BUT the camera that's doing the rendering. I'm sure it's a complex problem. I doubt we'll get an answer, explanation, or a solution anytime soon.

I mean honestly. When tacan and ILS stop working entirely because the scripting engine can't manage to remember to keep them on, that's a supercarrier breaking bug. I get that it's a DCS engine problem but it's DIRECTLY impacting your brand new module, and it really really needs to be fixed after all this time.

WMR support is fine. It's not great, but it's functionally fine. You need to have Steam VR installed, that's it. Sure, there's a whole bunch of tweaks you can do and Steam VR may have some overhead that going to WindowsMR native would help but it's by no means broken. DCS added support for the Varjo for professional training use, not for general gaming consumers.

That's fine but still doesn't explain why the audio engine doesn't render sounds in the proper location. In the F18 cockpit the engines and apu should sound like they're behind you, not in front of you.

I've got a full 5.1 setup for my PC and I'm getting effects in the center/rear channels but certain sounds that I would expect to come from behind me - engine noise, APU noise, etc... don't. Would really help with the immersion factor if the sounds came from the right speakers. Like I said, SOME effects are clearly going to all speakers... rain I can hear all around me, wind noise, the canopy open/close sound comes from the rear...

Re-calibrated again but this time went really gentle on the release and it seems to be fine again. I must have been letting it flick back during the calibration.

Having a bit of a problem with my stick returning to center point of the X axis after moving it to the right. It's holding at anywhere from 52-55% instead of going to 50%. Going left and back to center works fine. I've tried recalibration via CLI tool and in windows device properties to no effect. If I forcefully release the stick, it returns to 50%, but if I gently let go of it it holds at 55 to 52%. The easier I let go of it the worse it is.

I keep getting these black squares/blanking in VR since the latest patch. It's incredibly annoying. Normal one frame: Black squares the next Seems to be related to MSAA. Enabling it at all causes this issue for me.

Newest leak shows what looks like a reverb + index + rift s. Manual ipd adjustment as well. Expected reveal on the 28th.

Throttle and mount bundle is more expensive than buying the throttle and mount separately. ¯\_(ツ)_/¯

I don't find this to be the panacea that this thread is making it out to be. I'm not seeing any great performance uplift versus my normal settings, and am in fact noticing that textures appear to be somewhat blurrier.

I'd probably be in for a throttle and the new startup panel if this were the case.

MFAA does work however, so feel free to enable that in the control panel.

Add the Harrier AV-8B engine fan blades. Only rendering in one eye.

You can remove the speakerphones from the index, they're held in place with a hex nut I think.

This was in MP, didn't test in SP. After landing on the deck of the Stennis, the Harrier bounces around and will eventually push itself off (or get pushed, whatever) the deck. Parking break on, engine off. Whatever DCS updated in the latest beta seems to have broken the deck completely.