SebastianR

Hi. I use the normal axis for the rudder and two virtual axes for brakes using the same main axis. In general, when the brake operates at low speeds, the rudder has no interference and at high speeds it is the other way around. In airplanes with differential brake I use a joystick axis and in modern airplanes where the nws is activated manually, it does not interfere with me either. All the configuration I do from the vkb program.

rivatuner statistics server have seteable fps limiter. it works on vr

Copy from my post on fb: "hi, i've proved different combinations to get the way to understand the variables of vr performance. mostly used fpsvr to check cpu and gpu frametime and the most perfirmance killer was the shadows. even in only flat, cpu goes down (with everything in low to minimize gpu usage). cpu graphic turn to red with >30 and fps drop to 27. gpu varies with other settings, but cpu show low usage but too slow. it does no change if mhz is 3600 or 4200. so, with shadows off, everything goes like charm, with both fpsvr graphics in yellow/green. is there any way to reduce shadows draw distamce to test? specs: ryzen 3600, 16gb 3200, gtx 1070, rift s"

For sure wmr do not recognize the enviroment. due a change of reference point. That usualy passed me when i'd change from wheel drive to hotas or vice versa. you must reconfigure wmr as seat position (it's fast and easy)

Yes, same problem here

Sorry if is has been answered yet, but where is the landing gear sound?

425.31? i'm using that. but i think the problem is the usb 3.0 drivers

Hi. did you try with the public beta software of oculus?

doing new tests, if I land before the cables, it explodes. If it's just over the wires, there's no problem. always starting the mission from the carrier. thanks

I'm in steam. DCS Beta version 2.5.5.33184, A4e-c 1.3.1. I will try to reproduce exactly the issue under the same conditions, but in instant action, launch carrier, turn arround and try to landing. Allways explode. When i make the mission (in mission editor) sometimes it does't explode.

Starting from "instant action > carrier launch" the issue persist. Always explode returning to carrier