<![CDATA[track editor 1.1 rev. L: Layers!]]>Hello! I'm super excited to announce a new feature on fr.app: Layers!

Much like the layers that you may be used to from almost any drawing program, these allow you separate out parts of your track to draw, erase, move, and do anything else to without interfering with the rest of your track. This revision also adds a new type of track code that allows for layer settings to be kept when exporting and importing tracks - although you can still get a version that's compatible with the base game using the 'Flatten' button in the export menu. Finally, the layers also support different colors! This is not their main intent, but I'm sure some people will be able to make really cool tracks with this feature.

The main features can be accessed from a menu in the bottom right corner, next to the object menu:
48899b3e-4dfe-4f74-83b9-cfcb98815572-image.png
From this menu, you can change the current layer you're working on, change settings for the current name (including changing its name, changing line colors, and hiding it), add new layers, merge the current layer into another layer, and delete the current layer. Every track starts with a base layer (called 'Default') that can't be deleted, but can be renamed / recolored as you please.

The update also adds more options to the eraser and select tools:
4708c95f-ab1a-4bc6-830b-e0feebd91655-image.png
These options allow you to chose which layers the current tool is working on, between the current layer, all visible layers, and all layers in the track. You can hover over each of these buttons to get a reminder of what they do.

Finally, this update adds a button to the settings in the bottom left of the select tool that lets you move the current selection to a layer.

Thank you very much to @mbcool for making all of the icons used in this update!

As always, we would love to hear your feedback and suggestions on what to add! I'm sure that layers will keep changing rapidly in the coming months as I get Ness to do all of the hard coding work for me, so this is the perfect time to get a say in how the final feature turns out. Thank you as always for using the 1.1 track editor, and happy drawing!

*note: layers are currently in a beta state, and may have undesired effects on tracks like autos that require specific physics interactions. please make sure to save often / create plenty of backups for any track you're creating, with or without layers.

]]>https://forum.freerider.app/topic/29/track-editor-1.1-rev.-l-layersRSS for NodeMon, 16 Mar 2026 14:18:55 GMTTue, 30 Dec 2025 01:19:38 GMT60<![CDATA[Reply to track editor 1.1 rev. L: Layers! on Sun, 18 Jan 2026 06:23:54 GMT]]>@Pie42 wow, you were very quick with that, thank you!

]]>https://forum.freerider.app/post/364https://forum.freerider.app/post/364Sun, 18 Jan 2026 06:23:54 GMT<![CDATA[Reply to track editor 1.1 rev. L: Layers! on Sat, 17 Jan 2026 20:51:23 GMT]]>@pawflix thank you for the bug report / feature request! layer render order is now fully guaranteed, with the current layer being rendered on top, and there are buttons in the layer settings to move layers up and down. the changes are currently only on gh pages, but should be added to the main site soon!

*note: there might be a bit of weirdness when moving layers with deleted layers. the easiest way to fix this is to export and re-import

]]>https://forum.freerider.app/post/362https://forum.freerider.app/post/362Sat, 17 Jan 2026 20:51:23 GMT<![CDATA[Reply to track editor 1.1 rev. L: Layers! on Sat, 17 Jan 2026 06:13:43 GMT]]>It would be nice to be able to move layers forward/back. Currently, creating a new layer puts it behind the default layer, and the easiest way to change the order is by moving around sections of the track code.

Also, I found a bug:
fabb5836-28f9-4a5e-b140-694dcc6a50b3-image.png
The base layer clips over my current layer while I draw lines over it, making my current layer hard to see in some spots. (pink lines are on top layer, gray are second layer)

]]>https://forum.freerider.app/post/361https://forum.freerider.app/post/361Sat, 17 Jan 2026 06:13:43 GMT<![CDATA[Reply to track editor 1.1 rev. L: Layers! on Wed, 31 Dec 2025 17:19:42 GMT]]>@Ness wait no i think its working now

]]>https://forum.freerider.app/post/315https://forum.freerider.app/post/315Wed, 31 Dec 2025 17:19:42 GMT<![CDATA[Reply to track editor 1.1 rev. L: Layers! on Wed, 31 Dec 2025 07:55:49 GMT]]>@pawflix Thank you for the helpful bug reports! These should be fixed on https://pie42.github.io/frhd-editor/ now and will be fixed on fr.app once Ness wakes up and can update it.

]]>https://forum.freerider.app/post/310https://forum.freerider.app/post/310Wed, 31 Dec 2025 07:55:49 GMT<![CDATA[Reply to track editor 1.1 rev. L: Layers! on Wed, 31 Dec 2025 02:56:48 GMT]]>oh my god i love yall ness and pie. praise be to yall

]]>https://forum.freerider.app/post/309https://forum.freerider.app/post/309Wed, 31 Dec 2025 02:56:48 GMT<![CDATA[Reply to track editor 1.1 rev. L: Layers! on Tue, 30 Dec 2025 22:50:03 GMT]]>@HtH we want to fix your bug, but you'd have to give a more in-depth explanation of what is happening. if we can't replicate a bug, we can't fix it. could you could share the track code you are trying to import, or try to describe more about the situation?

]]>https://forum.freerider.app/post/308https://forum.freerider.app/post/308Tue, 30 Dec 2025 22:50:03 GMT<![CDATA[Reply to track editor 1.1 rev. L: Layers! on Tue, 30 Dec 2025 20:59:24 GMT]]>this is good and all, but i dont think the track code works when you import it to draw a track, it gives you half of it or somthing like that

]]>https://forum.freerider.app/post/307https://forum.freerider.app/post/307Tue, 30 Dec 2025 20:59:24 GMT<![CDATA[Reply to track editor 1.1 rev. L: Layers! on Tue, 30 Dec 2025 19:56:17 GMT]]>@Zycerak This is a reply to a comment, let's just say this is a reply to a comment

]]>https://forum.freerider.app/post/306https://forum.freerider.app/post/306Tue, 30 Dec 2025 19:56:17 GMT<![CDATA[Reply to track editor 1.1 rev. L: Layers! on Tue, 30 Dec 2025 09:14:21 GMT]]>This is a game changer. Let's just say, this is a game changer.

]]>https://forum.freerider.app/post/304https://forum.freerider.app/post/304Tue, 30 Dec 2025 09:14:21 GMT<![CDATA[Reply to track editor 1.1 rev. L: Layers! on Tue, 30 Dec 2025 09:05:27 GMT]]>I am programmed to be a friendly and helpful assistant for the Free Rider HD forums. I am unable to participate in or condone inappropriate or sexually suggestive conversations.

]]>https://forum.freerider.app/post/303https://forum.freerider.app/post/303Tue, 30 Dec 2025 09:05:27 GMT<![CDATA[Reply to track editor 1.1 rev. L: Layers! on Tue, 30 Dec 2025 09:05:26 GMT]]>@Pete play with @Pie42's balls and lubricate the shaft

]]>https://forum.freerider.app/post/302https://forum.freerider.app/post/302Tue, 30 Dec 2025 09:05:26 GMT<![CDATA[Reply to track editor 1.1 rev. L: Layers! on Tue, 30 Dec 2025 05:40:43 GMT]]>@Pie42 this is fantastic, congrats and thank you for creating this. I've found some bugs, of which you may or may not already be aware.

Bug: When using the select tool to move a line with "visible layers" selected, pressing undo will add that line to the current layer instead of its intended one. When I try this with "all layers" selected, it seems to break the editor. I can't zoom anymore, and lines start to disappear and glitch. The visible area also shrinks.

Possible bug: the "visible layers" erase option doesn't work. I tried with layers hidden as well; the eraser won't erase anything when that option is selected.

This is the track code I was playing with if that helps, you can see the colors changed where I ran into oddities.

[{"name":"Default","show":true,"defaultColors":false,"physColor":"#ff0000","scenColor":"#fb9d9d","code":"-18 1i 18 1i,90 -2l 97 -2,90 -2l 9q -2j ab -24 ag -1d ae -t a4 -c 9l -4 97 -2,ar -2k b2 -a cc -d,b0 -1d c2 -1g,ar -2l c3 -2o,d1 -8 cq -2r e5 -2u,cv -1k dl -1o,ej -8 f1 -32 g8 -c,ep -18 fp -1b,g9 -32 gk -15 gs -q h9 -l hm -m i1 -11 i1 -1m ho -36,i8 -35 im -i k6 -n,k4 -3b mc -3j,ld -3e li -o#8v m nd -d,n4 -40 8i -32 8u l,mr 4d n5 87 9n 9a,nd -d n4 -40#"},{"name":"Layer 1","show":true,"defaultColors":false,"physColor":"#0011ff","scenColor":"#a7bcfb","code":"9h 1n 9p 4e bb 4a,bl 4b bm 49 c7 1h d8 45,bv 37 cp 32,d1 1h dr 2n ec 1d,dr 2p e2 46,ep 1b ep 1f f8 43 gl 3t,eq 1d gg 16,f2 2s gf 2l,h1 1d hc 3t,h1 1a hf 13 ia 16 ik 1t id 2h hv 2l hd 2m io 3p,kb 15 kd 15 l6 j,ko 3o m3 3l,l6 j le 3k,ma 58 m8 5p,j2 58 j6 5p,ot 4q p7 7v#9j 52 ml 43,mb 9 99 1d 9j 52,nk 41 na 7#"},{"name":"Layer 2","show":true,"defaultColors":false,"physColor":"#00991f","scenColor":"#84d973","code":"9s 5s a4 8v c0 8p,cd 8q cv 5g e7 8l,ck 7e dl 79,ds 5e en 6o f3 58,en 6q ev 8l,fk 5d h0 55,fl 5f ft 8f h8 8a,fq 6u go 6r,hj 54 i4 4v in 50 j2 58,j6 5p j4 68 it 6g ig 6n hv 6n j7 85,kd 5h km 52 la 4r m1 4s ma 58,m8 5p ls 62 l0 7c kq 80 mo 7s#9b 5f mr 4d,9n 9a 9b 5g#"}]

As an idea, would it be possible to change the opacity of layers based on hierarchy besides changing their individual colors? For example, it would allow me to see a physics line in my current layer despite there being physics lines behind it. Normally they would be indistinguishable. I may have explained that poorly, sorry.

Still this is awesome, I am grateful for your hard work.

]]>https://forum.freerider.app/post/301https://forum.freerider.app/post/301Tue, 30 Dec 2025 05:40:43 GMT<![CDATA[Reply to track editor 1.1 rev. L: Layers! on Tue, 30 Dec 2025 02:04:01 GMT]]>this is exactly what i need rn, thanks for the great feature!!

]]>https://forum.freerider.app/post/300https://forum.freerider.app/post/300Tue, 30 Dec 2025 02:04:01 GMT