And now even with latest build, it still no different. You can just scroll up a bit and you can see i was there before. I already mentioned the same last month in this post it's not like i didn't do what's was told about creating the patch.yml and put it to main directory. I can't chalk this up to luck so I encourage everyone still interested in emulating this game to check it out. The only extra step needed for me with the latest alpha build was the patch.yml and voila.
To repeat, you must create the patch.yml mentioned above inside the rpcs3 folder. I still have the last set of missions in Ultimate Mode to finish. (08-23-2019, 02:39 AM)cameronbarge Wrote: Screenshots for verification. Did you create the patch.yml in the rpcs3 main directory that reaper posted? That is what fixed it for me. Well maybe I just got lucky but that is unlikely. It seems this message still popup for everyone. The same msg still popup "Thread (CStageSceneBuilder) } MEM Access violation reading location 0x10010010" in the logs.Īnd this message always appear at the same situation after I beat Kshatriya. I can confirmed it is still NOT WORKING either the latest build or previous build. I've managed to finish Official Mode and am halfway through Ultimate Mode at the moment with no problems aside from the lag during the beginning of any mission after rebooting rpcs3. Not sure why you are getting the random freezes on the first mission. Thanks for posting about the patch reaper, I missed that.
Tried it with SPU ASMJIT and LLVM recompilers with and without SPU Cache, accurate xfloat, multithreaded rsx, etc.Ĭonfirmed working on this build with the patch.yml. PPU-da76bae72f6d8fef4865e63c4e75e91d8b7204ac: #Dynasty Warriors Gundam Reborn BLES02057 hackĪnd save it as "patch.yml" on the rpcs3 folderI just tested this on master build v0.0.6-8403 Alpha and I can confirm "Thread (CStageSceneBuilder) } MEM Access violation reading location 0x10010010" no longer occurs.īut I keep getting random freezes without recovery that makes it impossible to finish the first mission. (07-21-2019, 03:18 PM)AldoMC Wrote: (06-25-2019, 11:45 PM)reaper185 Wrote: isJuhn on Github made a quick patch to solve the issue for now.
0 kommentar(er)
