Dear Mtodor, here you are:
On my system the release version - contrary to the latest beta two days before - doesn't work,
My setup is:
- Antergos 64bit
- 4 GB Sapphire Radeon R9 380X Nitro with latest Mesa-drivers (open source)
- Intel i5-2500K CPU @ 3.30GHz × 4
- 16 GB RAM
- Play on Linux as Wine Client
- wine 17 (tried wine 16-staging as well)
- Steam running under POL, installed as described on winehq (report for: Arch Linux x86_64, Aug 25 2017, 2.15-staging, by: writergeek; PLEASE NOTE other games update and run on this Steam installation!)
Installing the game via Steam (for Windows) on a 64bit Wine worked.
Issues:
- couldn't install dotnet35, 40 etc. (neither via POL nor via console and wintricks) in my 64bit-Prefix (error: "Doesn't install on a 64bit-Prefix")
- whilst the latest Beta worked rather flawlessly still on April 13 2017 (!) the release version causes some Directx11 related errors and just crashes.
Workarounds:
1) Steam button actually launches "SupportTool.exe" from .../steamapps/common/Divinity Original Sin 2/bin
which causes a .NET Framework error.
- (well known) workaround: Launching Divinity via the "EoCApp.exe" within the same directory
2) Next: ntlm authentification error
- workaround: installing the "python2-ntlm-auth" packages
3) Finally "BAD WINDOW" error
Tried registry workaround: "MaxVersionGL key to the (DWORD hexadecimal) value 30002", but Divinity just shows its mouse cursor on my desktop and crashes.
Let's hope we find a general solution or proper general work around soon. Thank you very much!
Cecco
EDIT: Just ran it again in windowed mode (set via winecfg), now I 'merely' get this error:
fixme:d3d:swapchain_init The application requested more than one back buffer, this is not properly supported.
Please configure the application to use double buffering (1 back buffer) if possible.
Is there a way to fix this manually via registry entry?
Last edited by Cecco d'Ascoli; 18/09/17 01:23 PM. Reason: tried in windowed mode as well
