Dawgboy

I meant nauseous literally. I'll work this weekend on the stutters and let you know.

I was about to focus on getting DCS running well with my Pimax Super 50ppd U/Wide, but when the Viper added the helmet hardware to the Viper's view, I had to stop flying...nausea. I guess I could work with some other aircraft to get it operational. I have the normal stutters Pimax Super 50ppd were describing, but I've not configured quadviews in any form.

As subject reads; I get a FORBIDDEN error that I don't have permissions. This is after the recent trouble with the forum. I logged off and on and still the same.

I have the 50ppd Super Ultrawide, and the FOV is better than my old Reverb G2, of course. Resolution is outstanding, but as stated, I have problems with the hazy glow/bloom around any light sources during night flying, even with full moon. I have to pull the brightness back (decrease), and with a full moon, I can't see any terrain features as I would in real life. The guys flying with flatscreens are commenting on the gorgeous terrain in the moonlight, and I see nothing without NVGs. I had a ticket open for this, and they merged it with my other still-open ticket that has nothing to do with the night-flying hazy glow.

A word or two must be missing. Are you referring to the hazy glow (bloom) effect around the light sources during DCS and Falcon BMS night flights? And that Pimax isn't taking action to alleviate this problem? TIA

Yes for me. Same issue...hazy glow from all light sources, only in headset. Flat screen monitor does not have the glow.

Does this seamlessly manage DCS mods to enable and disable, including lines added to config files? That might be a stupid question, but I stay away from DCS mods because it's too much of a PITA to hand mod files, etc. If you have another article of video, would you pls add the link?

I agree with this, and I have the Super 50ppd UltraWide. I swapped for the Super 57ppd, and I'm glad I did. I primarily fly my combat in Falcon BMS v4.38, and the clarity is amazing in both that and DCS, which I use for joyrides.

This is what I do; however, as @Captain Orso said, even Pimax says to launch DCS via the My Assets-created DCS icon to ensure PP applies the per-game settings to DCS, in this case. My suggestion is for Pimax to fix PP so it reliably detects the sim when running, apply the per-game settings, even if I have to make PP aware of the sim executable. Again, per-game settings should be applied automatically and reliably if I start with the native DCS Windows icon.

Agreed. I'm hoping improving software and firmware will reach parity with the hardware's FULL potential, including usability features working. For example, I'd like PP to automatically apply the "per game" settings to the headset when I run each sim from its native launcher, similar to the way NVIDIA control panel, etc., applies per game settings for the GPU when I run DCS, BMS, MSFS.

Same...no QV. Please, what are your setting details in PP and DCS, if you don't mind? TIA. I'm just starting my DCS quest with Super U/W 50ppd.

I'm deliberately not installing SteamVR, trying to keep my VR pipeline less complex for troubleshooting, etc. What are the must-have capabilities of SteamVR?

Yeah...sort of like birds and civilian aircraft. Anyway, +1

BTW, speaking of inside-out-tracking, I've not had any issues. (fingers crossed since I've not upgraded Pimax Play...yet) I have a physical, motionless Viper cockpit and three walls surrounding it, with a door on the left. Tracking is flawless for me, similar to my Reverb G2.

I did it both ways. Another user said even with the game-specific settings and starting the sim with PimaxPlay, unless he changed a setting and reapplied it, the setting wouldn't work. Starting the sim in PimaxPlay needs to ensure it's monitoring whether a game starts in a "standalone" mode, not through their processes. While it might work well in some cases, such as DCS, other sims won't. PimaxPlay needs a lot of work across the board.