RealDCSpilot

CSV slaving after ground stabilization is the most important step in the procedure.

Could it be sound vibrations? Had this with directly attached off ear speakers. The sound vibrations can interfere with the gyro sensors in the headset if certain frequencies are at high levels.

Tested trim hat operation and it works as expected on my side. Maybe you guys have to check the FFB settings tab in controls to reverse force axis or something...

What? It's working well, just like in ED's helicopter modules. You might have missed to make this special setting: You should also disable trimming for pedals, because this could cause the most disorientation when it works in insta trim mode, while your cyclic is working realistic with FFB. Better get used to holding it in place with your feet everytime you trim.

Yeah, the PSVR2 has great potential to be the new leading headset for PCVR. Feature rich on a low price. Can't wait to try it out soon. OLED, HDR, eye tracking, great controllers, reasonable resolution per eye. All rumors say it will be directly connected via adapter box to display port. Nvidia compability was just confirmed...

@BIGNEWY So with the unified build and 6 weeks release cycle, what's the plan about hotfixes? Are we now really doomed to wait 6 weeks everytime for getting serious issues fixed?

Well, in fact, they are most of the time. With TrackIR set to exponential head turning, they can look at their six and would have broken their necks a thousand times in real life already. It's the same with the VR tool called "Necksafer". xD

@Hiob I don't really get why we have to explain this to you. Why are you not doing something simple as typing "Größenwahrnehmung und Augenabstand" in your search engine?

Why all the fancy dancing around the matter? In VR options you can force IPD. Simply try 40mm vs 80 mm and check what happens. (Hint: one will transform you in a toddler and the other one into a giant.)

Guys, what kind of controller hardware are you using during developing your modules? Why are you using only 50% of the analog axis for certain axis bindings? Latest example: F-15E HUD brightness axis. If i bind one of my axis dials to it it works like: 0%-50% nothing, 50%-100% = 0% brightness to 100% brightness.

Your hardware is ready... Ever tried VR already? Basically, you have to check if you are sensible to motion sickness. "good enough" is the next thing, the expectations about "sharpness". Simply don't expect monitor replacement here. This point is currently what is expected to change the most in the next years. Current "normal" generation is having panel resolutions between 2000 - 3000 pixels, next gen is above 3000. From my experience since 2014, i will stop caring about VR panel resolution when we reach 3800x3800 at reasonable price ranges. Your first headset will not be your last headset. However, VR is delivering on so much other important factors where monitors will never be able to shine.

Didn't see this post until now... I don't know what you are doing there, but only 40fps with a 4080 means that something isn't right on your machine. You may have overtinkered with stuff you don't know much about or simply misconfigured Windows or whatever. In December you should have got your fps close to this: and after the latest patch it should even improve close to this:

Dream on little man...

VD quality setting sets the main resolution per eye. DCS's PD setting can be used as a multiplicator for that main resolution for fine tuning. As an example, on my end i use "godlike" (3120x3120) and PD of 1.2 to push the super sampling resolution to 3744x3744. Then DLSS takes this resolution and puts it down to 2496x2496 to rescale it back to 3744x3744. Sharpening on 1.0 and it looks pretty crisp, absolutely zero aliasing.

Have bound these two and they are now working exactly how i need it. Before they only worked as "press and hold" buttons. @nima2014 @Kirk66 However, if you find other buttons not working as expected, report them!

Saw this on the Syria map and Marianas. My real position doesn't match the tablet's map position with a huge offset (couple hundred meters? didn't measure it...).

There are two options now for certain switches!

It's definitely only something on your side and not related to the module. I reconfigured all my inputs yesterday and have not the slightest idea what you are talking about. Everything works well, as expected. You should check your system much deeper for control issues that come with your hardware, double bindings and driver/firmware settings.

Fixed with the latest update!

Alright, thanks!

For the Master Arm Switch i have to hold the button to keep it in position, for the Flare Dispenser Button Cover too. On other switches it works as expected, like Weapons Panel STDBY/ON or Left Pylon Arming Switch Cover. Why? Is this an oversight?

Because it's the best VR anti aliasing option since... years? The super sampling from 2496x2496 -> 3744x3744 per eye works really well for me. Thanks ED!

@rcalfa @Johnny Dioxin Check in LAB settings if hand tracking is enabled and disable it.

@Bashibazouk To rule out that the problem might come from a different angle, can you please provide some screenshots from the beginning of that mission? Maybe it's a terrain physics problem and the skids are stuck into the ground. Please take a closer look from the outside and provide some screenhots. And one screenshot with the loadout from the ground crew menu please.

This is the golden rule for any helicopter. And you almost never need more than 50% fuel unless you plan to fly around for hours. I'm flying the Gazelle very often on the Syria map. Never had this issue. Please check your weight/loadout and make sure to have only the amount of fuel that is really needed. Also check if your start trim is slightly left and back and countering mainrotor torque with pedals is smoothly synchronized with raising the collective.