Hello,
This is my problem :
Are there any settings related to the DirectX version used by RealFlight?
I came across this thread like this : AMD GPU with DirectX 9 and RealFlight, and it made me wonder if the issue I’m facing might be related to DirectX compatibility.
You can install support for any modern DirectX version, and performance is going to depend on the hardware. That said, programs use different timing mechanisms which are going to behave differently under WINE and DXVK.
You’ve said you can’t clear it even with “full throttle,” but not what is actually happening in game - your craft never goes full speed, or despite your speed saying it is maximum it is actually slower than expected? Does it drop frames?
I can’t think of any game-killing speed issues aside from the old obscure USB lag bug in some engines - Where an input device plugged into a USB 3 port is polling so fast, it causes in-game timing problems. If you plugged it into a USB 2 port (effectively capping the max polling speed) things worked fine.
The game performance is good, with no any lag.
I couldn’t find an option for V-Sync. I disabled ESYNC/FSYNC in Wine (not in the game itself), but it didn’t seem to make a difference.
I’m using the default Wine version. I switched it to Proton (Experimental), but that didn’t solve the issue either.
I rebooted the laptop with the updated settings, but the result was the same.
To verify the in-game clock, I used a real-world timer (cell phone), and the clock appeared to be functioning correctly — time passed normally in the game, neither too fast nor too slow.
It seems the issue may lie with the USB driver. Despite engaging full throttle with the drone transmitter, Challenge mode does not seem to engage full throttle on the aircraft. In normal simulation mode, I can check the throttle output, and the result was okay. but in Challenge mode, I can’t check the throttle output. so I’m not sure.
I changed below settings but the result was same :
(1) DXVK version : v2.4.1 → v2.3
(2) VKD3D : v2.13 → v2.10
(3) D3D Extras version : v2 → v1
(4) DXVK NVAPI version : 0.7.0 → 0.7.1
I’d enquire if people running natively have experienced the same problem, then at least you know its probably not your choice of OS+WINE, but something a bit more obscure.
Rather than a newer runner, maybe drop it back to a slightly older one. DirectX9 was released about 20 years ago or thereabouts. Anything much older than 7.2.2 might give you other issues though.
I’d still try and narrow down things to focus on first.
A road I’d take if I was out of other options - If you’ve got it installed outside of Steam in its own prefix, then you can build a new prefix and try a few more things like DLL overrides with winetricks, and maybe other DirectX options, like Gallium9.
It turns out that I had to retract the gear and flaps in order to achieve the shortest flight time.
I thought I had successfully set the gear and flaps, but when using Lutris, it seems that the USB controller stick functionality is messed up.
I’ve noticed a strange behavior, and since it’s a complex issue, I will post a separate thread for this problem. Thank you.
This flight requires 4 sticks and 2 switches.
If I configure only the 4 sticks, everything works fine. However, when I add 1 switch, it’s not recognized as a switch and is instead treated as another stick.
When I add a second switch, it takes control of one of the existing sticks, which causes all the settings to become misconfigured.
Sorry if I’m not explaining this clearly.
I was able to retract gears and flaps with keyboard, but I’m still figuring out why this problem happens…