Some suggest the engine is just buggy and works fine if locked to a single CPU core, but that does not help in my case (tried with taskset and "-CPUCount:1 -CPUPriority:high " -parameters for the exe.
Also, this slowdown is a common issue on Windows and even Consoles, judging from some Google Searches I've found. It is still there, but the effect is perhaps 1/3 - 1/5 of the slowdown on while running trough Proton. Haven't found a workaround, but can say that running trough plain Wine (and Windows Steam) the slowdown is much less severe. I get very fluent FPS otherwise, but the galaxy map drops FTP to around 5-20 (don't have a functioning FPS counter, but I presume it is around 60+ FPS otherwise). A similar slowdown is present at the beacon in the first mission, but not so severe.
For example, the galaxy map thing in the very beginning (also during the starting split screencutscene for a few split seconds) causes this. Mass Effect has very poor FPS in certain places with Proton. I had actually been working on Skyrim SE. Unfortunate, I didn't take note of what it reset, but it wasn't an intentional change, I do know that. I was able to fix this with a git reset -hard (I have compatdata as a Git repo). So within the first hour seeing a crash is a big deal to me.but I just reset whatever changed so I pushed it from my mind and moved on to something else. Both Mass Effect 1&2 run BETTER in Wine/CrossOver than on Windows 7. In fact, it has run nearly perfectly, and I can't actually remember if it has ever crashed before in Linux (On Windows it sure did!). In the 100+ hours I've played Mass Effect in wine/CrossOver (it was the first game I beat in Linux, and I've beat it more times there after) I've never gotten an error related to pure virtual functions. I'm feeling quite silly I should have spent more time on this, however I didn't think to report it until now. Issue transferred from posted on T01:47:52: Mass Effect crashes with a Pure Virtual Function error.
0 kommentar(er)
