If you prefer fast paced layouts, then you probably wouldn't like my amended KK2 layout, that I've called Kris Kros 3.



Last section is very fiddly and slow.

EDIT
====

Forgot to add layout

Last edited by sinanju, Fri 10 Mar 2017, 00:59. Reason : Added V3 layout

Have fun

I've updated the layout for my own use - put video of couple of laps on YouTube ... and put link here on forum under Movies section https://www.lfs.net/forum/post/1917586#post1917586

Layout I made for AU1 Autocross area, called Kris Kros 2 ...



My pc wheel is broken, so used keyboard to drive laps.

Updated my old AutoX AU1 Kris Kros layout using concrete objects, and extending layout some, so now approx 1,400 metres / 0.8 miles long overall.







Not sure if the tunnel and ramp sections make this layout for drifting - probably ok if you are a controlled drifter.

May put this on my SIN'RS server later.

Edit - V3 included in a later post (5th).

Last edited by sinanju, Fri 10 Mar 2017, 01:02. Reason : Added V3 of layout

Do what you want with them - that's why I put them in the public domain. No credit required.

All my old layouts could do with being updated anyway, now that's there more and different type of objects.

Glad you like it, although seems very old fashioned compared to what you can do with layouts now, especially with additional objects and types of objects.

It's one of my very old layouts - called AU1 Kris Kros - likely that I used it for a while on one of my Sin'rs servers.

Would have been good to watch collisions in the intersections when lots of people on layout at same time.

Layout attached.

Used same sort of idea for another layout - Windmills of your mind.

Didn't think they were as good as my Scaletrix and Livingston layouts (both names can be found using search function - each had multiple layouts).

Quote from Popughini :

That in a zone X of the track stop and there they supply you fuel

Why not just go into Autocross (Shift U) mode and place a pit box?

Don't see why you need to make it any more complicated than that, and everyone should recognise it as a pit of and what it does.

Quote from Bass-Driver :

See many variations for Timeattacks

Funny you should mention that, because I amended the track slightly to get a layout i've called 'High Plains Drifter'.



Layout currently on one of my (Sin'rs) servers, where some lap times have been recorded!



My XRG time is almost 5 seconds slower than the one recorded above, so the rest of my times should be easily beatable. And as I can't drift, all my drift scores should be easily beaten too.

I made a couple of tongue in cheek type Blackwood layouts for a demo user (who couldn't use them if he only had demo license), but they may give you idea's to make your own ....

https://www.lfs.net/forum/thread/86925

https://www.lfs.net/forum/post/1877205#post1877205

First layout is extremely short!

As for your shops issue, you'll need to give some details, especially in regard to what InSim you are using.

Best Times and Drift Scores after 100th recorded lap ....

Amended one of my layouts for no other reason than to go with the puny pun I came up with!

It's basically for playing about on.

Overhead shot of layout ....


Some shots of parts of track layout ...

... little house on the layout



... windmills of my layout



Very little in way of barriers to stop you falling off edge, so watch what you're doing!

EDIT: Details for High Plains Drifter layout can be found few posts down.

Last edited by sinanju, Sat 24 Dec 2016, 12:03. Reason : Added details for High Plains Drifter layout

So, less than a week, and times have been set for each car.

Best times, and top Drift scores...

Only just found my old Microsoft Sidewinder wheel to replace my faulty G25, so can now drive my layouts again

Layout now loaded onto my 'Sin'rs EbolaDrome GT Layout' Server.

I've recreated the Grand Tour 'EbolaDrome' track for LFS, as close to 1:1 scale as I could, considering there's no real details anywhere, and measuring small distances on Google maps is difficult.

Layout is the 'unexploded bomb' version, where double chicane added, leading to 'old ladies house'.

Due to limitation in LFS autocross size (both autox areas are far too small for this layout), I've had to build the track layout in the air - so this is another skytrack. The track length is approx 2.375 metres / 1.48 miles long.


Also, due to lack of autocross objects (currently 1,800), large parts of the track have nothing at sides to stop you falling off. This has unintended consequence that means that you have to be more exact in your driving to get round some of the turns - no bad thing in my view, as a lot of drivers use barriers as bumpers to help to get round corners quickly. Does mean that getting a clean lap will be very frustrating!

Certain corners that are likely to be targets for 'cutting' have been sown with autocross 'restricted area' circles, so best to stay within track white lines - especially at start, where there's a left kink. There are also 'route checker' circles placed around track to make sure you drive correct route.

I've made a video of a standing start lap in a RB4 - driven slowly as I kept falling off the track when trying to video me driving fast ...

Overhead shot of track layout HERE

Start/Finish line HERE

Not straight / Your name here corners HERE

This layout will be loaded onto one of my Sin'rs servers once I get my lapper InSim working with the layout.

I'll repeat - without seeing your code script, likely not much can be done to help.

I'm not sure what translation service you are using, but it's outputting rubbish, or at least, nothing I can understand.

The Hazard Lights script is a CASE command that will output buttons ONLY when you type the word "!blink".

If you already have other buttons in your lapper script called 'blink', then the newer buttons will overwrite the older same name buttons.

Is this what's happening?

Without seeing your code script, likely not much can be done to help.

If you're not using 'regex' to close buttons, then you'll have to show your code (preferably saved in a zip file) so someone can look at it.
If you are using regex, then you need to change your code a bit, but it's possible that you have given multiple buttons the same name.

Updated times for this track layout, which is still on my Sin'rs server, along with best drift scores to date (number 1 is best score I've ever seen on any of my layouts!) ...

Made this layout a while ago, and was going to put it on one of my servers once I'd done timed laps in every car. Unfortunately, my wheel and pedals went wonky, so couldn't finish doing laps in every car.

Track layout ...


My best times (single lap sprint) ...



Different track views ...



Be aware that the track isn't smooth - this is deliberate. Lots of people have complained over the years that the LFS tracks are too smooth, so I made bits that overlapped and this causes bumps. Think of it as how a track might be after a small earthquake tremor - only you are driving on an iffy track that's a long fall down!

To help others in future who may have similar issue, can you please detail what the problem actually was, along with the solution?

What would be simpler, would be large single colour light panels that you could place and have change the colour of, both by InSim command, as is possible just now for the existing layout start-lights.

Colours of Green (safe), Yellow (warning), Red (danger), and Blue (let leaders past).

Not only could they be used for proper racing, but if you were to place the Red, Yellow (as Amber) and Green in certain permutations (vertical, horizontal), then you could make your own traffic/start lights as you suggest.

The few people who make layouts do so regardless of size of area available or number of objects that can be placed.

Increasing these will make little difference, except for those that make layouts.

Part of the challenge for the layout maker is to see if you can make something challenging with what tools we already have.

Part of the challenge for the driver, is to see if they are better at the layout than anyone else.

For someone who is likely to only spend just over 2 hours a year on LFS (5 mins x 26 fortnights = 130 mins), I don't think you are qualified to say anything about the game.

If you were to spend the same amount of time playing LFS as the average person brushed their teeth in a fortnight, maybe I'd think you had a viewpoint worth exploring, but you don't, and neither are you brave enough to put your country rather than hiding behind "other".

For this tutorial, it is assumed that you will already be aware on how to code basic buttons.

In LFSLapper ("lapper"), you can use Nodes and Zones to ‘trigger’ a sub-routine (a ‘sub’) for something to happen, for instance, open a button to display text.

Node
A Node is an invisible line that cuts across a track, and divides the track into small sections.



Typically, nodes would be used for Start/Finish lines, and splits/sectors. On LFS tracks, these are hard-coded in specific nodes on the track. You can place your own Start, Finish and (up to 3) split/sector lines on your own layouts. If placing these items, LFS and lapper are both configured to give timing details.

If you know the Node number, you can also define that to trigger your own sub.


Zone
A Zone is an invisible circular area that can be placed on any area of the track, or even off-track, and is used to trigger an event.



With LFS running, and LFSLapper connected to your LFS server (either online or local), you can find the Node and Zone coordinates by driving to the area you want to define then typing the following commands;

!node
!zone

Typing !node will display a single number (e.g. 123), and typing !zone will display the X and Y coordinates (e.g. -40 123).

Zone X and Y coordinates can be negative numbers as well as positive. And a zero (0).

These Node and Zone numbers will be needed for any code you make.

Once you have the numbers, you have to Register the node or zone, which is used to define the place chosen.

In lapper, the code could look like;


RegisterNodeAction
The first part of the code defines the Track name abbreviation.
The second part, the number, defines the Node line.
The 3rd part defines the name of the sub(-routine) that is to be run when a car crosses the specified node.
The double quotes can be used if you want a second sub to run when car leaves node. Replace quote marks with name of sub. Leave quote marks if no sub is to be used.

Example sub for node;


This sub basically opens a background box, with RADAR at top, and your speed underneath.

Example output of a Node sub



RegisterZoneAction
The first part of the code defines the Track name abbreviation.
The second part, the 3 numbers, defines the X and Y coordinates, along with the size of the zone in metres. Minimum size would be 1.
The 3rd part defines the name of the sub(-routine) that is to be run when a car crosses into the specified zone.
The double quotes can be used if you want a second sub to run when car leaves zone. Replace quote marks with name of sub. Leave quote marks if no sub is to be used.

Example sub for zone;


Example output of a Zone sub




Or to put it another way, think of SatNav - you put in your destination (the ZONE), and when you get there, you get message that you've arrived (the SUB_ROUTINE).

You can help define the node or zone by adding lines and objects, which will help to show the section better than just seeing an anonymous piece of track or off-track area.


EDIT: Updated for LFSLapper V7.0.4.4 as the sub callback for Zones and Nodes now has an extra variable ($ZoneID).

Last edited by sinanju, Thu 5 Jan 2017, 15:16.