08-25-2019, 03:37 PM -
Hello, thanks for the reply, i will test the psn one them when i can get it, i just test today the arcade mode on latest build and it get stuck again on before the last boss battle, i will leave the image of the after combat with ky and them the one with the screen freeze after it. the settings are all default except Opengl instead of Vulkan because vulkan on battle goes slow for me, no sure why but that bug was long ago, same as the final boss crash. about the fullscreen bug on opengl, i think it is global, i try others ps3 games and have same issue thats why i post it on support, i dont remenber when the fullscreen opengl black screen issue start, but i can tell you that on version 0.0.6-8340 no have it.
Yes the system i have is a low end pc but it get a lot of titles on fullspeed, some games that no get fullspeed are ones like dead or alive 5 that goes near fullspeed, soul calibour 5 or ninja gaiden yaiba that goes really slow but i see that this one goes slow even on a powerfull pc. I hope that this info help you about the issue.
Screen after vs ky combat:
Last screen before freeze:
Edit: I get the lastest Guilty Gear Revelator with the dlcs on pkg format NPUB31806, and i have the same issue, on arcade episode with sol it get stuck on before final boss, here is whats the error said on the log:
F {PPU[0x1000000] Thread (main_thread) [0x008adffc]} MEM: Access violation reading location 0x3ea4a564
I hope that this can help.
Yes the system i have is a low end pc but it get a lot of titles on fullspeed, some games that no get fullspeed are ones like dead or alive 5 that goes near fullspeed, soul calibour 5 or ninja gaiden yaiba that goes really slow but i see that this one goes slow even on a powerfull pc. I hope that this info help you about the issue.
Screen after vs ky combat:
Last screen before freeze:
Edit: I get the lastest Guilty Gear Revelator with the dlcs on pkg format NPUB31806, and i have the same issue, on arcade episode with sol it get stuck on before final boss, here is whats the error said on the log:
F {PPU[0x1000000] Thread (main_thread) [0x008adffc]} MEM: Access violation reading location 0x3ea4a564
I hope that this can help.
This post was last modified: 08-26-2019, 03:08 PM by pidgey.