Repository navigation
V1.3 - Updates to FrameCount and CSVWriter + New AdditiveSceneManager
This release makes some important changes and a new addition to the pacakge: AdditiveSceneManager
Updates
- CSVWriter:
- Fixed a bug where, when running the writer multiple times with the
unix_mstoggled, multipleunix_mscolumns would be added every time. WriteLine()now doesn't need atrueargument pushed to writeunix_mseven whenunix_msis toggled; if no boolean is passed as an argument, it will use itsunix_msvariable to interpret whether the user wants to write unix timestamps to their csv file.
- Fixed a bug where, when running the writer multiple times with the
- FrameCount:
- You can write the frame count, FPS, or smoothed to FPS to any
TextMeshProUGUItextbox using the newtextboxesarray available in the inspector.
- You can write the frame count, FPS, or smoothed to FPS to any
New Addition: AdditiveSceneManager
Beginner implementations of Unity may load single scenes into a game. However, Unity has the ability to load in "additive" scenes where smaller scenes are stacked on top of already-running base scenes. The new AdditiveSceneManager is one attempt to make this functionality more transparent to game devs.
During runtime, if you are in the editor, you can debug how additive scenes load in via the Inspector; you can load and unload your additive scenes via some UI buttons we've added. Alternatively, if you are playing the game directly, you can instead call the component's public functions to control loading and unloading scenes. Feel free to check the README for a list of public functions and their parameters.