-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gallium Nine issues #2
Comments
This is where the game stops and remain in that state. I had to terminate the process after a while... |
@Mastergatto It doesn't even get to run wine. This seems like a problem with the steam client. |
Just to be clear, without the option to turn on Gallium Nine, all games run fine like on normal Proton. |
@Mastergatto So just to be sure run the game again with |
The game (A Hat in Time) runs fine though. I want to thank you for putting efforts and time in making a version of Proton with Gallium Nine patches, if you manage to fix this issue you'll make my day 👍 |
Dishonored: Dead Space
|
@Mastergatto Thank you very much, it's weird you didn't get to see the stacktrace ? Do you have anything set in a @archfan Can you confirm that a wine patched with gallium nine works on your system ? I get the same kind of trace on my nvidia, I need to do more research using known to work wine versions patched with gallium nine. |
As far as I remember, no, I haven't done anything with WINEDEBUG, but I'll have to find why it doesn't output the stacktrace |
Ok, this is it it seems :
Doing this :
Gives
It looks like a library location screw up. Could you try putting the symbolic link and try to run again ? |
A Hat in Time is 64-bit. But with other games like Dragon Age: Origins it worked!
|
@Mastergatto Cool! The modulepath for the d3dadapter9 can be set via registry
Yeah no problem you can specify for both arch using You can apply the following patch to your proton
What would be the best way to determine the location of the So basically since this was compiled with the steam-runtime, it's no multilib. It will compile wine 64 using the 64bit docker image and wine 32 with the 32bit docker image. So by default the location of the
I'll put
|
Also, #2 (comment) indicates lack of DRI3. According to following PPA, DRI3 needs to specified in xorg.conf. I will try to test that tomorrow on an AMD laptop. https://launchpad.net/~commendsarnex/+archive/ubuntu/winedri3 |
Ok, hotfixed version available for testing : https://github.com/popsUlfr/Proton/releases/tag/proton-3.16-5-gne-0.1.1 Thank you all :) |
Thank you very much for this, nice job! 👍 (Meanwhile, Proton 3.16-6 has been released now, bad timing) |
@Mastergatto Ah yes I just saw that. There's some very cool stuff in that release I'll definitely update, and if I get some more feedback about how gallium nine runs for users I'll consider submitting a pull request. |
Doesn't function on old hardwareGreetings, I am not sure whether I should submit separate issues for following. As I promised, I fetched an old AMD GPU laptop to test this fork of Proton. Specs: OS: Mint 19.1 Mate Warhammer 40,000: Dawn of War - Dark Crusade (officially whitelisted 32 bit Direct3D 9 game) When I tried to launch the game for the first time with When I clicked OK, it showed me configuration window with no option: Then I deleted the launch parameter to relaunch the game via WINED3D, the game launched properly without Gallium Nine. Then I quit the game, re-enter the launch parameter, attempted to launch the game; I got a different warning and couldn't launch the game again: Log: Dear Esther (original version; 32 bit Direct3D 9 game, Source Engine) Doesn't launch. It launches and plays properly if the launch argument is deleted. Log: Path of Exile (F2P game, DirectX 9 and DirectX 9 EX version are 32 bit, DirectX 11 version supports 64 bit) When I tried to launch the game for the first time with Log: Also, Deus Ex with enhanced Direct3D 9 renderer launched and played with Gallium Nine only once, later attempts failed. But as that is an unofficial custom renderer and there exist another custom OpenGL renderer from the same dev that works just fine, I don't mind at all. https://www.cwdohnal.com/utglr/ As this is a fairly old laptop, I am not sure if it is meant to run Gallium Nine. To make sure, I will later attempt to run those games directly with "Wine + Gallium Nine" build; https://launchpad.net/~commendsarnex/+archive/ubuntu/winedri3 |
On Ubuntu 18.04 I had to set: |
Yes, yes! Thank you @andy-d1969! Changing Gallium Nine module path solved the problem. DoW:DC, Dear Esther, PoE and Deus Ex with enhanced Direct3D 9 renderer launch just fine. Here are libd3dadapter9 file locations on Mint 19.1 and most probably on Ubuntu 18.04: libd3dadapter9-mesa
libd3dadapter9-mesa:i386
By the way, Steam Overlay does not work with DoW:DC and Dear Esther when Gallium Nine is active. Interestingly enough, when Gallium Nine isn't active, Steam Overlay works with those titles. DoW:DC Dear Esther: Lastly, following is my Steam Library. Does anyone knows a 64 bit Direct3D 9 game that doesn't have a Linux version in that list, so I can test it? Sure, there might be some Linux games that happens to be also 64 bit Direct3D 9, but I don't want to deal with /tmp/proton_$USER/run for external games at this point. https://steamcommunity.com/id/realtunya/games/?tab=all&sort=name Edit: https://pcgamingwiki.com/wiki/Smite#API Edit 2: Smite doesn't function with Proton or Wine due to Easy Anti-Cheat software. There goes my 18 GB download... |
Dungeon Defenders II (F2P 64 bit Direct3D 9 game) The game doesn't work out of box because of lack of dependencies. When the game is launched, a launcher shows up; When PLAY button is clicked, instead of launching the game, following error window appears: This happens with Proton 3.16-5 Gallium Nine Extras 0.1.1 regardless of Gallium Nine. When, I switch to Proton 3.16-6 Beta, the game installs 5 dependencies. After digging a lot, it turned out that those are Microsoft Visual C++ 2008 x86, x68; Microsoft Visual C++ 2013 x86, x64 and DirectX End-User Runtimes (June 2010). Those dependencies are stored in
After completing these steps, the game properly launched and played. I would argue, dependency installation issue has to be investigated. Finally I can confirm that Proton with Gallium Nine patches does run 64 bit Direct3D 9 games. Edit: Just like DoW:DC and Dear Esther, Steam Overlay doesn't work with DD2 when Gallium Nine active. |
@rea987 I'm not sure it is possible for the Steam overlay to work since it only has OpenGL and Vulkan version. Yet Gallium Nine exposes native d3d9 where api calls do not go through OpenGL or Vulkan. About your errors on launch I had something similar happen to me with Dark Souls where even wined3d would just crash the game immediately. |
New release with Proton 3.16-6 : https://github.com/popsUlfr/Proton/releases/tag/proton-3.16-6-gne-0.1.1 |
@rea987: "ATI Radeon HD 4650" this card should be supported by gallium nine.
Surprising, this should work. At least Steam Overlay works for me with nine (but I haven't tried Proton).
Surprised to see some ddx still opt for DRI2, and that the DRI2 fallback requirements are not met... what configuration was it ? A small note for people having memory issues (or related mysterious crashes) with nine, but not without it: Some 32bits games really need a lot of virtual address space, and nine is more sensitive, as the libs are mapped into address space, and the wine d3d libs are loaded as well (thus more space taken than without). Forcing large address aware can help. Or disabling d3d11 (fewer libs loaded). Plus there are tricks to reduce pulseaudio virtual space usage. And mesa also is not releasing virtual space when it should for some textures, there is a patch on the mailing list so, it should be better in future releases. |
I solved the issue, my problem was related with PROTON_GALLIUM_NINE_MODULEPATH. Steam Overlay should work if you use Steam for Windows via Nine, because Steam Overlay that use Direct3D 9 is renderer via Nine in that case. But, if you use Proton with Nine patches, Steam Overlay shouldn't work at this point, since Steam Overlay for Linux is renderer by OpenGL which isn't provided by Nine. In fact, I use that defect to make sure if Nine is active or not. Adding |
I'm on Mint 19.1 Mate echo PROTON_GALLIUM_NINE_MODULEPATH="$(find /usr ( -type f -o -type l ) -name d3dadapter9.so.1 -exec sh -c 'file -L "{}" | grep -q "ELF 32-bit"' ; -print -quit 2>/dev/null):$(find /usr ( -type f -o -type l ) -name d3dadapter9.so.1 -exec sh -c 'file -L "{}" | grep -q "ELF 64-bit"' ; -print -quit 2>/dev/null)" |
@logan001 https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers I suggest using Ubuntu 18.10 to get d3dadapter9 from default repos. |
General thread to discuss problems running games with gallium nine on.
Make sure you have mesa installed with gallium nine enabled.
In Ubuntu, Mint use the following PPA :
https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers
In the game's launch options put :
PROTON_DUMP_DEBUG_COMMANDS=1 PROTON_USE_GALLIUM_NINE=1 %command%
This will dump scripts into
/tmp/proton_<username>
Use the
./run
script to launch the game or./run winecfg
to access the wine configuration.Read through the wiki : https://github.com/popsUlfr/Proton/wiki
Especially the debugging page : https://github.com/popsUlfr/Proton/wiki/Debugging
The text was updated successfully, but these errors were encountered: