Stephen Miller
Stephen Miller
@Tarik366 Please provide an update this issue, and include a log of the crash. Until a log is provided, this issue report is invalid.
Uncharted 4 gets further on Linux devices, crashing on ``` [Debug] vector_memory.cpp:177 operator(): Assertion Failed! Non immediate offset not supported ``` [shad_log.txt](https://github.com/user-attachments/files/19491584/shad_log.txt)
@Hermiten This error is still present on current builds. Here's a log from the current WIP showing this. [shad_log.txt](https://github.com/user-attachments/files/18267366/shad_log.txt) I'll update the compatibility listing when I have a chance.
Yes, the game gets past this halt, but then immediately crashes from what appears to be an issue with sceKernelAvailableFlexibleMemorySize. These are the printed errors. ``` [Kernel.Vmm] memory_management.cpp:sceKernelAvailableFlexibleMemorySize:246: called size...
Looking at logs from running the game on a base PS4, I think the issue is likely with how we handle flexible memory size assignments instead. I think the game...
The specific issue I was reporting in this issue was fixed, the game is crashing on something else now.
We know why it's crashing, but we haven't found a proper solution yet. Either way, we've got a while before larger games start working, shadPS4 is still very early in...
Readbacks is known to fix the vertex explosions described here. This issue is still open because our readbacks implementation is imperfect, and regresses some games (on top of the performance...
Closing as completed since the readbacks setting is known to fix the issues described here.