RPCS3 Forums

(08-29-2017, 07:46 AM)digitaldude Wrote: [ -> ]RPCS3 v0.0.3-3-85199e2

Need to move out a file called pxd_shader_ps3.ppu.sprx from bin/modules/ps3 folder then it will go to intro.

Yes. However, its crash after fmv. I hope devs can fix its as soon as they can. And yes, on new build same results    .

(01-10-2018, 11:20 PM)GrantKane Wrote: [ -> ]RPCS3 v0.0.4-6305-51a2b43d8 Alpha | HEAD
Black screen with FPS counter.

Quote:·F 0:06:27.140686 {PPU[0x1000000] Thread (main_thread) [0x00bf99ac]} class std::out_of_range thrown: invalid vector<T> subscript

Yes, on new build same error. I hope its may be fixed soon.

(05-15-2018, 12:35 PM)goku1988 Wrote: [ -> ]

(08-29-2017, 07:46 AM)digitaldude Wrote: [ -> ]RPCS3 v0.0.3-3-85199e2

Need to move out a file called pxd_shader_ps3.ppu.sprx from bin/modules/ps3 folder then it will go to intro.

Yes. However, its crash after fmv. I hope devs can fix its as soon as they can. And yes, on new build same results    .

(01-10-2018, 11:20 PM)GrantKane Wrote: [ -> ]RPCS3 v0.0.4-6305-51a2b43d8 Alpha | HEAD
Black screen with FPS counter.

Quote:·F 0:06:27.140686 {PPU[0x1000000] Thread (main_thread) [0x00bf99ac]} class std::out_of_range thrown: invalid vector<T> subscript

Yes, on new build same error. I hope its may be fixed soon.

Issue fixed in rpcs3-v0.0.5-c27604ba
Graphic error in some areas are serious.
Screenshot taken in Shimizu temple area and yorozuya in Gion

RPCS3 v0.0.5-7004-00c9b323c (build 0.0.5-7004)

Intro cutscene (pre-rendered) has some minor colour issues (at least with SPU LLVM), worst case:


Gameplay pics:




Log file: [attachment=8806]

rpcs3-v0.0.5-7491-986bb243_win64

i7-8700K | GTX 1070

Completed the game in 3rd of September, but at that time there were exploding vertices, making it not that enjoyable to play. As of October those issues have been fixed, and would be OK to move it to playable.

I wanna point out the remaining issues in the game:
 - SPU LLVM will show visual bugs on prerendered cutscenes, its not recommended to use;
 - The AVG Fps is 30 but the 1% and 0.1% are 15 in multiple areas (it can be a little distracting, depending on the person);
 - The only place where it can tank the fps by the most is in the main city (with this system);
 - Shadows can look slightly off in certain places but they are nowhere close to make it look too bad in the game;
 - AMD GPUs may suffer graphical issues.
 
For recommended settings use:
 - PPU LLVM
 - SPU ASMJIT
 - SPU Threads: Auto
 - Framelimit: Auto
 
Feel free to upscale the game as much as you want

rpcs3-v0.0.19-13008-48ad9596_win64

This may need  to be moved to ingame.

Certain special condition/title turtle races can't be started, game freezes on race selection,black screen,some sound playing on a loop,gpu usage none but cpu stays the same as normal gameplay, can't go into betting screen.

This bug blocks from getting a 100% completion.

The titles themselves:
these unlock special races but:
broken
最強無敗賞  Best Undefeated Award: 10 consecutive wins
金剛杯    Vajra Cup All Yokozuna Titles Conquered Yokozuna class races >横綱 races<

could've started
白寿賞    White Life Award: Turtle nearing the end of its life

haven't tested/gotten the title
最強敗者賞  Strongest Loser Award: 10 consecutive losses

I will test older rpcs3 versions i saved, after i will play around with the settings.

Should i open a github issue about this, or mention this bug in the big yakuza games bugs issue.

I have messed around with the logging settings and the log file may not give the full picture.

[attachment=23519]

(11-15-2021, 12:05 AM)kenzannotgood Wrote: [ -> ]rpcs3-v0.0.19-13008-48ad9596_win64

This may need  to be moved to ingame.

Certain special condition/title turtle races can't be started, game freezes on race selection,black screen,some sound playing on a loop,gpu usage none but cpu stays the same as normal gameplay, can't go into betting screen.

This bug blocks from getting a 100% completion.

Thanks for report. Please open a GitHub issue preferably attach a save file near the affected areas so they can reproduce the issue. And test a few other builds to see if it's a regression. Something from one year and then two years ago works. If you find it works in old builds but not new builds, try and narrow it down so we can determine where it broke.

As for moving this to ingame, will discuss with team. Personally I think it's okay to leave in playable as it only affects a few minigames and doesn't hinder ability to finish the game. But regardless, we will look into this.