Route checkers are numbered. They show as "route index: n", where n is a number.

If you put your 5 route checkers as per your image, and later decide you want to put in another - say between 3 and 4, then you place your new checkpoint, and click on "route index: ", and give that the number 4, which will automatically increase all higher numbers by 1 and renumber accordingly.

At the moment, you only get wrong way message, and subsequent spec, if you miss a number in sequence. I agree that would be much better if you pass a checkpoint twice, that the same would happen as missing one.

Until that happens, all you can do is try make your route checkers as small as possible, and place barriers and/or restricted area circles where you think people might cheat.

If you check, you'll find that on first lap, LFS doesn't record your time for that lap either, and it's only when you cross a time checkpoint, then the finish line that LFS starts recording 2nd (and subsequent laps) as 'proper' lap(s).

So Lapper does what LFS tells it - Lapper will only record complete lap time (and drift score) when it's a proper completed lap - as defined by LFS.

Nothing much you can do about it, except maybe don't use Practise mode, or set huge amount of laps or time, or, what I've done in past, show a message when driver pops up on track.

Something like;

The pitboard error, you won't get rid of - it refers to the width of the button (32) on that particular line. No reason why lapper doesn't like that part of the code, as it's almost exactly same as the code 2 lines up. And it appears in lots of other places too.

The line in question is for an ELSE statement, so might never get used, and so you could just put a hash at the beginning of that line to disable it, as likely no-one changes the pitboard anyway.

The others - I think these are because you are missing one of the standard add-ins (utils.lpr) that tell lapper what to do with the function closeButtonRegex.

Make sure utils.lpr is in your /includes directory, and if there, make sure it has not been disabled in the addonused.lpr file.

Failing that, you'll have to show what the error lines refer to - just copy and paste one of each.

Driftmenu - I have some hazy recollection of making that on request - for you? - something to do with on screen button to show drift score table and/or arrows scrolling drift scores back and forward?

Quote from THE WIZARD DK :

im up for an Airport track as well....

An alternative would be Ehra-Lessien (posted HERE), VW's giant long test track, or, in the UK, the Millbrook Proving Ground


which has giant ring road, about 1km in diameter.

Call it a never ending long road.

Website HERE.

Google maps.

Some times have been set on the server, and this is best achieved to date:



(Thought I'd show times now while I still have my name on top for some of the cars!)

Quote from cargame.nl :

A long time ago I learned on school that 1 m/s * 3.6 = 3.6 km/h

I started school in 1964, and at no time since that first day, till I left, and started work in 1976, was I ever taught that.

If asked, might have been able to work it out for myself...1 ms
=> * 60 seconds = 60 metres per minute
=> * 60 minutes = 3600 metres per hour
=> / 1000 in a kilo = 3.6 km per hour.
Then, for the proper speed, 3.6 * 0.621 = 2.24mph.

I've made an Oval track that you have to drive on a large grass area within the Westhill confines.



There are certain sections of the layout where the wheels of the car disappear into the grass, and in the last turn, before start/finish straight, I've managed to get my anti-gravity machine, hidden underground, working at long last.

I haven't covered every square inch of the track, but there doesn't appear to be any holes for you to fall into, and even with the long grass and levitation, there is traction all round oval.

Layout is saved for 8 laps, but this can be edited in SHIFT U mode to whatever number of laps you wish.

I'm currently using this layout on one of my Sin'rs servers. Only using cars that have Autocross tyre capabilities (UF1, XFG, XRG, LX4, RB4, FXO and XRT).

As you can see in the screenshots, sub 40 secs is achievable in the UF1.

I can confirm that RackService provides lapper, and any issues I've had (ALL of my own making!) have been sorted out quickly, and I've even been provided with an extra overnight backup facility for the sql database files that lapper creates and uses. Great service!

Something I made for one of my servers, which could be accessed once you'd completed the course layout.



For this layout, I added slight extension to what's on the server.


Video of hoop and jumps performed by Pavlu

For 2nd jump, you need to be doing at least 80mph / 130kph.

Since early this morning, have been unable to access Control Panel, or ftp in.

Yet Another Rally Layout...


ROUTE


IMAGES

Includes simple RoC layout part way round route, along with driving balancing act at top of small cliff, leading onto short sky bridge. Route goes through both underpasses and uses part of one of the kart tracks.

There are a few sections where you must drive on the grass, including a large section after the RoC complex.

My best, non-respectable, time in a XFG was;

sectors 1, 2 and 3 > 2:45.65 / 6:15.26 / 10:05.72
lap time > 13:00.39 + penalty > 2.00

Overall time: 13:02.39

In my defense (e.g. an excuse), I kept damaging the clutch by 3rd sector, so a much quicker time is easily do-able.

Note: there are tight constraints in keeping to the course, as I've used approx 60 route-checkers, so you must go through the 'gates' (easily spotted).

Found way to measure course - just shy of 10 miles / whisker over 16km

Last edited by sinanju, Sun 17 May 2015, 22:49. Reason : Added layout length

Made a layout on Westhill that basically goes round the perimeter, and is 3.77 miles / 6 km in length.



Has start and finish lines, corner markings and route 'gates', which you must drive through, else you get spec'd. You must also stay on road at all times, or you may get spec'd.


Image: start and 'gates'.

I've got it on one of my Sin'rs servers with choice of XFG or XRG only (XFG took me just over 3 mins 30 secs to get round).

Likely if you have better eyesight / memory than me, you'll manage better times - I struggled to see signs when they were far away.

Last edited by sinanju, Wed 25 Mar 2020, 05:14.

Made a layout on WE2X that heads in towards the roundabout that leads to the tunnel that goes under the track (see image below), and while driving, road and some of the surrounds suddenly went blue.



Same thing happens everytime I go this route.

No problems with car falling through a hole or anything, and at speed, it's just a quick blue blur.

I saved an mpr; I slowed down at the 40 mins mark to see it better.

Last edited by sinanju, Sat 11 Apr 2015, 23:23.

I'm now running slightly longer version of this layout on one of my Sin'rs servers.

EDIT: Now there's just over 200 timed laps, best of these are ....



As you can see, even though it's a Rally track with off-road sections, people will still try set times with every car available.

Last edited by sinanju, Sun 26 Apr 2015, 00:08. Reason : Top times from over 200 Timed Laps (as at 25 April 2015)

So after spending hours and hours and hours turning off add-ons and then re-enabling; no difference.

Played with removing 2nd split, then when that didn't work, added 3rd split; no difference.

Tried removing all checkpoints; no difference.

By this stage, fed up, so went on my server and tried setting time in UF1 - got round in just over 5 mins 30 seconds, but time not saved.

Next tried XFG - got round in about 4:50, but big penalties. No time saved. Tried few times, but always penalties putting me over 5 mins. Finally managed clean(ish) lap and recorded under 5 mins. Time recorded!

Ha!

Went round slowly in XRT (lots of people have recorded times with this car), and took over 5 minutes to cross line - no time recorded.



As you can see in the image, few people have taken over 5 mins to do lap, which LFS has recorded, but !top command for their car not showing their times.

CONCLUSION:

Lapper limitation in that any layout that takes more than 5 minutes to get round, regardless of car, the time will not be recorded for !top table. If you score drift points in that car, in same lap, points will be recorded.

Can anyone confirm having problems with times not being recorded if taking more than 5 minutes to complete a lap in a layout?


EDIT: In version 7.0.4.5: the Laptime is increased to 30 minutes

Last edited by Bass-Driver, Tue 8 Aug 2017, 22:01.

Not a pitboard issue, as I turned it off and tried laps in UF1, but time still not recorded.

Tried renaming layout from WE2X to WE2Y, and WE1X and WE1Y. No difference.

Next step will be to turn off all add-ons and re-enable them one by one to see if one of them is causing issue

Personally, I use PSPad, which colours different parts of the code script to make it easier to see if there's a glaring error.

Use PSPad with lapper.ini (found HERE), which has been setup with colours for different syntax highlighters.



Won't help with your specific issue, though.

Last edited by sinanju, Thu 9 Apr 2015, 06:10.

Quote from Gutholz :

...please read doc/readme.txt.....there is no such file?

A lot of very useful information can be found in the doc folder, when you open zip file (bin, doc, spec, src).

A lot of coding help can be found in changes.txt, and various Vars, etc, can be found in Lapper Events.txt and playerVars.txt.

Yisc is the guy for helping you!

Surprised it works at all - normally you have to specify your GlobalVar.

Your code

Should define the Var value.

So, its name of Var first, followed by same name with a value.

The most common GlobalVar's are usually specified by people for button properties, such as;


Lapper doesn't care if you layout each Var on 1 line or 2, as long as Var
Name and Var value are both followed by a semi-colon.

GlobalVar $MHeight; $MHeight = 4; # ...height of row of text

or

Might have been a bit premature!

On my new rally server, I've done laps in UF1, RB4 and BF1.

Only the BF1 time shows in !top, but only the UF1 drift score shows in !drf. Nothing for RB4 anywhere.



My BF1 time is fastest of the 3 cars I've used, and UF1 has had highest drift score, so it seems as if only quickest/highest is being saved. For me at least.

Only a few people have set times on server, but most of their times/scores seem ok. Not all. For instance, someone has set time in XRT, and apart from seeing time in top 12 on front screen, his time doesn't show anywhere else, but his drift points do!

I can't download the sql database (GripPB.dbs, etc) files yet, but when I can (tomorrow), I'll need to check if my times/scores are being saved; but maybe not being displayed.

I've made up a rally layout and put it on one of my servers today (Sin'rs Too [Westhill Rally]).

Based on this layout HERE, with an additional section.



Most people seem to want to race the BF1 on it, even though there are bits where you have to go on the grass and gravel - go figure!

Many thanks for that, although I had problems with getting it working - but now everything ok.

Tried setting the cfgsplit on my layout and wouldn't work. Played around with split quantities, in case having start, 2 checkpoints and a finish line was actually 2 splits instead of 3 (it's not). Still same problem.

Made small test layout - straight line with 2 checkpoints only 20 metres or so apart, set cfgsplits to 3, and everything worked fine. Times shown on pitboard correctly, drift points shown, and times/points available with !top and !drf commands.

Set same cfgsplit setting (3) on my original layout and pitboard/drift scoreboard still not working correctly. Eventually got round to deleting the start/finish/split lines, then put them back in layout, and voila! All working

I made a Westhill WE2X rally layout (layout), and I was going to use it on one of my servers.

Before I load things on my server, I check that lapper will have the correct stuff loaded, as I sometimes have to make configuration changes (usually speed trap locations, etc). As I normally load AutoX layouts, I usually check the pitboard add-on, and change if number of splits has changed.

I've added WE2X into the pitboard file, but it wasn't showing the times correctly, nor was my drift scoreboard showing drift scores.

Added WE2 and WE2R to pitboard file, but still not working properly for WE2X, although WE1 and WE2 work correctly.

I don't think this is anything to do with the pitboard file, but something in lapper.

.

Lapping WE1 or WE2, lapper, the pitboard and drift scoreboard all work properly, and I don't get the message:
Open configuration detected
Taking set number of splits:

First time I've ever seen this message.

Changed the tracklist.cfg file to alter WE1/WE1R and add the other Westhill configs. Altered file attached (just remove the .txt at end).

There is a file called trackInfo.cfg, that has all the original track names and abbreviations, with various cars and times, but I'm not sure how this file came to be (it says auto generated file), nor if I should change it. How would I know times to add for new configurations?

Not sure lapper is supported anymore, so if this is a problem within the lapper programming, is there a solution?

Last edited by Bass-Driver, Tue 8 Aug 2017, 22:02. Reason : 5 min laptime increased to 30 min

Made a short rally track - mainly road driving, with very short spells on gravel and grass.

Route includes going through 2 underpasses (tunnels).



Has rally start and finish positions, 2 visible timed checkpoints, and a number of route 'gates'. Route has to be followed, as invisible checkpoints placed.

2 layouts;

> beginner - more arrow sign markers and some additional tyres to use as possible braking points

> intermediate - exactly same route, but less arrow markers and no tyre braking point references

Whichever layout you may choose to use, be aware that your safety has not been compromised!


I did few laps in XFG, and my best time was a 4m:09.24s (S1 1:21 / S2 2:35). I've no doubt that someone who can actually drive could get that well under 4 mins

I would be interested in seeing video of anyone that can do much better times.

Also, as this is my first off-road (especially not an AutoX layout), so constructive criticism welcomed.


Edit: Managed to get my best time down from 4:24 to 4:09!

Last edited by sinanju, Tue 7 Apr 2015, 09:02.

I know absolutely nothing about how you are programming this (!), but it looks like a range? If so, can you change it to just a specific 1 x 1 X,Y square, and try crossing that space to see if anything happens.

At least you would know that basic code is working correctly, and as you expect.

This would be a doddle in LFSLapper ('lapper')!

I'm so used to;

RegisterAction (e.g. Node or Zone), track, X, Y, size, sub-routine_name
e.g.

Apologies, if nothing here in this post helps.