Managor
Published
Steam reports "Application load error 2:0000065558" and does not launch the game.
I was able to launch the game by manually navigating to the game files and launching AssassinsCreed_Dx9.exe
Works fine once you let the game compile its shaders
Shader compilation was rough.
I am able to get to the main menu but selecting new game doesn't allow me to get into the game.
Works well
From my previous report, I was running the game of of bcachefs drive. Apparently inode64 doesn't jive well with 32 bit Source games. The game runs well if you use tried and tested filesystems.
Not entirely sure if some anticheat prevents you from connecting to the time trial record servers. I was never able to connect to them. I'm not entirely sure if the servers are just offline either. The game itself works perfectly and the time trial records get saved locally.
The game crashes randomly and after reconnecting to the same map it keeps crashing.
Some Unity window appears and the game closes immediately after.
Can be made to run once until it crashes on alt-tab. Haven't been able to get into the title screen a second time.
At least the game now launches
The game launches and crases as soon as the ESRB warning is over. If you alt-tab during the ESRB, you can move forward to the loading screen that doesn't go anywhere.
The corner of the minimap sometimes shows a gap in the edge of it and very rarely there is a single line going across the terrain right behind your vehicle.
The VRAM is limited to 512MB, but that seems to be a common bug among Windows, Linux, AMD and Nvidia users.
It finally runs OOTB now that GFWL is removed.
To override the VRAM limitation, download the dinput8.dll from here https://github.com/colistro123/GTAIV_ExtendVidMem
Make sure that your browser doesn't block the download. Otherwise the destination file will be 0 bytes.
After that add WINEDLLOVERRIDES="dinput8=n,b" %command% as a launch option for the game
The latest patch enabled -availablevidmem but broke Proton compatibility completely
The loading screens last a lifetime
Runs perfectly. A single custom server crashes with "Engine Error Map_LoadModelGuts: Map with no texinfo, maps/l4d_hospotal03_sewers.bsp" Being an isolated incident, I'd be willing to bet the same thing happens on windows too.
The Nexon launcher appear for a brief second, after which it disappears but leaves the process running. The game must be killed manually.
If you turn down the graphics, you can play the game just fine
Sometimes a sound source would cut out completely
Had to turn graphics down to not experience lag
You need to disable PhysX from the Mirror's edge settings for it to run smoothly. There are times when the game will grind to a halt if PhysX is enabled.
TKG kernel with fsync2
Noita seems to utilize WaitForMultipleObjects() extensively. The game will lag a lot waiting for the next queued lock to be free when it just needs one lock somewhere further in the queue. With fsync2, the Linux kernel is able to replicate the windows behavior and the game will not lag.
Game won't launch but wineserver stays on. Steam will think the game is running even if nothing shows
The game runs perfectly for about 0.5-1 hours until the game becomes a laggy mess. I presume the it's due to a memory leak. When the game reaches around 770MB of memory usage, the lag starts
It's playable.
Some chairs were lit up stronger than they should
Crashes sometimes when alt-tabbing
Regressed
Unable to perform first time setup with 5.0. You can switch to 4.11 to set it up and then switch back to 5.0
The game runs perfectly. Controller support is on the other hand isn't perfect. The game recognizes and uses generic controllers like DS3 but not Steam Input controllers like SC
Starts up but crashes on the first loading screen before main menu
The program itself works great. Visually the program is doing what it's supposed to do. However movies that it renders are completely black with sound.
Primary viewport doen't show anything unless SFM is launched with -noqt -usevgui
Exporting a movie exports only a black screen
Remember to add -noqt -usevgui when launching.
This game is even more of a mess than it is on Windows
Space and M1 would not work occasionally in Ripto's Rage.
The loarding screen lags even if the game is not compiling shaders.
The game starts up but results in a black screen. I don't know if the .NET 3.0 warning 'You must use "Turn Windows features on or off" in the Control Panel to install or configure Microsoft .NET Framework 3.0' warning has anything to do with this.
The game boots now that there is CEG support, but it crashes as soon as you try to start a new game
Once the shaders are compiled, the game is as good as on windows
Shader compilation takes a lot of time.
The shader generation is way too much.
The game generates a lot of shaders all the way up to the very end of the game. You'd have to play the game through several times before they maybe stop
The game crashes when the shader cache reaches the maximum memory capacity that a 32-bit program can address.
The game runs really well but suffers from random crashes. When you turn on the tv in your home world for example. Also hangs on exit.
