BlackDaemonBound by Flame [BLES01952]
Started by BlackDaemon




3 posts in this topic
BlackDaemon
Moderator
*****


2
844 posts 374 threads Joined: Aug 2017
02-08-2017, 04:50 AM -
#1
Tested on recent master build v0.0.1-1669d0fd (PR #2352). With minimal resolution set (720x480) crashes on "press start" screen
Code:
...
E {rsx::thread} RSX: FBO check failed: 0x8cd6
E {rsx::thread} RSX: FBO check failed: 0x8cd6
E {rsx::thread} RSX: FBO check failed: 0x8cd6
S {SPU[0x2000002] Thread (CellSpursKernel2)} SPU: Function detected [0x37018-0x37078] (size=0x60)
...
S {SPU[0x2000003] Thread (CellSpursKernel3)} SPU: Function detected [0x02910-0x033a0] (size=0xa90)
E {PPU[0x1000000] Thread (main_thread) [0x00d08b80]} cellGcmSys: cellGcmSetTileInfo: bad compression mode! (10)
E {PPU[0x1000000] Thread (main_thread) [0x00d08b80]} cellGcmSys: cellGcmSetTileInfo: bad compression mode! (10)
E {PPU[0x1000000] Thread (main_thread) [0x00d08b80]} cellGcmSys: cellGcmSetTileInfo: bad compression mode! (10)
E {PPU[0x1000000] Thread (main_thread) [0x00d08b80]} cellGcmSys: cellGcmSetTileInfo: bad compression mode! (10)
E {PPU[0x1000000] Thread (main_thread) [0x00d08b80]} cellGcmSys: cellGcmSetTileInfo: bad compression mode! (10)
E {PPU[0x1000000] Thread (main_thread) [0x00d08b80]} cellGcmSys: cellGcmSetTileInfo: bad compression mode! (10)
E {PPU[0x1000000] Thread (main_thread) [0x00d08b80]} cellGcmSys: cellGcmSetTileInfo: bad compression mode! (10)
S {SPU[0x2000001] Thread (CellSpursKernel1)} SPU: Function detected [0x01410-0x04bfc] (size=0x37ec)
...
S {SPU[0x2000003] Thread (CellSpursKernel3)} SPU: Function detected [0x08520-0x08b1c] (size=0x5fc)
E {rsx::thread} RSX: Unknown/illegal instruction: 0x3d (forced unit 2)
S {SPU[0x2000000] Thread (CellSpursKernel0)} SPU: Function detected [0x03e80-0x042b0] (size=0x430)
S {SPU[0x2000001] Thread (CellSpursKernel1)} SPU: Function detected [0x037b0-0x03be0] (size=0x430)
S {SPU[0x2000003] Thread (CellSpursKernel3)} SPU: Function detected [0x03b70-0x03fa0] (size=0x430)
F {rsx::thread} class std::runtime_error thrown: Invalid RSX method 0x9d80 (arg=0x0)
(in file C:\rpcs3\rpcs3\Emu\RSX\rsx_methods.cpp:34)

LLE used
Code:
- libac3dec.prx
    - libac3dec2.prx
    - libadec.prx
    - libapostsrc_mini.prx
    - libat3dec.prx
    - libatrac3plus.prx
    - libatxdec.prx
    - libdmux.prx
    - libdmuxpamf.prx
    - libl10n.prx
    - libpamf.prx
    - libresc.prx
    - librtc.prx
    - libsail.prx
    - libsail_avi.prx
    - libsail_rec.prx
    - libsjvtd.prx
    - libsmvd2.prx
    - libsmvd4.prx
    - libspurs_jq.prx
    - libsre.prx
scribam
Member


0
21 posts 1 threads Joined: Feb 2018
02-25-2018, 02:07 PM -
#2
RPCS3 v0.0.5-6463-7753ac6 Alpha

Ingame


Attached Files Thumbnail(s)
           

.gz   RPCS3.log.gz (Size: 795.68 KB / Downloads: 2)
Deminating
RPCS3 Tester


1
388 posts 105 threads Joined: Mar 2018
04-17-2018, 12:22 AM -
#3
RPCS3 v0.0.5-6653-d957531da Alpha | HEAD

Intel® Core™ i5-6600K CPU @ 3.50GHz | 4 Threads | 15.92 GiB RAM | AVX+ | TSX


This game is perfectly playable as a game, good fps, sound, graphics.
I was going to make a report to put this into playable until I came back in for a log file and noticed loading from a save file doesn't work.
Once that works fine this game is easily playable.


Attached Files Thumbnail(s)
   

.gz   RPCS3.log.gz (Size: 282.94 KB / Downloads: 2)
UaQ - lover
Member


0
494 posts 46 threads Joined: Nov 2018
02-08-2020, 12:09 AM -
#4
RPCS3 v0.0.8-9528-54da9ac7 Alpha | HEAD | Firmware version: 4.85
Intel® Core™ i9-9900KF CPU @ 3.60GHz | 16 Threads | 15.91 GiB RAM | TSC: Bad | AVX+ | TSX

Operating system: Windows, Major: 10, Minor: 0, Build: 18363, Service Pack: none, Compatibility mode: 0
·! 0:00:00.000000 RSX: Found vulkan-compatible GPU: 'GeForce GTX 1070' running on driver 441.87.0.0


stats: playable

same as NPUB31459


ingame stable at 29 to 30fps all the time.


it's fine and no crash or freeze at all


log file and screenshots in Attachment


Attached Files Thumbnail(s)
           

.gz   RPCS3 Bound by Flame [BLES01952].log.gz (Size: 549.93 KB / Downloads: 1)
soon


Forum Jump:


Users browsing this thread: 1 Guest(s)