Turbo Sliders 2.0.0 Beta
Moderator: Forum Moderators
I also have problem with high cpu usage when directX is off but no problem at all with FPS.
1024 x 768, full screen, directX off, no eye candy - 47 FPS @ 95-100%
Same setup but directX on - 50-52 FPS @ 10-15%
Computer specs:
1024 x 768
Intel Celeron CPU 2.4 GHz
ASUS A9250 Series - 256 MB
512 MB RAM
Windows XP Pro SP2
DirectX 9.0c (4.09.0000.0904)
Main window properties:
1024 x 768 bpp: 32 Bpp: 4 pitch: 4096 size: 3072 kB (3145728)
RGBA masks: ff0000,ff00,ff,0 shifts: 16,8,0,0 losses: 0,0,0,8
colorkey: 0 alpha: 255
SWSURFACE: 0 HWSURFACE: 0 ASYNCBLIT: 0 ANYFORMAT: 0
HWPALETTE: 1 DOUBLEBUF: 0 FULLSCREEN: 1 OPENGL: 0
OPENGLBLIT: 0 RESIZABLE: 0 HWACCEL: 0 SRCCOLORKEY: 0
RLEACCEL: 0 SRCALPHA: 0 PREALLOC: 0
1024 x 768, full screen, directX off, no eye candy - 47 FPS @ 95-100%
Same setup but directX on - 50-52 FPS @ 10-15%
Computer specs:
1024 x 768
Intel Celeron CPU 2.4 GHz
ASUS A9250 Series - 256 MB
512 MB RAM
Windows XP Pro SP2
DirectX 9.0c (4.09.0000.0904)
Main window properties:
1024 x 768 bpp: 32 Bpp: 4 pitch: 4096 size: 3072 kB (3145728)
RGBA masks: ff0000,ff00,ff,0 shifts: 16,8,0,0 losses: 0,0,0,8
colorkey: 0 alpha: 255
SWSURFACE: 0 HWSURFACE: 0 ASYNCBLIT: 0 ANYFORMAT: 0
HWPALETTE: 1 DOUBLEBUF: 0 FULLSCREEN: 1 OPENGL: 0
OPENGLBLIT: 0 RESIZABLE: 0 HWACCEL: 0 SRCCOLORKEY: 0
RLEACCEL: 0 SRCALPHA: 0 PREALLOC: 0
Could you guys who have problems with windib show some results with the old default screen mode, 640x480. What is the load with that?
100% load doesn't mean it's not graphics is are taking time. If you press F10 during a game, you can see time statistics of the last frame. For everything to be smooth, total time should always be less than 20 ms.
About Jarno's odd results with DirectX in windowed mode: windowed mode has always used software surfaces instead of hardware. So DirectX in window mode is performance wise pretty much like windib I guess.
But anyway, my first priority is now to find some settings that should work with as many people as possible. Maybe it could help just to put the screen mode to 640x480...
A long term goal would be to either wait for next major SDL update (1.3 is rumoured to have better system but it has been developed for years and there is no promise it will ever get ready) or make the game use some better graphics interface. One other thing I hate about current SDL is that there is no way to prevent tearing since you can't sync graphics updates to screen refreshing. Also you don't know what the screen refresh rate (or change) is which causes some extra jumpiness when the game FPS is 50 and screen FPS for example 60.
100% load doesn't mean it's not graphics is are taking time. If you press F10 during a game, you can see time statistics of the last frame. For everything to be smooth, total time should always be less than 20 ms.
About Jarno's odd results with DirectX in windowed mode: windowed mode has always used software surfaces instead of hardware. So DirectX in window mode is performance wise pretty much like windib I guess.
But anyway, my first priority is now to find some settings that should work with as many people as possible. Maybe it could help just to put the screen mode to 640x480...
A long term goal would be to either wait for next major SDL update (1.3 is rumoured to have better system but it has been developed for years and there is no promise it will ever get ready) or make the game use some better graphics interface. One other thing I hate about current SDL is that there is no way to prevent tearing since you can't sync graphics updates to screen refreshing. Also you don't know what the screen refresh rate (or change) is which causes some extra jumpiness when the game FPS is 50 and screen FPS for example 60.
-
[FTR] Burnout
- Community User Level: 2

- Posts: 148
- Joined: Mon Nov 26, 2007 11:24 pm
Game runs well however I found a couple bugs:
1) I experience slowdowns in menu and in-game at resolutions 1024 x 768 and up. No problems so far 800x600 and below.
2) My game freezes at the shutdown screen while trying to quit and go back to the desktop. I have to ctrl+alt+delete to leave the game before hitting quit. However, it takes a long time to terminate since the shutdown maxes out my cpu time IF I try to ctrl-alt-delete from the shutdown screen (99-100%).
Overall gameplay wise, it works well!
1) I experience slowdowns in menu and in-game at resolutions 1024 x 768 and up. No problems so far 800x600 and below.
2) My game freezes at the shutdown screen while trying to quit and go back to the desktop. I have to ctrl+alt+delete to leave the game before hitting quit. However, it takes a long time to terminate since the shutdown maxes out my cpu time IF I try to ctrl-alt-delete from the shutdown screen (99-100%).
Overall gameplay wise, it works well!
How many tracks do you have? Do you have "GenerateHTMLOnExit" enabled? I forgot that enabled, and it took 10 minutes just to show Task Manager, then other 10 minutes to click on the kill process button.[FTR] Burnout wrote: 2) My game freezes at the shutdown screen while trying to quit and go back to the desktop. I have to ctrl+alt+delete to leave the game before hitting quit. However, it takes a long time to terminate since the shutdown maxes out my cpu time IF I try to ctrl-alt-delete from the shutdown screen (99-100%).
I used to have those menu slowdowns in 1.0.8 too, not sure what causes them. They are annoying though, especially when some spectator tries to steal your Punaball spot.[FTR] Burnout wrote:1) I experience slowdowns in menu and in-game at resolutions 1024 x 768 and up. No problems so far 800x600 and below.
The 2nd "bug" is probably caused by what dede pointed out, try disabling HTML stats generation on exit.
-
[FTR] Burnout
- Community User Level: 2

- Posts: 148
- Joined: Mon Nov 26, 2007 11:24 pm
Yes the generateHTMLonexit is enabled. I did transfer over some oval tracks I've made and others I've downloaded. I haven't seen any issues with those yet, however when others download cars, it shows an easyslider when I have all the pattern files and car files transfered. It'll keep redownloading for them.
-
[FTR] Burnout
- Community User Level: 2

- Posts: 148
- Joined: Mon Nov 26, 2007 11:24 pm
4 players Banaring:Ande wrote:Could you guys who have problems with windib show some results with the old default screen mode, 640x480. What is the load with that?
100% load doesn't mean it's not graphics is are taking time. If you press F10 during a game, you can see time statistics of the last frame. For everything to be smooth, total time should always be less than 20 ms.
[...]
Code: Select all
1280x1024 640x480
2.0 SDL 1.2.9.0 20% 10%
2.0 DirectX 9.0c 25% 10%
2.0 SDL 1.2.13.0 100% 10fps (89-90ms) 100% 47fps (18-20ms)
TS 2.0.0 SDL 1.2.13.0
Game values with different settings(20players mode):
Full screen 640x480, directx off, alpha-blending on, eye candy full = 50FPS @ 35% -> ugly but works well
(windowed mode was almost the same)
Full screen 800x600, directx off, alpha-blending on, eye candy full = 50FPS @ 50-60%
Full screen 1024x768, directx off, alpha-blending on, eye candy full = 50FPS @ 80-90% -> not so smooth anymore
With directx it was 5-25% all the time
TS 1.0.8 SDL 1.2.9.0
Full screen 640x480, alpha-blending on, eye candy full = 50FPS @ 60-95%
Full screen 640x480, alpha-blending off, eye candy full = 50FPS @ 10-30%
Full screen 800x600, alpha-blending on, eye candy full = 50FPS @ 50-95%
Full screen 800x600, alpha-blending off, eye candy full = 50FPS @ 15-35%
Full screen 1024x768, alpha-blending on, eye candy full = 50FPS @ 60-95%
Full screen 1024x768, alpha-blending off, eye candy full = 50FPS @ 20-35%
Game values with different settings(20players mode):
Full screen 640x480, directx off, alpha-blending on, eye candy full = 50FPS @ 35% -> ugly but works well
Full screen 800x600, directx off, alpha-blending on, eye candy full = 50FPS @ 50-60%
Full screen 1024x768, directx off, alpha-blending on, eye candy full = 50FPS @ 80-90% -> not so smooth anymore
With directx it was 5-25% all the time
TS 1.0.8 SDL 1.2.9.0
Full screen 640x480, alpha-blending on, eye candy full = 50FPS @ 60-95%
Full screen 640x480, alpha-blending off, eye candy full = 50FPS @ 10-30%
Full screen 800x600, alpha-blending on, eye candy full = 50FPS @ 50-95%
Full screen 800x600, alpha-blending off, eye candy full = 50FPS @ 15-35%
Full screen 1024x768, alpha-blending on, eye candy full = 50FPS @ 60-95%
Full screen 1024x768, alpha-blending off, eye candy full = 50FPS @ 20-35%
Spinnering on limits...
TS 2.0.0 SDL 1.2.13.0
640 x 480 full screen, directX off, eye-candy off: FPS 50-52 (19-21ms) @ 31-40% -> unsmooth
640 x 480 full screen, directX on, eye-candy off: FPS 50-52 (19-21ms) @ 0-10% -> smoother than previous but still not too good
TS 1.0.8(/2.00) SDL 1.2.9.0
640 x 480 full screen, eye-candy off: FPS 50-52 (19-21ms) @ 0-10% (my general setup actually) -> no problems at all
Same values for everything, but in 1.08 car is still moving smoother while in 2.00 either car or the rest of the screen has some what a shaky moves. If I replace the new SDL with the old one, everything is working fine.
640 x 480 full screen, directX off, eye-candy off: FPS 50-52 (19-21ms) @ 31-40% -> unsmooth
640 x 480 full screen, directX on, eye-candy off: FPS 50-52 (19-21ms) @ 0-10% -> smoother than previous but still not too good
TS 1.0.8(/2.00) SDL 1.2.9.0
640 x 480 full screen, eye-candy off: FPS 50-52 (19-21ms) @ 0-10% (my general setup actually) -> no problems at all
Same values for everything, but in 1.08 car is still moving smoother while in 2.00 either car or the rest of the screen has some what a shaky moves. If I replace the new SDL with the old one, everything is working fine.
I have "little" problems with TS 2.0b rc2
Im using windows vista premium, and i downloaded ts.exe, installed this to different folder and checked that "open game after installing" box. Ok, then turbo sliders starts like TS 1.0.8, but when i close this version and try to open game again by clicking sliders.exe, it wont open anymore. So what's the problem?
Im using windows vista premium, and i downloaded ts.exe, installed this to different folder and checked that "open game after installing" box. Ok, then turbo sliders starts like TS 1.0.8, but when i close this version and try to open game again by clicking sliders.exe, it wont open anymore. So what's the problem?
I'm thinking it was not Vista's fault (if that's what you may think) as TS is running better for me on Vista after the update.Sic wrote:I have "little" problems with TS 2.0b rc2
Im using windows vista premium, and i downloaded ts.exe, installed this to different folder and checked that "open game after installing" box. Ok, then turbo sliders starts like TS 1.0.8, but when i close this version and try to open game again by clicking sliders.exe, it wont open anymore. So what's the problem?
Back up your 108 stuff, and install 200 over it, and it should work. Working for me thus far...

Which sliders.exe do you mean? "Turbo Sliders" link on the desktop or start menu or do you open TS 2.0 folder in explorer and click sliders.exe there? So what exactly happens? Nothing? No error messages? What does output.txt contain?Sic wrote: Im using windows vista premium, and i downloaded ts.exe, installed this to different folder and checked that "open game after installing" box. Ok, then turbo sliders starts like TS 1.0.8, but when i close this version and try to open game again by clicking sliders.exe, it wont open anymore. So what's the problem?
-
Rendy Andrian
- Community User Level: 2

- Posts: 230
- Joined: Sun Nov 25, 2007 4:10 am
- Contact:
This didnt help meMouse wrote:I'm thinking it was not Vista's fault (if that's what you may think) as TS is running better for me on Vista after the update.Sic wrote:I have "little" problems with TS 2.0b rc2
Im using windows vista premium, and i downloaded ts.exe, installed this to different folder and checked that "open game after installing" box. Ok, then turbo sliders starts like TS 1.0.8, but when i close this version and try to open game again by clicking sliders.exe, it wont open anymore. So what's the problem?
Back up your 108 stuff, and install 200 over it, and it should work. Working for me thus far...
i tried to open sliders from desktop and from jollygood/ts and it wont start game, older version works by both ways.Mouse wrote: Which sliders.exe do you mean? "Turbo Sliders" link on the desktop or start menu or do you open TS 2.0 folder in explorer and click sliders.exe there? So what exactly happens? Nothing? No error messages? What does output.txt contain?
Could you tell me what output.txt in your game folder contains? Is there anything that might explain what happens? You don't get any error messages? If you know how to use command line parameters, you could try running the game in windowed mode (-f 0) or without sound (-sound 0) to see if that helps to see if the problem is related to graphics or sound.Sic wrote: i tried to open sliders from desktop and from jollygood/ts and it wont start game, older version works by both ways.
1.0.8 screenie
2.0.0 screenie
I admit, the difference is not _that_ big (it was much bigger with another image I tested
), but still noticeable.
2.0.0 screenie
I admit, the difference is not _that_ big (it was much bigger with another image I tested
I dont get any error messages, and here's what i have in output.txt:Ande wrote:Could you tell me what output.txt in your game folder contains? Is there anything that might explain what happens? You don't get any error messages? If you know how to use command line parameters, you could try running the game in windowed mode (-f 0) or without sound (-sound 0) to see if that helps to see if the problem is related to graphics or sound.Sic wrote: i tried to open sliders from desktop and from jollygood/ts and it wont start game, older version works by both ways.
Game version: Turbo Sliders 2.0.0w (Windows) Built: Sep 7 2008 16:35:34
Audio Devices found:
- Generic Software on Kaiuttimet (Realtek High Definition Audio)
- Generic Software on Realtek Digital Output (Realtek High Definition Audio)
Default: Generic Software
hw: 0 blit_hw: 0 blit_hw_CC: 0 blit_hw_A: 0
blit_sw: D, blit_sw_CC: 0, blit_sw_A: 0, video_mem: 0
Current video mode: 1680x1050
Available modes:
1680 x 1050 (wide)
1600 x 1200
1600 x 1000 (wide)
1440 x 900 (wide)
1360 x 1024
1360 x 768 (wide)
1280 x 1024
1280 x 960
1280 x 800 (wide)
1280 x 768 (wide)
1280 x 720 (wide)
1152 x 864
1152 x 720 (wide)
1024 x 768
848 x 480 (wide)
800 x 600
720 x 480
640 x 480
Main window properties:
1680 x 1050 bpp: 32 Bpp: 4 pitch: 6720 size: 6890 kB (7056000)
RGBA masks: ff0000,ff00,ff,0 shifts: 16,8,0,0 losses: 0,0,0,8
colorkey: 0 alpha: 255
SWSURFACE: 0 HWSURFACE: 0 ASYNCBLIT: 0 ANYFORMAT: 0
HWPALETTE: 1 DOUBLEBUF: 0 FULLSCREEN: 1 OPENGL: 0
OPENGLBLIT: 0 RESIZABLE: 0 HWACCEL: 0 SRCCOLORKEY: 0
RLEACCEL: 0 SRCALPHA: 0 PREALLOC: 0
Audio information:
Audio context information:
Vendor: Creative Labs Inc.
Version: 1.1
Renderer: Software
Extensions: EAX EAX2.0 EAX3.0 EAX4.0 EAX5.0 EAX3.0EMULATED EAX4.0EMULATED AL_EXT_OFFSET AL_EXT_LINEAR_DISTANCE AL_EXT_EXPONENT_DISTANCE
Audio context created
Localized string test: Stringtesti
String test 2 (personal best): Uusi henkilökohtainen ennätys
Surface store stats: 0 reloads (0 surfaces), 0 invalidations, 0 failed reloads, 0 copies, 0 updates
Exiting.
g surfaceLocks: 0 - 0
alSamplesLoaded: 37 alSamplesFreed: 37
alGenBufs: 37 alDeleteBufs: 37
I mailed you about how to get more debug information (by using -d 3 command line option). But I can see that you have at least changed resolution to 1680 x 1050, so maybe that has caused the problem for some reason. If you delete sliders.ini in Turbo Sliders directory, you can probably run the game again with default settings.Sic wrote:
I dont get any error messages, and here's what i have in output.txt:
Main window properties:
1680 x 1050 bpp: 32 Bpp: 4 pitch: 6720 size: 6890 kB (7056000)
invalid protocol
Hello-
Excited about 2.0!!! I have no clue what I'm doing though so here's where I get stuck...
When I open the Master Server list.....It reads "Invalid Protocol" and something about "server being newer or older."
Any help on this would be much appreciated.
Cant wait to play!
Cheers

Excited about 2.0!!! I have no clue what I'm doing though so here's where I get stuck...
When I open the Master Server list.....It reads "Invalid Protocol" and something about "server being newer or older."
Any help on this would be much appreciated.
Cant wait to play!
Cheers
A new version has come:
(Link removed since there already is a newer version)
This should fix rest of the movement bugs and some other smaller issues. Unfortunately, old track records were invalidated again. I hope this was the last time this had to be done.
Players playing the previous versions (rc1 and rc2) and the new version cannot join each other's games so anyone still having rc1 or rc2, please upgrade before playing.
I believe that future versions will be compatible with rc3 (unless some really bad bugs are found).
There are still graphics and FPS related compatibility issues with some machines but most people should be able to find decent settings by adjusting video settings. I am investigating how to make the game work smoothly for everyone with default settings.
(Link removed since there already is a newer version)
This should fix rest of the movement bugs and some other smaller issues. Unfortunately, old track records were invalidated again. I hope this was the last time this had to be done.
Players playing the previous versions (rc1 and rc2) and the new version cannot join each other's games so anyone still having rc1 or rc2, please upgrade before playing.
I believe that future versions will be compatible with rc3 (unless some really bad bugs are found).
There are still graphics and FPS related compatibility issues with some machines but most people should be able to find decent settings by adjusting video settings. I am investigating how to make the game work smoothly for everyone with default settings.
Last edited by Ande on Tue Sep 30, 2008 3:37 pm, edited 1 time in total.


