search

theNizo / linux_rocksmith

Guides to get Rocksmith 2014 running on Linux
https://thenizo.github.io/linux_rocksmith/
GNU General Public License v3.0
110 stars 10 forks source link

I get stuck following the guide at "WATCH OUT FOR VARIABLES" step #58

Closed zoobporsor closed 3 weeks ago

zoobporsor commented 1 month ago

I'm following the guide, https://github.com/theNizo/linux_rocksmith/blob/main/guides/setup/arch-pipewire.md

I get stuck at the step 

"To make Proton use wineasio, we need to copy these files into the appropriate locations:
# !!! WATCH OUT FOR VARIABLES !!!
cp /usr/lib32/wine/i386-unix/wineasio32.dll.so "$PROTON/lib/wine/i386-unix/wineasio32.dll.so"
cp /usr/lib/wine/x86_64-unix/wineasio64.dll.so "$PROTON/lib64/wine/x86_64-unix/wineasio64.dll.so"
cp /usr/lib32/wine/i386-windows/wineasio32.dll "$PROTON/lib/wine/i386-windows/wineasio32.dll"
cp /usr/lib/wine/x86_64-windows/wineasio64.dll "$PROTON/lib64/wine/x86_64-windows/wineasio64.dll""
The commands dont work

[zeebpc@arch wineasio-1.2.0]$ cp /usr/lib32/wine/i386-unix/wineasio32.dll.so "$PROTON/lib/wine/i386-unix/wineasio32.dll.so"
cp: cannot create regular file '/lib/wine/i386-unix/wineasio32.dll.so': No such file or directory

What does "WATCH OUT FOR VARIABLES" mean? What should I do?

zoobporsor commented 1 month ago

I managed to manually use a GUI to track down the files and copy them over, but I dont know how I was supposd to get the commands to work Now im stuck at another step

"To register wineasio (so that it can be used in the prefix), run the wineasio-register script that comes in the wineasio zip and set the WINEPREFIX to Rocksmiths."

env WINEPREFIX=$STEAMLIBRARY/steamapps/compatdata/221680/pfx ./wineasio-register If I type it in terminal, I get an error

[zeebpc@arch ~]$ env WINEPREFIX=$STEAMLIBRARY/steamapps/compatdata/221680/pfx /home/zeebpc/Downloads/wineasio/wineasio-1.2.0/wineasio-register 
wine: chdir to /steamapps/compatdata/221680/pfx : No such file or directory

sorry for basic noob mistakes I am trying to learn

Is it possible that $ Variables are broken on my system somehow? do I need to do something special to make $STEAMLIBRARY and $PROTON actually point towards my stuff and work? For instance, if i type printenv STEAMLIBRARY or printenv PROTON they return no results. also echo $PROTON echo $STEAMLIBRARY no results

Also, earlier in the guide to test if wineasio works, the command also does not work for me.

[zeebpc@arch ~]$ find /usr/lib32/ -name "wineasio*" find /usr/lib/ -name "wineasio*"
find: paths must precede expression: `find'

????

EDIT: Ok i got the command the work by just entirely ignoring all the $ shenanigans and just manually typing in my steam library like so

env WINEPREFIX=/home/zeebpc/.local/share/Steam/steamapps/compatdata/221680/pfx ./wineasio-register

Edit again: Managed to get it all working, but I usually have to start the game multiple times for it to start working I launch it using the startup script non-steam game option 1st try usually gets a black/grey screen (frozen) i have to alt tab and quit , try again, then it usually works Why does it crash on the first attempt most times?

theNizo commented 1 month ago

What does "WATCH OUT FOR VARIABLES" mean?

It's a reminder that you should set the environment variables as mentioned in the prerequisites. Otherwise, the paths won't be recognized correctly.

Also see #52

theNizo commented 1 month ago

Sorry, didn't read till the end.

Also, earlier in the guide to test if wineasio works, the command also does not work for me.

Actually no idea, tbh. You ran find <something> find <somothing>. You need to seperate the commands, either by line breaks or by &&. This needs to be corrected in the guide.

The paragraph below is still valid, just not as relevant now.

The command just searches for the files and reports where they are IF you placed them. It's meant to quickly see if they are in the correct spots. You could also check that manually.

Managed to get it all working, but I usually have to start the game multiple times for it to start working [...]

That's new behavior to me.

I would guess that it freezes in the first few seconds, or rather, even in the first second. Can you please try the following, for further analysis:

zoobporsor commented 1 month ago

thanks for replying so soon

oh geez, I totally missed that part.. https://github.com/thenizo/linux_rocksmith/?tab=readme-ov-file#common-paths

This is because once I opened this guide link, I thought this page had everything I needed! . Maybe preface this page with "Make sure you read Pre-requisites and set paths if necessary!" + add the echo $ checks, to verify in the common paths section

I wonder why my Arch system doesnt have any default paths for $PROTON and $STEAMLIBRARY, it seems like its usually setup automatically

Another person had the same confusion as me https://www.reddit.com/r/rocksmith/comments/18dh9bo/some_issues_i_ran_into_running_rs_with_rs_asio_on/

I will keep testing the crashes, it seems like so far it has run 100% of time thru terminal, and through steam shortcut it crashes frequently on first startup. However I have since restarted steam and I havnt noticed a crash, so maybe its just a fluke.

Anyway, once its setup the experience is awesome! all the "guides" on proton.db are trash, this one is mostly great. I'm so happy to have Rocksmith working on Linux :) and OBS just works with it, too! Its much better than Windows.

I did make one adjustment i edited the rocksmith.ini and changed LatencyBuffer from 4 to 2 for lowest latency possible. Feels good! Thank you

theNizo commented 1 month ago

I wonder why my Arch system doesnt have any default paths for $PROTON and $STEAMLIBRARY, it seems like its usually setup automatically

Those are made up by me. I use them in the guide so that readers can just copy-paste the commands.

Maybe preface this page with

Agreed.

theNizo commented 3 weeks ago

Done.

f0ebd54 e6c4ee5 e785b14 4718ac6

Let me know if I missed something.