Free Rider Community

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:

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:

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.

@loge_0 congrats i'm so happy for you

the thing with stacked portals is that their behavior depends entirely on the order they're in within the track, which is why i mostly only generate tracks with them. this also means that a variety of features have the potential to mess with their function, including the select tool, layers, and possibly even erasing and undoing, but it isn't guaranteed. if you can remember exactly what you were doing when they stopped working, i'll look into fixing it, but it's a pretty difficult problem to solve. in the meantime, here's a script i made when looking at computer by seasnails, but that doesn't work quite as well for stacked portals:

// ==UserScript==
// @name         double-click portals
// @version      0.1
// @description  ​
// @author       Pie42
// @match        https://www.freeriderhd.com/t/*
// @match        https://www.freeriderhd.com/create
// @match        https://freerider.app/*
// @grant        none
// ==/UserScript==


function main() {
    let canvas = GameManager.game.canvas;
    console.log('double click active ', canvas);
    canvas.addEventListener('dblclick', (e) => {
        let position = GameManager.game.currentScene.mouse.touch.real,
            sectors = GameManager.game.currentScene.track.sectors.physicsSectors,
            sectorPos = position.factor(1 / GameSettings.physicsSectorSize || 300),
            found = false;
        sectorPos.x = Math.floor(sectorPos.x - 0.5);
        sectorPos.y = Math.floor(sectorPos.y - 0.5);
        //console.log(sectorPos, 'sectorPos');
        for (let xOffset = 0; xOffset < 2; xOffset++) {
            if (!sectors[sectorPos.x + xOffset]) continue;
            for (let yOffset = 0; yOffset < 2; yOffset++) {
                let currentSector = sectors[sectorPos.x + xOffset][sectorPos.y + yOffset];
                if (!currentSector) continue;
                let teleporters = currentSector.powerups?.teleports,
                    teleporter;
                if (!teleporters) continue;
                for (let i of teleporters) {
                    //console.log(i, position, Math.hypot((i.x - position.x) ** 2, (i.y - position.y) ** 2) ** 2);
                    if (Math.hypot(i.x - position.x, i.y - position.y) ** 2 < 1000) {
                        teleporter = i;
                        break;
                    }
                }
                if (!teleporter) continue;
                let camera = GameManager.game.currentScene.camera;
                let dCamera = camera.position.sub(teleporter).add(teleporter.otherPortal);
                console.log(dCamera);
                camera.position = dCamera;
                camera.playerFocus = false;
                found = true;
                break;
            }
            if (found) break;
        }
        console.log('double clicked!');
    });
}

let track = undefined;
window.setInterval(function () {
    if (window?.$ && $("#track-data")?.data?.("t_id") != track || +location.href.match(/\/(\d+)/)?.[1] != track) {
        track = window?.$?.("#track-data")?.data?.("t_id") || +location.href.match(/\/(\d+)/)?.[1];
        console.log(track);
        function rInterval() {
            window.clearInterval(v)
        }
        var v = window.setInterval(function() {
            if (GameManager != undefined && GameManager.game != undefined) {
                rInterval();
                main();
            }
        }, 250)
    }
}, 500)

@nathanpertman1
there isn't a strict limit to the number of objects that can be saved, but with them being saved to localstorage, each origin (basically website) has a strict limit of 5 MiB that it can save in total (browser limitation). most likely, when you tried to save your track as an object, the code for doing that errored silently in the background and nothing ever actually saved, meaning it's likely lost forever, and i'd recommend getting rid of or exporting to local files some of your less-used, larger objects. i can add in a temporary fix to let you know when those operations fix, but until we add more sophisticated browser storage mechanisms (and honestly even after that), the only way to be absolutely certain that something has saved is by saving it to disk (downloading it). i'm sorry for your loss, and i hope you have previous backups of the code.

@Zycerak zycy i'm sorry i love your life updates but when i see a post this long i just ctrl+f the word 'pedo' and count the results

@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

@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.