Turbo Sliders 2.0.0 for Linux
Moderator: Forum Moderators
Turbo Sliders 2.0.0 for Linux
Here is the Turbo Sliders 2.0.0 Linux version:
http://www.turbosliders.com/download.php?type=lnx
Only binaries are included as usual. Unfortunately, this probably causes problems for some. The binaries were compiled with the latest Ubuntu. There are two versions of the binaries, one that uses the dynamic link libraries found in the installation directory and one that tries to use the ones in system directories.
For some reason, OpenGL seems to be very laggy on my machine even though FPS is perfect. It just seems that the window system doesn't want to update the screen fast enough. Let me know how it works on your machine or if you can find a solution for that problem.
UPDATE:
I compiled my own versions for all the libraries that are included in the installation packet. GLIBC_2.4 is not required any more when using sliders.linux.
UPDATE:
Rc6 fixes track loading problems. Upgrading is recommended.
UPDATE:
Rc6 will be the final 2.0.0 version.
http://www.turbosliders.com/download.php?type=lnx
Only binaries are included as usual. Unfortunately, this probably causes problems for some. The binaries were compiled with the latest Ubuntu. There are two versions of the binaries, one that uses the dynamic link libraries found in the installation directory and one that tries to use the ones in system directories.
For some reason, OpenGL seems to be very laggy on my machine even though FPS is perfect. It just seems that the window system doesn't want to update the screen fast enough. Let me know how it works on your machine or if you can find a solution for that problem.
UPDATE:
I compiled my own versions for all the libraries that are included in the installation packet. GLIBC_2.4 is not required any more when using sliders.linux.
UPDATE:
Rc6 fixes track loading problems. Upgrading is recommended.
UPDATE:
Rc6 will be the final 2.0.0 version.
Last edited by Ande on Wed Oct 22, 2008 9:39 pm, edited 4 times in total.
Both binaries run on my Arch Linux laptop. I had no problems with video on a quick test, OpenGL or SDL but audio was scrambled. It wasn't that way all the time, there were seconds here and there when it sounded completely normal. There were more of these moments when I ran the shared libraries binary but it still happened. I don't have this problem on 1.0.8.
Regarding the GLIBC_2.4 problem, presuming the machine is running Debian etch, a quick hack -less solution would be to wait for lenny to be released and upgrade. Don't know about the security, they might already support it.
Regarding the GLIBC_2.4 problem, presuming the machine is running Debian etch, a quick hack -less solution would be to wait for lenny to be released and upgrade. Don't know about the security, they might already support it.
Great! Both binaries run fine on my Gentoo desktop althought I did some symbolic linking with the libraries for the rc3-version. OpenGL gives me fps about 62 and SDL shows 111. With quick test I didn't notice any lagginess. Don't know about the audio, because I haven't used it for ages.
About the Glibc, couldn't you just compile it from the source and install the library to your homedir with using the prefix-option in the configure-script.

About the Glibc, couldn't you just compile it from the source and install the library to your homedir with using the prefix-option in the configure-script.
You're using quick and Debian in the same sentence. You must be kiddingSharp wrote:a quick hack -less solution would be to wait for lenny to be released and upgrade
oldschool slider <3 | Hengari @ Quakenet/IRCnet
sliderpoint
sliderpoint
I did that - compiled every library myself - and updated the Linux version. Now I can run it at least on the US server machine again. I upgraded record server to 2.0 and started two 2.0 servers.
With 1.0, the only executable that was working in the US server was the statically linked one. With this new packet, I managed to run the dynamically linked sliders.linux. Currently, I don't plan to include the statically linked version any more since I expect this new executable with manually compiled libraries to work at least as well as the old static version. Let me know if I am wrong.
With 1.0, the only executable that was working in the US server was the statically linked one. With this new packet, I managed to run the dynamically linked sliders.linux. Currently, I don't plan to include the statically linked version any more since I expect this new executable with manually compiled libraries to work at least as well as the old static version. Let me know if I am wrong.
Did see a repeating error message "Unknown macro" in log.txt when loading a track.
Probably way to late and too much to ask for another feature, but for future reference here it goes...
1. A command where you could send a private message Server -> Client and Client -> Server. /whisper <destination nick or IP> <message>
You could then send directed messages. A player could be asking for coming cups and the server would respond.
2. Some way for admins to get a message to log.txt without going through main chat. /note <message>
ex. /note Beginning of F1 cup #23
This will make it easier for admins to find certain parts in a big log.txt-file.
Edit: Forgot to mention that I have TS 2.0.0 rc6, Linux.
I suspect it will go away when a macro called Track_sandycur are present but I shouldn't get an error for this.Message: Autoserver cup pause before next race is 30 seconds.
Message: Unknown macro Track_sandycur.
Message: Track 1/10 will be Sandycur (by Ande).
Probably way to late and too much to ask for another feature, but for future reference here it goes...
1. A command where you could send a private message Server -> Client and Client -> Server. /whisper <destination nick or IP> <message>
You could then send directed messages. A player could be asking for coming cups and the server would respond.
2. Some way for admins to get a message to log.txt without going through main chat. /note <message>
ex. /note Beginning of F1 cup #23
This will make it easier for admins to find certain parts in a big log.txt-file.
Edit: Forgot to mention that I have TS 2.0.0 rc6, Linux.
Yes, those are good feature requests, I won't implement it them to 2.0.0 but maybe in the future...
That Unknown macro message is rather ugly, too. Since it is only in log.txt when running an automatic server, maybe we have to live with it for now, I won't make a new build for that unless something bigger is found. As you probably guessed, by defining those macros you can make track specific macros. For admins, there are also other powerful commands like /source and /cmd. Especially /cmd could be used to do almost anything, including security holes by badly written scripts
. More info about how to enable and use it in README-autoserver.txt.
That Unknown macro message is rather ugly, too. Since it is only in log.txt when running an automatic server, maybe we have to live with it for now, I won't make a new build for that unless something bigger is found. As you probably guessed, by defining those macros you can make track specific macros. For admins, there are also other powerful commands like /source and /cmd. Especially /cmd could be used to do almost anything, including security holes by badly written scripts
That's because there is no macro configured for that track. It has been there in 1.0.8 too, I guess. And I don't think it's a real error, it's more like a notice.The Dude wrote:Did see a repeating error message "Unknown macro" in log.txt when loading a track.
That could be quite nice (also having the possibility to write messages to own chat only, /ownmsg "This is a message visible only to me").The Dude wrote:1. A command where you could send a private message Server -> Client and Client -> Server. /whisper <destination nick or IP> <message>
You could then send directed messages. A player could be asking for coming cups and the server would respond.
It would be also nice to enable ONLY custom script (now to run a custom script, we need to enable all scripts and raceend.cmd is run even if it's not there), and the possibility to run own custom scripts even when being in client mode.


