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

I can't run any game - RSX: Linkage failed: Compute shader(s) failed to link #12813

Closed
spiraluc opened this issue Oct 15, 2022 · 8 comments · Fixed by #12820
Closed

I can't run any game - RSX: Linkage failed: Compute shader(s) failed to link #12813

spiraluc opened this issue Oct 15, 2022 · 8 comments · Fixed by #12820
Labels
Driver: AMD OpenGL Proprietary AMD OpenGL driver OS: Windows

Comments

@spiraluc
Copy link

spiraluc commented Oct 15, 2022

Quick summary

When I start any game I get this error (probably related to old AMD graphics HW):

The problems started after Ogl bringup 6 #12454 (rpcs3-v0.0.23-14004-3e923b49_win64)

·F 0:00:15.220862 {RSX [0x0003fe4]} RSX: Linkage failed: Compute shader(s) failed to link.
Compute link error: INVALID_OPERATION.
ERROR: error(# 370) Missing or invalid layout qualifier for image variable

·F 0:00:15.221036 {RSX [0x0003fe4]} RSX: swap_bytes not found.
·F 0:00:15.221061 {RSX [0x0003fe4]} RSX: src_pitch not found.
·F 0:00:15.221082 {RSX [0x0003fe4]} RSX: format not found.
·F 0:00:15.221102 {RSX [0x0003fe4]} RSX: region_offset not found.
·F 0:00:15.221125 {RSX [0x0003fe4]} RSX: region_size not found.

Details

No response

Attach a log file

RPCS3 error.log

Attach capture files for visual issues

No response

System configuration

CPU: Intel Core 2 Duo E7500
GPU: AMD HD 7570 2GB (openGL 4.5 only) (driver 16.2.1)
RAM: 8GB
WIN 10 (21H2)

(meets the minimum HW requirements)

Other details

No response

@kd-11
Copy link
Contributor

kd-11 commented Oct 15, 2022

The provided log does not include the crashed session.

@kd-11
Copy link
Contributor

kd-11 commented Oct 16, 2022

I'm mostly certain that this is failing in the CopyBufferToImage routine which writes to an image without specifying the format. This is because the format specifier is not required for images marked as "writeonly".
To quote the OpenGL specification for ARB_image_load_store:

Any image variable used for image loads or atomic operations must specify
a format layout qualifier; it is an error to pass an image uniform
variable or function parameter declared without a format layout qualifier
to an image load or atomic function.

Uniforms not qualified with "writeonly" must have a format layout qualifier.
Note that an image variable passed to a function for read access cannot be
declared as "writeonly" and hence must have been declared with a format
layout qualifier.

The solution here will be to detect the legacy ATI driver and avoid touching any of the more modern stuff when it is being used.

@spiraluc
Copy link
Author

spiraluc commented Oct 16, 2022

If you need any further information, please let me know how to get it.

I tried logging with debug output enabled.
RPCS3 debug output error.log

@kd-11
Copy link
Contributor

kd-11 commented Oct 16, 2022

Test #12820

@spiraluc
Copy link
Author

Still not functional. Now it shows different errors.

RPCS3 debug output.log

@AniLeo AniLeo added OS: Windows Driver: AMD OpenGL Proprietary AMD OpenGL driver and removed Need Information labels Oct 16, 2022
@kd-11
Copy link
Contributor

kd-11 commented Oct 16, 2022

I made some changes. Try now.

@spiraluc
Copy link
Author

Yes, now it works without problems. Thank you.

@yubokn
Copy link

yubokn commented Jan 27, 2023

hello, i am having the exact same problem with bordering on the exact same specs. please help, what did you do to fix this? i am completely new i am sorry if i am doing something wrong here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Driver: AMD OpenGL Proprietary AMD OpenGL driver OS: Windows
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants