11-14-2018, 03:47 PM -
(11-13-2018, 10:43 PM)Ani Wrote: I need the full log file to find out what's causing that memory access violation.
Get such log file while using the latest build available on the website, if it outputs that memory access violation.
Your first log shows that the game crashes due to
·W 0:07:55.795840 {PPU[0x100004d] Thread (bnusCoreDecoderAT3PThread) [0x00399d00]} sys_memory: sys_memory_allocate(size=0xe0000, flags=0x200, alloc_addr=*0x0)
·F 0:07:55.796045 {PPU[0x100004d] Thread (bnusCoreDecoderAT3PThread) [0x00399d00]} MEM: Access violation writing location 0x0
This may be a bug with the emulator, as it's not accounting for NULL alloc_addr. This behavior will be checked on a real PS3 to find out what is the correct implementation, but it's a different issue than the one you indicated on your most recent post.
This time I have used the latest build from the download section, this is rpcs3-v0.0.5-7496-0e0a82e5_win64.
I tried first with OpenGl and then with Vulkan.
By the way, about CPU "generic" that I use, it is because in some cases if I leave "LLVM CPU" in config.YML untouched, without any name, the games crash the emulator.
Do I have to put any different name there from "generic" ? My CPU is Wolfdale, but if I leave LLVM CPU without a name, the emulator uses the name "penryn" ( this is a quad core CPU ) and that usually crashes some games.
Using the above mentioned rpcs3 build, I get a white screen with any configuration tested, and an error message pops up saying that "the program stopped working and I have to close it", it is again the memory violation issue.
( Update: today I tried a new rpcs3 build, which is rpcs3-v0.0.5-7497, tested it and had the same issue as in rpcs3-v0.0.5-7496 )
Please find the logs attachment in the following link:
https://drive.google.com/file/d/12vAJCXT...sp=sharing
This post was last modified: 11-14-2018, 07:15 PM by customizer.