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 ?
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.
Here is some info while you wait for the official breakdown:Originally Posted by NasT65 Go to original post
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.
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.