[Endeavour OS] Proton: No compat data path? Error

[Ruukha]

Hi, I've been trying to install csp in my EndeavourOS fresh installation, but it doesn't seem to be working. At first i just had to install Steam in order to get the 32-bit libraries and proton, but now, when running the installer, this is the outcome:

[ruukha@endeavouros csp-linux]$ ./csp-installer.sh 4
Downloading GE-Proton 9-20...
GE-Proton9-20.tar.gz                  100%[=======================================================================>] 428,69M  34,2MB/s    in 19s     
Extracting GE-Proton 9-20...
 428MiB 0:00:04 [ 104MiB/s] [======================================================================================================>] 100%            
Removing GE-Proton 9-20.tar.gz...
Downloading steamrt...
steam-container-runtime.tar.gz        100%[=======================================================================>]   3,06M  9,02MB/s    in 0,3s    
3,06MiB 0:00:00 [33,9MiB/s] [======================================================================================================>] 100%            
Downloading CSP_403w_setup.exe...
CSP_403w_setup.exe                    100%[=======================================================================>] 442,43M  15,0MB/s    in 30s     
Installing CSP...
Setting Windows version to win81...
Proton: Upgrading prefix from None to GE-Proton9-20 (/home/ruukha/.local/share/csp-linux/csp-pfx/)
fsync: up and running.
Starting installer...
Go through the process as you usually would then press enter (on terminal) to finish

After looking into it, it seems that the problem is in the line: "GE-Proton9-20/proton" run "$CSP_SETUP". If i try to run that command by itself, this is the outcome:

[ruukha@endeavouros csp-linux]$ GE-Proton9-20/proton run /home/ruukha/Downloads/CSP_403w_setup.exe
Proton: No compat data path?

Any ideas on what could've gone wrong?

[minsiam]

Hey, that’s not actually the issue here.
Since you ran the command directly, Proton doesn’t know the correct compat data path or some of the required environment variables. The script takes care of setting those, which is why it works when you run it through the script instead.

From the output you posted, it looks like Proton did start correctly and a new window should have opened. Can you double-check whether a Clip Studio Paint window shows up at all (even for a moment)?

Also, which desktop environment or window manager are you using (KDE, GNOME, Hyprland, etc.), and is your session X11 or Wayland?

[Ruukha]

Thank you for your reply! When i run the command, nothing happens, even if i wait for a bit, and if i press enter nothing happens either. After looking at the script, i noticed that if i put the line that prints "Go through the process as you usually would then press enter (on terminal) to finish" AFTER the line that calls proton, it doesn't print, which means that it gets stuck there, right? That's why i tried to call on proton by itself
My window manager is KDE