jaxx_za

I actually quite liked the cover - different take on the original - less anger, more sad. *Let's see how this flamesuit holds up*

Nothing of value to add, other than WOW! Now that my jaw is off the ground, how well would a physical cockpit layout work in VR? No criticism intended, just wanted to know your thoughts around getting VR to align with actual reality. I fly the mi-8 in VR as well, and am hoping hand tracking like in the Oculus Quest comes to the rift, to allow interaction with the cockpit.

Yes, you would need to use the Saitek profiler SW to program different functions across modes. Also remember that you would need to load the profile and keep the Saitek app running in the background, before starting DCS.

Welcome down the rabbit hole... Before long you will be tempted by the Huey module, reading Reddit posts about the visual improvement of the Rift S over the 1st gen, and crawling Amazon and eBay for specials on the TM Warthog Hotas[emoji16] But it's worth it.

I removed the guard after 2 minutes as I found it a little ticklish. In my case, without the guard there is enough of a gap to see the keyboard. But even if this weren't the case, the improvement in resolution is really massive from the CV1, so if your IPD is in range don't hesitate - you will not regret it.

Just did the same a week ago, and it's a massive step up. Do it - you will not regret it (provided your IPD is within range) Sold my CV1 today, and before shipping I gave it one more go in DCS - while the CV1 still holds its own, it feels previous gen in comparison to the S. In the CV1 @1.7 pixel density, everything inside the cockpit looks crisp (excluding text), but outside of the cockpit the jagged edges are really apparent. With the Rift S, other than the text being completely clear, the outside of the cockpit appears as clear as the inside does in the CV1 - if this makes any sense at all. The image also appears to pop more in the S - color just seem more vibrant. Screen door effect is so much better that I hardly notice it at all. Audio is not nearly as bad as its made out to be - after a week I don't feel like I'm missing out on much. Somr have complained about the black levels on the S - I didn't find it to be a problem at all. Same for the 80hz refresh rate - I cannot tell the difference. Comfort wise, I find that halo style band much better. It doesn't put as much pressure on your face as the CV1 does, which makes longer sessions much easier. I did remote the nose guard as it was somewhat ticklish. Many reviewers have criticized the S for not being a generation up from the CV1 - I tend to disagree, as the improvement is significant. I finally feel like VR has matured with the S, and for the first time I can say that I'm content with where my VR experience is right now.

Thanks for the feedback - could be interesting if the HUD is only partially visible in real life too. I'll give the IPD settings a bash. Sent from my Nexus 5X using Tapatalk

Thanks, does this also correct the HUD readout size? At preset I cannot see the full HUD text unless I move the viewpoint forward, but then I'm sitting too close. Sent from my Nexus 5X using Tapatalk

Sir Yes Sir[emoji2], just completed both BFT03 and 04. Guess my Xplane habits of banking at 30' had to change. Thanks. Sent from my Nexus 5X using Tapatalk

Just experienced the same - flying out to sea at 300... Will try the quick turns as you suggest, but also a little dissapointed as it is turning out of be a really good training tool. Sent from my Nexus 5X using Tapatalk

[emoji106] Sent from my Nexus 5X using Tapatalk

Thanks - been wondering about this myself. Also wondering if there's any means of triggering different graphics profiles for VR and non-VR via command line ?

Hi, I'm no expert, but it depends on what you are trying to bind the axes as... If you are trying to assign as an axis in DCs, I don't see any reason why they shouldn't work ( that is, you click on assign axis, and then move the slider or rotary to assign). If on the other hand you are trying to assign to a button, then you would need the SST SW to output a keypress based on the slider / rotary position, and then assign that keypress in DCS. Perhaps share what you are trying to assign to the axes ? Sent from my Nexus 5X using Tapatalk

Yes, PoV hat 3 is configured as the throttle designator, and the scroll wheel depress to lock. Sent from my Nexus 5X using Tapatalk

Thanks for bumping this :thumbup: I've been looking for good missions / campaigns for the A10C, but as the module has been out for a while it's difficult to find the good content that stilll works. This seems very interesting - can't wait.