Mod Organizer 2 x Special K incompatibility in MGS3MC due to usvfs proxy not in use

[AkiraJkr]

The problem:

Game will start, sometimes without mods, but there will a terminal window constantly being spammed, specially after I try to focus on Metal Gear Solid 3. Problem specifically happens when MO2 and Special K are mixed together, with the _usvfs_proxyx86.exe present in the MO2 installation.

https://github.com/ModOrganizer2/modorganizer/assets/27028529/76b0e955-b437-4134-b771-302dc15492cd

EDIT; Apparently, this also makes Steam Input stop working(when there's no such problem if I use Special K without the mod manager.)

To Reproduce

1. Install Special K. Global or Local Injection does not make a difference.
2. Start the game through MO2 with Special K ready(again, either Global or Local Injection).
3. Game will start(a random chance of without mods), usvfs_proxy_x86.exe window will spam for a few seconds and stop, until you focus on the game, then infinitely repeat that.

Environment

• Mod Organizer Version that exhibits the issue: MO2 v2.5.1rc2
• Last Mod Organizer Version that did not exhibit the issue (if applicable): Not applicable.
• Desktop OS/version used to run Mod Organizer: Windows 11 Pro

Details:

Here's the thing with the problem. I can SAFELY remove usvfs_proxy_x86.exe from Mod Organizer 2(not a problem for portable installations), and the game will succesfully start with Special K, with all the mods loaded and working normally like nothing went wrong. Having MGSHDFix installed or not changes nothing on the behaviour. Having SkipLauncher set to true on MGSHDFix changes nothing on the behaviour. It's a 64-bit game. Sometimes Mod Organizer might keep the "locked while application is running" message even after closing the game, or closing steam, as steam.exe, x64launcher.exe and x86launcher.exe are holding the lock.

Here's how it's supposed to launch(I've used SkipLauncher in MGSHDFix to speed up the process, but result is still the same):

https://github.com/ModOrganizer2/modorganizer/assets/27028529/47d33aa4-2edd-40d7-9bdf-cafca769302f

Link to Mod Organizer logs:

USVFS:

https://gist.github.com/AkiraJkr/c5965382b94dde4c332896571229da6b

MO Interface:

https://gist.github.com/AkiraJkr/479742e125758625b18e39c2851f20fa

[NightHammer1000]

Exclude usvfs_proxy_x86.exe and usvfs_proxy_x64.exe in SKIF

Exclude steam.exe, SKIF.exe in MO2s VFS Blacklist.

Make sure MO2 is not running as Admin.

And the Issue is gone.

[AkiraJkr]

This(MO2 blacklisting) seems to fix the lock-ups found after closing the game, but not the window spamming of usvfs_proxy_x86.

Also, doesn't seem like excluding the proxies(in SKIF) changes anything.

[NightHammer1000]

Well. That's what fixed it for me in Multiple Games.

[NilTPL]

Sorry to butt in, how did you manage to create an instance for this game?