Didn't notice was demo player. Thanks for pointing that out.
Not being able to use layouts explains why xmas drag lights don't work as expected, and don't close - the script will only progress when a checkpoint triggers are activated on the AU1 layout.
Not much else I can do or recommend, except use the basic drag light system, or maybe fork out for at least a S1 license.
Are you talking about my older drag system with the 'xmas lights' layout rather than my newer and simpler set?
Did you use the AU1 drag layout I bundled with the drag.lpr set? This is required as the code needs the car to enter into various marked zones to trigger the light sequences.
Did the lights come on as per my video?
Did they come on, go through the sequence, but then didn't clear from the screen? If so, did you use the !dragoff command?
My script was written a lot of years ago, and the lapper code has been updated since then, so there may be some issues there, in which case, maybe try Bass-Drivers system.
Did you use the AU1 drag layout I bundled with the drag.lpr set? This is required as the code needs the car to enter into various marked zones to trigger the light sequences.
Did the lights come on as per my video?
Did they come on, go through the sequence, but then didn't clear from the screen? If so, did you use the !dragoff command?
My script was written a lot of years ago, and the lapper code has been updated since then, so there may be some issues there, in which case, maybe try Bass-Drivers system.
Firstly, you don't have to worry about MCI or other packets with lapper.
The code within lapper, which runs in the background, does all the packet work for you.
In the main, you specify a lapper Event (eg Leave Pits) and execute your own code (eg show button/text) and/or run a sub-routine.
I'd suggest downloading my original drag script and the AU1 layout, which are both in the zip file in the 1st post (HERE). At the same time, have read through all the posts, as there's some useful information there.
Along with the files, you can have a look at the video I made, which shows both the layout and what the script actually does.
I'm not sure if you know the difference between Nodes and Zones, but I made a post about it to explain HERE, which helps explain.
As for how to only show lights to only the drivers you want to have a drag race, that's beyond my capabilities.
Probably what I'd do, is just have a Global message advising drivers not involved in the drag race to stay out of the drag area while lights are on. Although if lights are up and running, should be fairly obvious whats going on.
The code within lapper, which runs in the background, does all the packet work for you.
In the main, you specify a lapper Event (eg Leave Pits) and execute your own code (eg show button/text) and/or run a sub-routine.
I'd suggest downloading my original drag script and the AU1 layout, which are both in the zip file in the 1st post (HERE). At the same time, have read through all the posts, as there's some useful information there.
Along with the files, you can have a look at the video I made, which shows both the layout and what the script actually does.
I'm not sure if you know the difference between Nodes and Zones, but I made a post about it to explain HERE, which helps explain.
As for how to only show lights to only the drivers you want to have a drag race, that's beyond my capabilities.
Probably what I'd do, is just have a Global message advising drivers not involved in the drag race to stay out of the drag area while lights are on. Although if lights are up and running, should be fairly obvious whats going on.
The simple drag system I made is for use with LFSLapper ("lapper").
It uses global buttons (openGlobalButton), which means that everyone sees it.
You could change that to private buttons (openPrivButton) so that only the person who enters the !drag command sees the lights.
If you want the lights to only appear in a certain area, you would have to register a node or a zone.
If you want a more developed drag system, you could try Bass-Drivers system (HERE).
I tried to make a drag system before that, but it only partly worked as I couldn't get the penalty part working. Can be found HERE.
It uses global buttons (openGlobalButton), which means that everyone sees it.
You could change that to private buttons (openPrivButton) so that only the person who enters the !drag command sees the lights.
If you want the lights to only appear in a certain area, you would have to register a node or a zone.
If you want a more developed drag system, you could try Bass-Drivers system (HERE).
I tried to make a drag system before that, but it only partly worked as I couldn't get the penalty part working. Can be found HERE.
You don't have to go from Demo user straight to a S3 user - you have the option to take it in 3 stages, with S1, S2 and S3 licenses, with each license being the same amount of money.
I think people in Turkey get a whopping 50% discount on the license fees, so that means each license will cost approx £6 / 335 Turkish Lira.
I holidayed in Turkey few years back, and I spent more than that getting a basic haircut. Maybe it would have been cheaper if I hadn't agreed to the hair in my ears being singed?
If you can't afford 300+ lira for a license, I have to wonder how you managed to afford to buy a laptop or pc to play LFS.
I think people in Turkey get a whopping 50% discount on the license fees, so that means each license will cost approx £6 / 335 Turkish Lira.
I holidayed in Turkey few years back, and I spent more than that getting a basic haircut. Maybe it would have been cheaper if I hadn't agreed to the hair in my ears being singed?
If you can't afford 300+ lira for a license, I have to wonder how you managed to afford to buy a laptop or pc to play LFS.
I also made a couple of grass oval tracks - both on Westhill.
https://www.lfs.net/forum/thread/87757
This one's also on Westhill.
For the UF1 to LX cars, a lap is about 30-40 seconds. Times at bottom of post.
Goodness - layouts are 10 years old
https://www.lfs.net/forum/thread/87757
This one's also on Westhill.
For the UF1 to LX cars, a lap is about 30-40 seconds. Times at bottom of post.
Goodness - layouts are 10 years old
Seems like you can't connect to lapper, so not a problem with my simple script, which basically opens, overwrites and closes a dozen buttons.
Maybe a firewall issue?
You've checked the ERR file. What does the MSS file say?
If no clues there, you could try an earlier version than you have - I'm still running V7.093.
If you still have problems connection, it's not something I can help with.
Maybe a firewall issue?
You've checked the ERR file. What does the MSS file say?
If no clues there, you could try an earlier version than you have - I'm still running V7.093.
If you still have problems connection, it's not something I can help with.
Do you get a connection window open, like this ...
(I've greyed out my IP and Port)
Assuming this shows, if lapper doesn't connect, you should get an error message.
Also, In your lapper directory, look in /bin/default/logs and you will see 2 files - one ends -ERR and other -MSS.
The -ERR file shows if there are any errors, and what these errors are.
The -MSS file will give some connection information.
The information in these files may be helpful.
(I've greyed out my IP and Port)
Assuming this shows, if lapper doesn't connect, you should get an error message.
Also, In your lapper directory, look in /bin/default/logs and you will see 2 files - one ends -ERR and other -MSS.
The -ERR file shows if there are any errors, and what these errors are.
The -MSS file will give some connection information.
The information in these files may be helpful.
OK, following looks a lot, but should be straightforward ...
Download lapper, and save to your '/LFS' folder.
Download from https://www.lfs.net/forum/434-Releases.
I'm still running V7093, but no reason why script won't work with the newer versions.
You can rename this downloaded folder or leave name as is.
Because I use lapper with lots of different layouts, I make a new folder with the name of my new layout, as lapper saves times and drift scores in databases using the track abbreviation. And as I use LA1 a lot, the 2nd layout would overwrite the times/scores of the 1st layout.
In this downloaded folder, in the /bin directory, open 'LFSServers.cfg' file
Change the IP and port numbers on the last line to match your rented LFS IP / port numbers
(e.g. DEF1|gr1|123.456.78.901|59901|./default|default_1.ini|autowork)
In the /bin/default directory, open 'default_1' file.
Change the password to match your multiplayer host password (e.g. $password = "mypass": )
In the same directory, open both the 'admin.txt' and 'superusers.txt' files, and add your LFS username.
Download the 'drag2.txt' file in my post
(https://www.lfs.net/forum/thread/112222-Simple-Drag-Light-System),
and rename to 'drag2.lpr'.
Move this file into the /bin/default/includes folder.
In that folder, open the 'addonused' file, and add the line
include("./drag2.lpr");
All the above files can be opened with your default note app, e.g. Notepad.
To run lapper, click on the 'LFSLapper.exe' file.
If all that works, then when in your server, type "!drag".
If you want to change any of the light colours, you can. For instance "^0•" will show a black light, but if you want it white, you would change the 0 to 7, or 8 if you wanted grey, etc.
Good luck.
Download lapper, and save to your '/LFS' folder.
Download from https://www.lfs.net/forum/434-Releases.
I'm still running V7093, but no reason why script won't work with the newer versions.
You can rename this downloaded folder or leave name as is.
Because I use lapper with lots of different layouts, I make a new folder with the name of my new layout, as lapper saves times and drift scores in databases using the track abbreviation. And as I use LA1 a lot, the 2nd layout would overwrite the times/scores of the 1st layout.
In this downloaded folder, in the /bin directory, open 'LFSServers.cfg' file
Change the IP and port numbers on the last line to match your rented LFS IP / port numbers
(e.g. DEF1|gr1|123.456.78.901|59901|./default|default_1.ini|autowork)
In the /bin/default directory, open 'default_1' file.
Change the password to match your multiplayer host password (e.g. $password = "mypass": )
In the same directory, open both the 'admin.txt' and 'superusers.txt' files, and add your LFS username.
Download the 'drag2.txt' file in my post
(https://www.lfs.net/forum/thread/112222-Simple-Drag-Light-System),
and rename to 'drag2.lpr'.
Move this file into the /bin/default/includes folder.
In that folder, open the 'addonused' file, and add the line
include("./drag2.lpr");
All the above files can be opened with your default note app, e.g. Notepad.
To run lapper, click on the 'LFSLapper.exe' file.
If all that works, then when in your server, type "!drag".
If you want to change any of the light colours, you can. For instance "^0•" will show a black light, but if you want it white, you would change the 0 to 7, or 8 if you wanted grey, etc.
Good luck.
If you're willing to use LFSLapper("lapper"), I've just made an add-on script that show a start light sequence ...
Made a short YouTube video - https://youtu.be/pFmTPuCUVVY
See post in the lapper section (https://www.lfs.net/forum/post/2133251#post2133251) for script.
Made a short YouTube video - https://youtu.be/pFmTPuCUVVY
See post in the lapper section (https://www.lfs.net/forum/post/2133251#post2133251) for script.
Simple Drag Light System
Add-on for a set of lights to start a drag race...
Made a short YouTube video - https://youtu.be/pFmTPuCUVVY
Light sequence start when you type !drag. If you want to cancel part way through the sequence, type !dragoff.
Lights aren't track specific, nor do they need a start location.
You will need to change drag2.txt to drag2.lpr, and add it into your /Includes folder.
Made a short YouTube video - https://youtu.be/pFmTPuCUVVY
Light sequence start when you type !drag. If you want to cancel part way through the sequence, type !dragoff.
Lights aren't track specific, nor do they need a start location.
You will need to change drag2.txt to drag2.lpr, and add it into your /Includes folder.
The most obvious issue is that if you are adding a lapper script, you need to 'Catch' any and all events.
So "Event onMSO.." should be "CatchEvent OnMSO...", and the end should be changed from "EndEvent" to "EndCatchEvent".
Not sure why there's a 'rivi1' sub, when the !brief command sends you to 'rivi2'.
As for the sub info (or lack thereof) within the brackets after the sub name, this is something I always struggle with, and even asked about ...
SUB event Q - https://www.lfs.net/forum/post/1693093#post1693093
SUB event A - https://www.lfs.net/forum/post/1693302#post1693302
The answer helped me a little, but not always, so I go through the following ...
# Possible subs to use:
# Sub sub1()
# Sub sub1($userName)
# Sub sub1($KeyFlags,$userName)
# Sub sub1($KeyFlags,$argv)
# Sub sub1($KeyFlags,$id)
If you're using a command to start things off, why do you need a distance to do first?
Another issue might be the directory and folder you're placing your briefing.lpr file. It should be in the standard \bin\default\includes directory, and should be added into the existing addonsused.lpr file.
Good luck.
So "Event onMSO.." should be "CatchEvent OnMSO...", and the end should be changed from "EndEvent" to "EndCatchEvent".
Not sure why there's a 'rivi1' sub, when the !brief command sends you to 'rivi2'.
As for the sub info (or lack thereof) within the brackets after the sub name, this is something I always struggle with, and even asked about ...
SUB event Q - https://www.lfs.net/forum/post/1693093#post1693093
SUB event A - https://www.lfs.net/forum/post/1693302#post1693302
The answer helped me a little, but not always, so I go through the following ...
# Possible subs to use:
# Sub sub1()
# Sub sub1($userName)
# Sub sub1($KeyFlags,$userName)
# Sub sub1($KeyFlags,$argv)
# Sub sub1($KeyFlags,$id)
If you're using a command to start things off, why do you need a distance to do first?
Another issue might be the directory and folder you're placing your briefing.lpr file. It should be in the standard \bin\default\includes directory, and should be added into the existing addonsused.lpr file.
Good luck.
2 Formula Americas cars with same short name
Both the Formula Americas cars (2019 & 2022) have different Skin ID's, but the same short name - FOA2
Shouldn't the short name's be different too?
If both cars are involved in the same race, then when the race is complete, the timing screen shows the same name, which can be confusing.
Shouldn't the short name's be different too?
If both cars are involved in the same race, then when the race is complete, the timing screen shows the same name, which can be confusing.
Lights should be controlled by sector as well as globally.
In racing, Yellow is used in affected sector, but Red to stop race is global.
Top Times per vehicle ...
I've also included the 3 layouts I made for the circuit; Perimeter, Short and Long.
I've also included the 3 layouts I made for the circuit; Perimeter, Short and Long.
LA1 Sinanju Go Kart 2
I've made another go kart layout, but this one is only for use on my 'Sin'rs' server.
Layout consists of 3 routes, but am using the long route, which is approx 0.85 miles / 1.36km.
Overhead - Routes
Whole track layout
My layout is heavily based on the La Conca track in Italy. I added another piece of track from turn 2 so I could make a perimeter layout.
There are 17 vehicles to choose from to try set a hotlap - the MRT and 16 mods. These are go karts and other small vehicles.
Be aware - a lot of these mods want to tip over on a short track with tight turns.
Many thanks to the mod makers for publishing them for general use.
If I've missed any mod that you think may also be suitable for use on a go kart track, let me know, as another 4 or 5 would be nice.
Even though I'm not using it on my server, taking advice given when I submitted my previous go kart layout, I've included a pit area.
EDIT
3 Layouts in post below.
Layout consists of 3 routes, but am using the long route, which is approx 0.85 miles / 1.36km.
My layout is heavily based on the La Conca track in Italy. I added another piece of track from turn 2 so I could make a perimeter layout.
There are 17 vehicles to choose from to try set a hotlap - the MRT and 16 mods. These are go karts and other small vehicles.
Be aware - a lot of these mods want to tip over on a short track with tight turns.
Many thanks to the mod makers for publishing them for general use.
If I've missed any mod that you think may also be suitable for use on a go kart track, let me know, as another 4 or 5 would be nice.
Even though I'm not using it on my server, taking advice given when I submitted my previous go kart layout, I've included a pit area.
EDIT
3 Layouts in post below.
Last edited by sinanju, .
Made a video of my driving a grass cutter round the 'infields' layout ...
As per your suggestion, I've made 2 different versions of the 'Perimeter' layout that now have pit areas. One to the left just before Turn 1, and one to the right ...
If anyoune wants to modify the other 3 versions, then be my guest.
As each layout uses the maximum 3000 objects, you'll need to remove the bales round some of the bends to give you spare objects to use for pits.
If anyoune wants to modify the other 3 versions, then be my guest.
As each layout uses the maximum 3000 objects, you'll need to remove the bales round some of the bends to give you spare objects to use for pits.
LA1 Sinanju GoKart
Go-kart layout with 4 configurations ...
Heavily based on circuit layout on Saipan (co-ordinates: 15.266423936618589, 145.78913892726305).
Heavily based on circuit layout on Saipan (co-ordinates: 15.266423936618589, 145.78913892726305).
For your original question, rather than bother with an insim, why not just add a note to your host welcome message.
eg. "Remember: At the start of a race, pull the right hand side wheel paddle when the lights go green.".
eg. "Remember: At the start of a race, pull the right hand side wheel paddle when the lights go green.".
The %nl% part means put next lot of text on a new line.
On my server, I have the following as part of a table to see the top time for each car ...
The code for this could look like this ...
Because I don't want a huge long line of text in my script, my actual code looks like ...
To make it more readable in the script, I've put the new lines on seperate lines, and started each line with
. "%nl%
The full stop and quotation mark (. ") tells lapper that the current line should be added to the previous line.
On my server, I have the following as part of a table to see the top time for each car ...
The code for this could look like this ...
<?php
openPrivButton( "tt_car_note",$tt_left,$tt_top+142,68,4,3,$tt_time-12,16,"^3This table has to be partially laid out by hand ^8and was last updated: ^019 May 2025"%nl%^1If a driver beats the existing fastest time for a vehicle shown above, then table order may be wrong%nl%^7If a driver sets a time for a vehicle that is *NOT* on this list,"%nl%^2then I will have to manually update the table");
?><?php
openPrivButton( "tt_car_note",$tt_left,$tt_top+142,68,4,3,$tt_time-12,16,"^3This table has to be partially laid out by hand ^8and was last updated: ^019 May 2025"
. "%nl%^1If a driver beats the existing fastest time for a vehicle shown above, then table order may be wrong"
. "%nl%^7If a driver sets a time for a vehicle that is *NOT* on this list,"
. "%nl%^2then I will have to manually update the table");
?>. "%nl%
The full stop and quotation mark (. ") tells lapper that the current line should be added to the previous line.
No problems with wheels, nor with placing concrete objects.
But happens with every other object, such as lines, cones, tyres, armco, barriers, markers, checkpoints, etc.
But happens with every other object, such as lines, cones, tyres, armco, barriers, markers, checkpoints, etc.
FGED GREDG RDFGDR GSFDG