![]() Or remove the link again and try something else. If my advice isn't working you could try linking without the "-s". ![]() (If you want to use relative paths instead you would probably need to cd to the exact same directory that the executable is when it is started and then create a relative link from there.) ", not "ln -s steamcmd/linux32/steamclient.so. "ln -s /home//steamcmd/linux32/steamclient.so. ![]() Make sure you use absolute paths for the source file when you are linking. I suspect he failed at creating the right link and made it refer to itself, i.e. PLEASE HELP (steam api error) By DeathAngel99, in General Discussions. The Steam Beta client is a known culprit of the problem. Solution 2: Opt-out of Steam Beta and Restart Steam. The last person I gave this advice to got a different error message though about "Too many levels of symbolic links". This topic is now archived and is closed to further replies. Click OK and restart your computer before re-launching the problematic game via Steam and checking if it will now run without displaying the Unable to initialize Steam API error message. You can't really break something serious short term if you make the library findable in a few more places. Maybe ~/.steam/sdk32/ as target works too, maybe try that too. I know that /usr/lib/ is definitely looked into for libraries, so you might try that. Essentially 7D2D just needs to find the lib, so linking to anywhere it looks for libs should be fine The steamclient.so in your 7d2d directory or the one in steamcmd/linux32/ (if there is one) should be ones you can use AFAIK.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |