Monitors: 4k 24" Dell monitor, 1080p 24" Asus monitorįully maxed out early 2017 Dell XPS 15, GTX 1050 4GB, 7700HQ, 1TB nvme SSD, 32GB RAM, 4k display.
Peripherals: Logitech G502, Ducky One 711Īudio: Xonar U7, O2 amplifier (RIP), HD6XX There may be some rogue patches floating around that fixes the launching issues, but I can't find them.Storage: 1TB 850 Evo, 1TB HDD, bunch of external hard drives This can be ignored as far as DXVK is concerned because until people come forth with the formula on howto even get the game to start, there is little point. I will later recompile wine-staging without the PBA patches and a couple others to see if it makes any difference (with a new prefix), but I'd be surprised if it does because those patches only affect opengl stuff. Not sure what the issue is, doesn't appear to be any information regarding this with 3.1.4.Īnd once again, no log outputs are given, so wine doesn't even get this to proper startup stage. Updated with RSI Launcher under windows, attempted to launch the game today under wine but it seems to stall with a zombie StarCitizen.exe. I will just boot into windows and update it and then test back under Linux, see what happens. UPDATE: So it seems the rsi launcher under wine fails to download all the files, it will grab only the data.p4k file and nothing else, so the verify process does not work. It might be better if I install this via vbox then try running it through wine. This isn't DXVK related and may be unique to my configuration. Wine: Unhandled exception 0xe0000008 in thread 5f at address 0x7b44f1b6 (thread 005f), starting debugger. At this point I'm only trying to get it to install correctly and unpack the game files which its not doing, until then I won't worry about recompiling wine.Ĭorruption of the data pack file might be occuring due to some wine bug that happens after 10mins or so: None the less it still does not verify correctly so I will attempt to download the data pack again. Anyway I got dotnet462 installed fine, seems it likes windows7 setting, win10 etc causes crashes.
0 kommentar(er)
