Open omicron-b opened 6 years ago
You could try switching to OpenGL manually. Find the Rune.ini and enable the OpenGL option and disable Direct3D.
This was solved by verifying integrity of game files, one of the files was corrupted.
Now, the issue is this: on first run, game defaults to GameRenderDevice=D3D9Drv.D3D9RenderDevice
in Rune.ini
This causes low fps and graphical glitches. You have to go to Video - Video Driver - Change. This will close the game and lead you through a setup wizard, which, with all default settings, will switch you to GameRenderDevice=D3DDrv.D3DRenderDevice
After that, game works perfect. Can anyone confirm the same happens with fresh install? I removed Rune.ini and Default.ini and re-validated the files just to be sure the issue persists.
Didn't look at Rune.ini at any point, but yes, for me fresh install defaulted to what GUI refers as software renderer which was slow and glitchy. Changed to D3D from options and it works fine after that. My Steam info here.
Works great out of the box. The new Direct3D 11 render fixes alot of bugs, especially since DXVK is now utilized. Theres a mod that includes the cut content called "Rune Extended" ( https://www.moddb.com/games/rune/downloads/rune-extended-mod-for-missing-levels).
Is anyone seeing an issue with this game and Proton 4.11-9 that would block it from being whitelisted?
I do not see any issue anymore with default settings and Proton 4.11-9
Just installed it, seems to work fine with Proton 4.11-9.
Tested on Mint 18.3 and Arch with Proton 3.7-3 and 3.7-5 Beta https://gist.github.com/omicron-b/f697ca5bd4b8e25a98cb1d721e10edfd Update: crash was caused by some corrupted game file. ~attached is an engine's crash information game has a safe mode - the result is same game has platinum Wine rating, will test with Wine later no relevant stdout it seems, please note
html_chrome.cpp (394) : Assertion Failed
happens every time, not related to any game~