(07-19-2017, 12:32 AM)Butz_san Wrote: [ -> ]This is the log
Possibly graphics driver crash from RPCS3 doing something bad...
(07-23-2017, 05:19 AM)zerocold1981 Wrote: [ -> ]And I will share the log. It's big, I tried different settings in it, volcano, opengl. Version of the emulator for person 5, but on new assemblies as well, so I think it does not depend on it. If required, I can download another and post a log.
That is only incomplete console output, not the log file. rpcs3.log is found next to rpcs3.exe.
For both of you, try to enable strict rendering mode. Also try the earlier reported good version:
https://ci.appveyor.com/project/rpcs3/rp.../artifacts
(07-24-2017, 01:25 PM)ssshadow Wrote: [ -> ] (07-19-2017, 12:32 AM)Butz_san Wrote: [ -> ]This is the log
Possibly graphics driver crash from RPCS3 doing something bad...
(07-23-2017, 05:19 AM)zerocold1981 Wrote: [ -> ]And I will share the log. It's big, I tried different settings in it, volcano, opengl. Version of the emulator for person 5, but on new assemblies as well, so I think it does not depend on it. If required, I can download another and post a log.
That is only incomplete console output, not the log file. rpcs3.log is found next to rpcs3.exe.
For both of you, try to enable strict rendering mode. Also try the earlier reported good version: https://ci.appveyor.com/project/rpcs3/rp.../artifacts
In last revisions of RPCS3 the game is working again
(07-24-2017, 04:56 PM)Butz_san Wrote: [ -> ]In last revisions of RPCS3 the game is working again
Thank you, I saw your video on YouTube. If I am not mistaken
The game keeps freezing after the tutorial, memory access violation or something like that, here is the log
(07-26-2017, 07:55 AM)zerocold1981 Wrote: [ -> ] (07-24-2017, 04:56 PM)Butz_san Wrote: [ -> ]In last revisions of RPCS3 the game is working again
Thank you, I saw your video on YouTube. If I am not mistaken
Yes, I made a video on youtube, same user as here in the forum
.
The game was working in a couple of revisions ago without freezing, but after a few revisions later became broken :C
Game is pretty much playable on OpenGL (with Strict Rendering Mode). Don't use Vulkan for now as it causes sever slowdowns and freezes (EDIT: a fix is in the works, PR #3241).
Also set framelimit to 30 fps, otherwise it is too fast (for some reason, auto framelimit is always set at 60, when only the ingame menu and skits are supposed to reach that framerate).
And don't forget to delete the cache every time you want to play the game, or you'll only get a black screen.
Log
Need a log file to move the thread and update compat db, per the submission guidelines.
After the 01/12 changes from Jarves and kd:
The game no longer needs you to delete the cache every time, and skits are now readable.
None of the playable compatibility reports are valid however in preparation for upcoming changes to the compatibility database, this thread has been moved to Playable. Due to other threads for the same media (Disc or PSN) already being in that category.
If you find a specific game ID that performs differently than others for the same game+edition of the same format (PSN or Disc) even when tested with the same build and settings then please discuss it in the relevant thread(s) and PM a moderator so we can look into it.
Tested with: RPCS3 v0.0.4-6226-17bfb3be Alpha
Moving to Ingame due to several issues related to crashing and graphical issues.
RPCS3 v0.0.5-6579-a35bcb131 Alpha | HEAD
Intel® Core™ i7-8700K CPU @ 3.70GHz | 12 Threads | 31.94 GiB RAM | AVX+ | TSX
Game only loads with Strict Rendering Mode Enabled, without it the graphics broken and NPC invisible
With Strict Rendering Mode Enabled game loads and works with these 2 bugs: half of the menu background is black, the Cell Shading effect that supposed to be around objects is "running" (scrolling) on backs of NPC models, always moves and changes.
After the first fight, during the Fight-summary menu, sound dissapeared and after pressing Circle button to exit the menu game crashed iwth following error:
F {SPU[0x2000006] Thread (atrac3plusCellSpursKernel0)} MEM: Access violation reading location 0x0