Matoking
protontricks-launch differs in results compared to launching from Steam
Description
I was trying to launch acs.exe (Assetto Corsa) with CSP installed (a mod for Assetto Corsa). The issue is that when launching from Steam it launches with CSP just fine, but when using protontricks-launch CSP isn't working. Furthermore I'm seeing some very odd graphical artifacts when using protontricks-launch, which aren't present when launching normally through Steam:
Here's the command I used: protontricks-launch --appid 244210 /home/philipp/.local/share/Steam/steamapps/common/assettocorsa/acs.exe
Is there some important difference between launching from Steam compared to using protontricks-launch which I'm not familiar with, or is this a bug?
The development version of Protontricks on the master branch sets additional environment variables to better match the actual Proton environment; those changes haven't been published in a new version yet. It could explain the wonky rendering since Protontricks didn't actually configure the environment to use the DXVK/vkd3d-proton DLLs until now...
You can follow the pipx installation instructions to install the development version. If you're on Arch or derivative, you can install protontricks-git from AUR.
Can you report back whether this solves the issue or not?
With the version from pipx the program is failing to start, for both regular and development versions.
Logs
$ protontricks-launch --appid 244210 /home/philipp/.local/share/Steam/steamapps/common/assettocorsa/acs.exe
pressure-vessel-wrap[377742]: W: Not sharing path --filesystem="/etc" with container because "/etc" is reserved by the container framework
pressure-vessel-wrap[377742]: W: Not sharing path --filesystem="/sbin" with container because "/sbin" is reserved by the container framework
fsync: up and running.
002c:fixme:winediag:loader_init wine-staging 9.0 is a testing version containing experimental patches.
002c:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org.
0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005
00a4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00a4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00a4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00a4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00a4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00a4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00a4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00a4:fixme:wineusb:query_id Unhandled ID query type 0x5.
00a4:fixme:wineusb:query_id Unhandled ID query type 0x5.
0120:err:ole:apartment_add_dll couldn't find function DllGetClassObject in L"C:\\windows\\system32\\uiautomationcore.dll"
0120:err:ole:com_get_class_object no class object {e22ad333-b25f-460c-83d0-0581107395c9} could be created for context 0x1
0120:err:tabtip:add_uia_event_handler Failed to create IUIAutomation interface, hr 0x800401f8