RPCS3 Forums

RPCS3 v0.0.3-3-9b8eb08 Alpha | HEAD

Quote:·F 0:00:06.714304 {PPU[0x1000008] Thread () [0x006857c4]} MEM: Access violation writing location 0xd00b1fb0

RPCS3 v0.0.5-7337-ed7012c9 Alpha | HEAD
After choosing teams:

Quote:·F 0:01:51.661620 {SPU[0x2000001] Thread (VCMathnodeSPUThread) [0x0976c]} class std::runtime_error thrown: Unknown STOP code: 0x111 (Out_MBox=0x87654321)
(in file c:\projects\rpcs3\rpcs3\emu\cell\sputhread.cpp:2329)

RPCS3 v0.0.6-7888-b879b322 Alph
Now ingame with good graphics, didn't play for long due to poor performance.

College Hoops 2K7 [BLUS30026]

RPCS3 0.0.6-7935-f30af3cc Alpha

Intel i9 9900K
16 GB 3000MHz DDR4
NVIDIA RTX 2080 (Driver 419.35)

Using Vulkan + default settings

Game should have PLAYABLE tag

Not sure how performance is on lower end systems, but I am getting a solid 35-45 FPS in game without any major graphical glitches. Only real issue I notice is very minor, but you will see in two of my screenshots that the basketball has a sort of "ghost" that you notice from time to time. I circled the ghost ball in yellow so it is easier to see. This also occurs in College Hoops 2K8 BLUS30078 (which is considered playable). Not sure if this is worthy of a github issue or if it's something likely to be fixed naturally as development continues.

Performance for this game isn't there yet, yeah it might perform alright on a 9900k but that's not good enough for us to consider it playable just yet. It still needs more performance.

(04-09-2019, 11:16 PM)Asinine Wrote: [ -> ]Performance for this game isn't there yet, yeah it might perform alright on a 9900k but that's not good enough for us to consider it playable just yet. It still needs more performance.

Fair enough. Just wanted to update every game i have on the forums.

Is that ball ghost issue something I should create a ticket for on github? Or just wait and see if it gets fixed?

RPCS3-v0.0.7-9004
Intel i9 9900K
16 GB 3000MHz DDR4
NVIDIA RTX 2080 (Driver 436.48)

Game should be moved to PLAYABLE. Game runs well and never dipped below 50 FPS during gameplay. The old "ghost ball issue" that I reported back in April on the compatibility page seems to be fixed as well. One of the better-running games I have tested so far.