RPCS3 Forums
Majin and the Forsaken Kingdom [BLES00919] - Printable Version

+- RPCS3 Forums (https://forums.rpcs3.net)
+-- Forum: Commercial Games (https://forums.rpcs3.net/forum-4.html)
+--- Forum: Playable (https://forums.rpcs3.net/forum-5.html)
+--- Thread: Majin and the Forsaken Kingdom [BLES00919] (/thread-189046.html)



RE: Majin and the Forsaken Kingdom [BLES00919] - GrantKane - 06-12-2017

RPCS3 v0.0.2-6-8e64e9d Alpha
Black screen only.



RE: Majin and the Forsaken Kingdom [BLES00919] - GrantKane - 12-21-2017

RPCS3 v0.0.4-6253-a285409f Alpha | HEAD
After starting a new game:
OpenGL: BSOD.
Vulkan:
Quote:·F 0:02:02.441154 {rsx::thread} class std::runtime_error thrown: Assertion Failed! Vulkan API call failed with unrecoverable error: Device lost (Driver crashed with unspecified error or stopped responding and recovered) (VK_ERROR_DEVICE_LOST)
[Image: slUIDct.jpg]


RE: Majin and the Forsaken Kingdom [BLES00919] - Asinine - 10-03-2018

Playable as of the report here: https://forums.rpcs3.net/thread-181598.html


RE: Majin and the Forsaken Kingdom [BLES00919] - Harakiri - 06-05-2019

Game shouldn't be in "Playable" state - it randomly freezes without any RPCS3 error randomly between 5min and an hour.
This happens with the latest RPCS3 version from this week as well as the supposely reported version rpcs3-v0.0.5-7362-972de4c7_win64 from the other thread. I used the same settings as provided in the log by the user who reported it as playable. Switching GFX profile or recompiler option does not change the crash behaviour.


RE: Majin and the Forsaken Kingdom [BLES00919] - Ani - 06-05-2019

Are you sure it isn't due to the NVIDIA 400 series drivers hang? Upload a log file


RE: Majin and the Forsaken Kingdom [BLES00919] - Harakiri - 06-06-2019

(06-05-2019, 10:43 PM)Ani Wrote: Are you sure it isn't due to the NVIDIA 400 series drivers hang? Upload a log file

Here is the log file with the version that the previous reporter claimed it is playable. I had to remove all lines with {rsx::thread} RSX: NV3089_IMAGE_IN_SIZE: unknown origin (0) which still happen after the freeze because the log was already 140MB in size.
As in the latest version, there is no log entry upon freeze (game music keeps playing).

And no, I'm not sure if this isn't related to a driver of Nvidia - what kind of driver version should I try to reproduce this? This also happened when using OpenGL.

Happened again while being in windowed OpenGL during a battle were controller was vibrating - freeze and controller kept vibrating music was still playing. This was with the reported playable version.


RE: Majin and the Forsaken Kingdom [BLES00919] - digitaldude - 06-29-2019

Bot analyzied your log, resolution scale is 198% and also a comment on drivers, that might be the cause of the issue. The guy that tested it completed the game beginning to end.