FIVE-one wrote on 2020-12-18, 16:03:

Sorry for the dumb question but kjliew test was made on a Linux running computer ?
Maybe I'm trying the wrong way as I'm tinkering with VM on a Win10 computer.

Yes the most recent tests (that use qemu-5.2.0) were made on Linux, but I think it *should* work on a Win10 host too (WHPX is a Windows thing, similar to KVM on Linux).
Unfortunately you can't apply the Linux recipe on Win10 as is, you will need some special sauce (msys2?) to compile.
Robertmo's compilation guides should provide a better basis to work on (I can't vouch for their correctness on the most recent version though).
Earlier in that thread there were even binaries for Windows available, but the guest stubs won't work for the current version - the thing is pretty finicky about the versions between guest and host, they must match.

Ok I better stick it to VirtualBox and VMWare so. As I don't have any Linux OS installed and last time I worked on a Linux system was more than 10 years ago. (even if I know it's like bicycle, you never forget how to use it)

FIVE-one wrote on 2020-12-20, 09:59:

Ok I better stick it to VirtualBox and VMWare so. As I don't have any Linux OS installed and last time I worked on a Linux system was more than 10 years ago. (even if I know it's like bicycle, you never forget how to use it)

Or just wait a bit, maybe robertmo or someone else does a Win10 run at some point.

A quick update to the case :

I finaly have USB support AND music rendering on VirtualBox, using ACH97 sound device in the virtual machine configuration for the latter.
I dropped the VMWare option, as VMWare is totaly unable to detect any USB device. Too bad cause it is way more stable and doesn't have to mess up to make MIDI plays.

Still have the inherent black screen bugs sometimes but clicking on switch update the display and make anything visible.

However I sometimes have unknown crash and returns to Windows on some missions, but seems to be a game bug. Using latest iF-22 version (V5)

iF-22 Persian Gulf V5.0 is playable via DDrawCompat. My specs are Intel Celeron 2.1Ghz N2840 + Intel HD Graphics + 8GB DDR3 L RAM. Running natively on Windows 8.1 (and should work the same on Windows 10 & 11).

I've managed to solve the controller part by using a combination of x360ce (to hide the USB controller via the HIDGuardian function) and DS4Windows (with ViGEm + Bluetooth DS4). I am also using a specific DxWnd version & an imported profile (from the SourceForge forum discussing about iF-22) to make the game run on a single core-affinity processor with some colorkey fix. The only compatibility settings I used on the game .EXE is "run as administrator".

It still has multiple problems ranging from occasional freezes (after jet crashes/ exiting a mission), missing transparency effects & textures (becoming black boxes) when using Direct3D rendering, and the menu... which is accessible and working fine but the graphics are broken with white background at the supposedly black button/ link/ text area.

I'm using Dxwnd v2.04.26 build and download the profile (for IF-22 Dxwnd) + the dxwnd.dll file from this forum: https://sourceforge.net/p/dxwnd/discussion/ge … hread/6aa4a166/

Combined with DDrawCompat Ver.0.5.4 (works for me)

GUIDE TO USE A BLUETOOTH CONTROLLER (DS4) FOR IF-22 PERSIAN GULF V5.0 TO PLAY NATIVELY ON MODERN WINDOWS

Assuming that you've already download and install both x360ce v4.x (with HIDGuardian) and DS4Windows (with ViGEm), please follow the 5 steps below:

1) Make sure DS4 controller (via wireless Bluetooth) is turn off.

2) Open x360ce program, go to DEVICES and tick HIDE for the X360 USB controller (or any other USB wired controller attached) ONLY.

3) Make sure that USB wired controller is disappear from the "Set up USB game controller" list in Windows. The list should be empty (no controller is detected).

4) Open DS4Windows program which is pre-configured to automatically use a virtual X360 controller (XInput) with the DS4 if being detected.

5) Start iF-22 game by clicking the shortcut & wait a few seconds (depends... mine is until 4 seconds) before pushing PS logo button of the DS4 to start the controller. If failed, close the game & turn off DS4 then repeat again.

*Skip step 2 & 3 if you don't have any USB controller (like the X360 wired controller) plugged in to your computer. You might not need to download x360ce at all if you don't have or not using any USB wired controller.

*Use DXWND to start the game (currently used for my game) so that the starting sequence can make a brief "gap" in time for the Bluetooth controller to work and the game can start normally (showing on screen, not just running in the background in Task Manager)

*You can also try & test any other Bluetooth controller out there besides DS4, but the bottom line is, the Bluetooth capable controller must be made "virtual" in order to use XInput for the game to recognize it.

*The game will not showing on screen when start (but running in the background in Task Manager) if it detect any HID/ USB controller connected prior to launch. The game will not recognize DS4 (DInput) unless via a virtual controller emulation (ViGEm in DS4Windows) with X360 controller preset only (using XInput).