You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
STAR OCEAN: Integrity and Faithlessness crashes on the following assertion on main:
[Debug] <Critical> liverpool_to_vk.cpp:710 operator(): Assertion Failed! Unknown data_format=40 and num_format=7
A PR was made to fix this assertion (#2813) but after some discussions it seems like this is not correct according to Stephen's research on AMD's open source PAL. With this though the game goes from nothing to ingame, with really broken graphics. Also if that helps, changing the vk format from unsigned to signed (eBc6HUfloatBlock to eBc6HSfloatBlock) breaks the water rendering, so if anything it should be unsigned as it looks the same as real hardware.
That's about all the information I can give, if I can help debug this in any other way please let me know I'd be glad to help.
Checklist (we expect you to perform these steps before opening the issue)
Describe the Bug
STAR OCEAN: Integrity and Faithlessness crashes on the following assertion on main:
[Debug] <Critical> liverpool_to_vk.cpp:710 operator(): Assertion Failed! Unknown data_format=40 and num_format=7
A PR was made to fix this assertion (#2813) but after some discussions it seems like this is not correct according to Stephen's research on AMD's open source PAL. With this though the game goes from nothing to ingame, with really broken graphics. Also if that helps, changing the vk format from unsigned to signed (
eBc6HUfloatBlock
toeBc6HSfloatBlock
) breaks the water rendering, so if anything it should be unsigned as it looks the same as real hardware.That's about all the information I can give, if I can help debug this in any other way please let me know I'd be glad to help.
Reproduction Steps
Launch the game and wait for the crash to occur.
Specify OS Version
Windows 11
CPU
Intel Core I9-13900K
GPU
Nvidia RTX 4090
Amount of RAM in GB
32 GB
Amount of VRAM in GB
24 GB
Log File
CUSA03219.log
The text was updated successfully, but these errors were encountered: