Hello There, Guest! Register

Narco Terror [NPUB31225]
#1
rpcs3-v0.0.1-2017-02-23-3e0c356b_win64
Reply
#2
RPCS3 v0.0.3-3-1572d01 Alpha
Still nothing.


Attached Files
.gz   RPCS3.log.gz (Size: 48.75 KB / Downloads: 17)
Reply
#3
RPCS3 v0.0.4-6226-17bfb3be Alpha
Still nothing, same errors as before.
Reply
#4
RPCS3 v0.0.5-6626-717f2b0ac

Code:
·F 0:00:32.421305 {SPU[0x2000002] Thread (Zen Job Worker 2)} SPU: Access violation reading location 0x0 (GET, size=0x30)
·F 0:00:32.421307 {SPU[0x2000001] Thread (Zen Job Worker 1)} SPU: Access violation reading location 0x0 (GET, size=0x30)
·F 0:00:32.421310 {SPU[0x2000000] Thread (Zen Job Worker 0)} SPU: Access violation reading location 0x0 (GET, size=0x30)


Attached Files
.gz   RPCS3.log.gz (Size: 55.21 KB / Downloads: 9)
Reply
#5
For documentation purposes:

The game suffers from a bug that makes it immediately destroys current buffer for the mfc get commands after pushing them, and before waiting for the command to finish.
If you execute the command before the destruction, the game would crash.
but if you emulate accurate delays between the SPU and the MFC, making the command execute after the destruction, it can work.
As long as there is not a cycle accurate mfc emulation, the game would never work on master builds. 
So I've made a workaround for this that makes the command wait until the game manually requasts the command to finish.

Disclaimer : due to the the inaccuracy it brings into the MFC, alot of games dont work with this commit!
https://github.com/elad335/rpcs3/commit/...944b0750b0


Attached Files Thumbnail(s)
   
Reply
#6
RPCS3 v0.0.5-7247-a93a40e8d Alpha | HEAD
Intel® Core™ i7-8700K CPU @ 3.70GHz | 12 Threads | 31.93 GiB RAM | AVX+ | TSX

E {rsx::thread} RSX: NV3089_IMAGE_IN_SIZE: Invalid blit dimensions passed
U {PPU[0x1000000] Thread (main_thread) [0x002b6568]} cellSysutil TODO: cellVideoOutConfigure(videoOut=0, config=*0xd00ffad0, option=*0x0, waitForEvent=0)
F {SPU[0x2000000] Thread (Zen Job Worker 0) [0x003bc]} MEM: Access violation reading location 0x0
F {SPU[0x2000001] Thread (Zen Job Worker 1) [0x003bc]} MEM: Access violation reading location 0x0
F {SPU[0x2000002] Thread (Zen Job Worker 2) [0x003bc]} MEM: Access violation reading location 0x0
Reply
#7
No need to worry too much about testing games that are already in nothing, the developers are ontop of it and we just dont post in the threads constantly, but as soon as they get fixed we will do a test and move them
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)