1. #1

    Optimizing Track Performance?

    Today I unfortunately discovered how inaccurate testing a track in the editor can be. I had spent the last month working on a new track and finally had what I considered to be ready to publish. I spent equal if not more time testing the track in the editor and occasionally in multiplayer, all while having no issue.

    I was confident that if I didn't have any issue as far as performance is concerned that I would be publishing something that performed the same in Track Central. This was not the case.

    The track central version of my track does not render some objects for about 0.5 of a second at every checkpoint reset. I don't know why this happened but I know I would have never published this track if I was aware of this issue, it looks bad.

    Less than an hour after publishing my track I sent a request to the track removal thread. I'm not going to post anything else regarding the issue in the support thread, I don't think it will be fixed. So how can I work around this? How can I fix something that I can't see until after I publish?
    Share this post

  2. #2
    The editor has a performance overlay in the radial menu, one of the directional buttons I believe. Or you could 'lock' your track with a button code. After the code has been entered, the track may begin. Be sure you don't beat the track while testing on TC though, unless you don't mind people looking around using the replay camera.

    Create a temporary Checkpoint at the start, before the proper one, and place a wall to keep the bike & rider there.

    Add a custom camera that faces away from the track and set it as the Game camera.

    Use buttons that do not show up in replays: All except Left Stick, A/RT and X/LT.
    Set each of those buttons, except one, to the following.
    On Hit > Set Variable Event: Add (different prime number each) > Variable Data Source

    The remaining button is your confirmation button. Set the following:
    On Hit > Generic Filter:
    slider = Equals
    Target 1 = The variable Data Source
    Target 2 = Secret number
    TRUE > Player Event:
    Reset to Checkpoint = 1 (or +1 from the first)
    Trigger Event > Camera Event: blue camera
    Share this post

  3. #3
    Thanks Jolan. I've known of the stats menu but never actually utilized it so that'll be what I look at first. It's a shame the only way to effectively test this issue is after uploading but locking people out of the map seems to be the best method. I'll set this up and spam track central trying different things until it finally performs the way is does in the editor.

    If anyone could give me a few suggestions as to why the problem could be occurring that would also be quite useful.

    I've since withdrawn my track removal request (hopefully) because other players are enjoying the track and have asked that I don't. I however will continue to play it in the editor.
    Share this post

  4. #4
    Originally Posted by DapperDash Go to original post
    Thanks Jolan. I've known of the stats menu but never actually utilized it so that'll be what I look at first. It's a shame the only way to effectively test this issue is after uploading but locking people out of the map seems to be the best method. I'll set this up and spam track central trying different things until it finally performs the way is does in the editor.

    If anyone could give me a few suggestions as to why the problem could be occurring that would also be quite useful.

    I've since withdrawn my track removal request (hopefully) because other players are enjoying the track and have asked that I don't. I however will continue to play it in the editor.
    Try this... https://www.youtube.com/watch?v=6jyMX3-au5c
    Share this post