Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Regression] GOW3 - rendering error #14083

Closed
JohnLoveJoy opened this issue Jun 23, 2023 · 4 comments · Fixed by #14101
Closed

[Regression] GOW3 - rendering error #14083

JohnLoveJoy opened this issue Jun 23, 2023 · 4 comments · Fixed by #14101

Comments

@JohnLoveJoy
Copy link

Quick summary

After the last modifications in the vk code, GOW3(Demo) started to show rendering errors, overlapping objects and smoke as if there was incorrect transparency.

Details

When standing still without moving the rendering issues go up for an instant.
GOW3_PS
GOW3_BUG

I used the recommended settings from the compatibility guide.

Build with regression

v.0.0.28-15227-Alpha

Attach two log files

RPCS3.log.gz

Attach capture files for visual issues

No response

System configuration

Specs 5500U @ Vega 7 + 12GB ram

Other details

No response

@JohnLoveJoy JohnLoveJoy changed the title [Regression] Enter a title here [Regression] GOW3 - rendering error Jun 23, 2023
@AniLeo
Copy link
Member

AniLeo commented Jun 24, 2023

Incomplete regression report

The build you mention just includes compilation fixes, missing build that regressed it and last good build

@kd-11
Copy link
Contributor

kd-11 commented Jun 24, 2023

It seems vega doesn't support KHR_synchronization2 so we need to restore the workaround path because default vulkan events were really broken on AMD.

@JohnLoveJoy
Copy link
Author

JohnLoveJoy commented Jun 24, 2023

I don't know how efficient GPU-Z is at detecting GPU extensions, but here mentions the one you mentioned:

PSGPUZ0

Anyway, just to clarify, the bug was introduced after this pull: #14065

@kd-11
Copy link
Contributor

kd-11 commented Jun 26, 2023

Test with #14101
If its still broken, attach log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants