Page 1 of 1

Not working on fedora 29

Posted: Tue Jun 25, 2019 12:14 am
by oldeschool
I believe I have everything correct, but plugin doesn't do anything.
Something I noticed when I placed the scs telemetry plugin into the plugin directory, the game warns about using modifications
I don't get that warning with etcars.
I built the scs plugin from source, it works so I have the correct location for plugins...

Re: Not working on fedora 29

Posted: Sat Jul 06, 2019 10:58 am
by jammerxd
Hi there,
Did you make sure you have all of the dependencies that ETCARS requires installed on your system? There may be a library not installed that is required.

I would see if there's a development tool on Linux that can tell you which libraries are required to load the Linux version of etcars. Also there is a build artifact on the gitlab repo under the ci/cd job pipeline section of a development build.

Re: Not working on fedora 29

Posted: Sun Jul 14, 2019 11:17 pm
by oldeschool
jammerxd wrote:
Sat Jul 06, 2019 10:58 am
Hi there,
Did you make sure you have all of the dependencies that ETCARS requires installed on your system? There may be a library not installed that is required.

I would see if there's a development tool on Linux that can tell you which libraries are required to load the Linux version of etcars. Also there is a build artifact on the gitlab repo under the ci/cd job pipeline section of a development build.
All libraries are OS default except for libsteam_api -- I tried using the one from the steam sdk and from the one supplied with ATS

I have had to remove the dot so dot version -- the forum interprets it as a domain and will not post
ldd output
linux-vdso (0x00007ffe83d97000)
libpthread.=> /lib64/libpthread (0x00007f4c1aab7000)
libsteam_api => /home/russ/src/sdk/redistributable_bin/linux64/libsteam_api (0x00007f4c1a84d000)
libstdc++. => /lib64/libstdc++ (0x00007f4c1a6b5000)
libgcc_s => /lib64/libgcc_ (0x00007f4c1a69a000)
libc. => /lib64/libc (0x00007f4c1a4d4000)
/lib64/ld-linux-x86-64 (0x00007f4c1b1db000)
libdl => /lib64/libdl (0x00007f4c1a4ce000)
libm => /lib64/libm (0x00007f4c1a348

Re: Not working on fedora 29

Posted: Tue Jul 16, 2019 2:11 pm
by jammerxd
What path are you installing this into? Have you tried Ubuntu(as that is the distribution I am using for builds)? Also, the libsteam_api is provided by the game and is not needed to be downloaded/copied anywhere. Are you running this in wine? Are you running this without the Steam Proton feature(native Steam OS + Linux)? This could be a distribution compilation issue as I've only tested and built on Ubuntu Linux.

Re: Not working on fedora 29

Posted: Tue Jul 16, 2019 10:00 pm
by oldeschool
Native Linux version of ATS -- I have tried Ubuntu 19.04 as well as Fedora
the plugin is in ~/.steam/steamapps/common/American\ Truck\ Simulator/bin/linux_x64/plugins/

ldd is finding all dependencies

need another 54 characters ti submit so +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Re: Not working on fedora 29

Posted: Wed Jul 17, 2019 5:15 pm
by jammerxd
Did you check game.log.txt and see if it has any clues as to why the plugin isn't being loaded? There could be a version discrepency between one of the libraries installed and the ones I built against. Please see if there's any clues there, that'd be the next place to look for issues.

Re: Not working on fedora 29

Posted: Fri Jul 19, 2019 10:55 pm
by oldeschool
I did not know the game logged -- found this:

undefined symbol: _ZN5boost6system15system_categoryEv
I've installed every boost library available including the development packages.

What version of Ubuntu do you build on?


30 more characters ...............................................................................

Re: Not working on fedora 29

Posted: Thu Jul 25, 2019 10:16 pm
by jammerxd
Hi oldeschool,
It looks like that is a reference to a boost library. I can't remember what I did to resolve that but it is boost related(the boost c++ library). I'll do some checking and see what I can find but again, I'm not sure what the issue was there. I'll double check the version of boost I'm compiling against but I don't have that issue at all.