1. #1
    NasT65's Avatar Senior Member
    Join Date
    Apr 2014
    Posts
    628

    Statistics Overlay

    So, I'm using the new statistic overlay. I don't have any performance issues, but one bar has me concerned. There's not really much going on at all yet. One bar...dynamic modifications is almost peaked already. Can anyone tell me or take a guess as to what those are?
    Share this post

  2. #2
    mutetus's Avatar Trials Developer
    Join Date
    Dec 2013
    Location
    The land of fin.
    Posts
    859
    Dynamic modifications bar is simply the amount of animations and visibility changes going on every tick. A good reminder to turn off your animations that are not needed anymore. I think there were 3 or something by default in empty track so everything above that counts.
    Share this post

  3. #3
    NasT65's Avatar Senior Member
    Join Date
    Apr 2014
    Posts
    628
    Thanks mutetus. I wondered about that. At One point I did turn a bunch of stuff off but didn't see anything change. Does the editor take a few minutes to recognize the change or could other things affect that as well. Is turnin off the trigger enough or is one better off to turn off each card in a chain? Thanks again.
    Side note...it would be super handy to have a short definition of all the things in the overlay, and what exactly changes them. Maybe we could get a glossary and sticky this for editors ?
    Share this post

  4. #4
    mutetus's Avatar Trials Developer
    Join Date
    Dec 2013
    Location
    The land of fin.
    Posts
    859
    You need to be in the track test mode for the bars, like active objects, to work correctly since in the editor a larger area has physics activated. Also to see dynamic modifications you need to test the track. But they do all work in real time.
    Share this post

  5. #5
    NasT65's Avatar Senior Member
    Join Date
    Apr 2014
    Posts
    628
    thanks again mutetus, all very helpful. One last question...do the devs plan to give us a breakdown of the whole overlay at some point? i think it would be really helpful. Lots of it is self explanatory, but i think there were several that had me scratching my head in confusion last night if i remember right lol.
    Share this post

  6. #6
    mutetus's Avatar Trials Developer
    Join Date
    Dec 2013
    Location
    The land of fin.
    Posts
    859
    We will soon shed some light on the new stuff, but let's get the game completely launched first
    Share this post

  7. #7
    NasT65's Avatar Senior Member
    Join Date
    Apr 2014
    Posts
    628
    thanks again mutetus, apologies if i sounded pushy, it was more a question of if than when. Appreciate your help.
    Share this post

  8. #8
    Originally Posted by NasT65 Go to original post
    thanks again mutetus, apologies if i sounded pushy, it was more a question of if than when. Appreciate your help.
    Here is some info while you wait for the official breakdown:

    Firstly there is 'peak' and then the colour coded bars. Peak is the peak of a specific statistic in your track. So for example if the peak of visible lights is 8, this is the maximum amount of lights that can be seen active in your track. If the number is high, you should find the location where all these many lights can be seen and make changes if necessary.
    Next is the colour coded bar. Once it exceeds full bar and is red then you are pushing the engine's capabilities/recommended use for that specific statistic. The bar is not constant, it is based on real time, so if Dynamic objects bar is full, you are near too many physics-enabled objects, but if you move elsewhere without a ton of physics in play, the bar will go down.

    Everything else should be mostly self-explanatory, yet still one cannot be certain on what does what without seeing the source material, so best wait for the official tutorials.

    As mutetus said, for best results view the statistics overlay when doing a proper test run. No use paying attention to all statistics in the editor interface as some info will not be a true representation.
    Share this post

  9. #9
    NasT65's Avatar Senior Member
    Join Date
    Apr 2014
    Posts
    628
    Thanks ap!!
    Share this post

  10. #10
    Lukeyy19's Avatar Member
    Join Date
    Mar 2014
    Location
    UK
    Posts
    449
    Just a quick addition to the "peak" this is the most that the camera has seen during the time you've been in the editor, it is not necessarily accurate to what the peak will be during a play through of your track, especially if you have a zoomed in camera, while the editor cam may have seen a lot of the track in one go during editing giving you a high number for your "peak" a play through of the track may have a much lower peak.

    To get a more accurate reading, save and exit the editor, open it back up, load your track, bring up the stats and then test, without moving the camera, upon finishing the test, before returning to editing, the peak values will be a better representation of how your track will perform.
    Share this post