Software No 3D acceleration on virtualized W11

[Laserpithium]

Dear orbiters,

I tried to install latest Orbiter 2024 under a virtualized Windows 11. Virtualized, because I am using Linux, and the Orbiter Linux version (which is already great to exist, thank you for this), is not on par yet with the original Windows version.
I am able to launch Orbiter, but can't activate the hardware acceleration (processor AMD Ryzen 9600X, using the iGPU).

• Under the host Linux system, I do have proper hardware acceleration
• Under the guest Windows 11 system, everything seems to be properly detected at the OS level:

* The list of peripherals do show the Virtio GPU (the name of the virtualized GPU), and show it as running properly
* When I do a dxdiag under Windows, the virtual GPU is properly recognized, and the DirectDraw, Direct3D and AGP texture acceleration is shown as activated. (I just have "DirectX 12 Ultimate" as not activated, not sure what this is).

I am using Orbiter-ng, adding the EnableDX12Wrapper = 1 in D3D9.cfg file.

My issue: in the Video tab, I can only see as 3D device the "Microsoft Basic Direct Rendered" (although I do have selected the D3D9 client). When starting a scenario, I can see D3D12/D3D9 (through the wrapper) is activated, and Orbiter runs properly (no CTD etc). But at ~1 FPS, making it unusable.

Going through a VM is for sure not helping, so I could understand running into some kind of CTD etc at launch. Where I am a bit puzzled is that I do not even see the GPU in the video tab. I mean, it appears properly in the list of peripherals, the Windows dxdiag shows hardware acceleration as enabled, but it is not even displayed in the launchpad.

I tried setting EnableDX12Wrapper = 0 and installing the old D3D9 file from June 2010 (downloaded on Microsoft website): same thing.

I did not see anything enlightning in the "advanced options" (page that I can access, and I did create there the symlinks as recommended).

 

[johnnymanly]

I can't help you with virtualization but are you against using Wine?

 

[Laserpithium]

No, not at all.
I actually tried couple of years ago to have Orbiter running under Wine, never succeeded. That was however ~5 years ago, so most probably things have matured since then.
Based on this bad experience, I tried that time another way around (virtualization). But if you could recommend me a link showing how to have Orbiter running properly under Wine, I would be happy with it!

 

[johnnymanly]

If I can remember, I think you only need to install wine, then the June10 DX runtime and your good.
Install the DX runtime to an empty folder. It will create a lot of files. Look for DXSETUP.exe and run that.

 

[Laserpithium]

I works like a charm!
Still need to try with the joystick, but it loads and runs smoothly! Thank you for the help!

 

[Laserpithium]

Arf, joystick not working.
It is properly detected when I do "wine control" (with proper name, and things move fine on the screen according to the move of the joystick), but I only see a "disabled" in the orbiter launch pad.
Some idea?

 

[johnnymanly]

No, mine doesn't work either.

 

[DaveS]

X-52? Then see this thread: https://www.orbiter-forum.com/threads/logitech-x52.42182/

 

[Laserpithium]

OK, I managed to get it work!
As usual, I simply had to RTFM, in this specific case: https://wiki.archlinux.org/title/Wine (as I am an Archlinux user). Installing the lib32-sdl2 package (from AUR) solved the issue.
Could someone explains me however how to configure the joystick? (programming the behavior of each button etc)? I did not found anything explicit on that in the Orbiter manual, and the keymap.cfg file looks more "keyboard centric" than "joystick centric".

EDIT: actually, this is not even needed to install this package from AUR. Simply installing lib32-sdl2-compat is enough.