Closed detiam closed 3 months ago
I don't know the setup but you seem to be mixing 32 and 64 libs. steamclient is found in linux64 folder but then you showed a 32 bit libsteam.
If you're doing lib replacement make sure to run the app from its intended script/executable, I have some which only work when launched through some launcher provided along with it. If you are using the steamclient setup use the script provided, or change it to run on your distro if it needs some changes.
Just wanted to rant a little bit, you can ignore this comment. This isn't really your problem or something even related to the emu, it's just a dll/lib at the end of the day. It's how Valve decided to setup their environment, plus how some games modify it to handle their own stuff, coupled with the awful way Linux handles dynamic loading which makes such a simple task a pain to even think about. On Windows you know the load order, you know how and where are things loaded, and you have many tools free and some open source, to explore the currently loaded dlls inside the mem space of a process.
The environment I'm referring to is this https://github.com/otavepto/gbe_fork/blob/574e7a77811830e71eefa674212d21ca160d3569/tools/steamclient_loader/linux/steamclient_loader.sh#L28
The steamclient setup along with this option is the safest bet and always 100% of the time in my tests worked, for 32 and 64 bit apps.
I don't know the setup but you seem to be mixing 32 and 64 libs. steamclient is found in linux64 folder but then you showed a 32 bit libsteam.
If you're doing lib replacement make sure to run the app from its intended script/executable, I have some which only work when launched through some launcher provided along with it. If you are using the steamclient setup use the script provided, or change it to run on your distro if it needs some changes.
Because libsteam.so
only have one 32bit version available in ~/.local/share/Steam/ubuntu12_32/
And I found I had a mistake, the [API loaded yes]
only happen in 32bit game, 64bit game will show [API loaded no]
even when launch from official steam client. Guess the libsteam.so
thing is a very old behavior of steam for native Linux game in 32bit era… So I think we can just ignore it, will close this.
Just wanted to rant a little bit, you can ignore this comment. This isn't really your problem or something even related to the emu, it's just a dll/lib at the end of the day. It's how Valve decided to setup their environment, plus how some games modify it to handle their own stuff, coupled with the awful way Linux handles dynamic loading which makes such a simple task a pain to even think about. On Windows you know the load order, you know how and where are things loaded, and you have many tools free and some open source, to explore the currently loaded dlls inside the mem space of a process.
The environment I'm referring to is this
The steamclient setup along with this option is the safest bet and always 100% of the time in my tests worked, for 32 and 64 bit apps.
@_@
When use emu, the game can't find
libsteam.so
and print[API loaded no]
after steam ID, normally this is[API loaded yes]
.So far, I haven't found any game that not satisfied with it, but this is an Inconsistent behavior.