| Plugins available on Patreon | |
|---|---|
| Naturalis v1.4 alpha | Enhanced physics simulation and natural dynamic morphing for the body. |
| UXPlus v1.2 | Usability improvements focusing on the VAM user interface. |
| Body Weight v1.0 | More realistic body mass, adjustable by region. |
| Default Scene Manager v1.0 | Select scene to load on VAM start, and create scene load actions for Keybindings. |
| Continue Scene v1.0 | Auto-save the current scene to Continue.json when exiting VAM. |
| Performance Overlay v1.0 beta | Configurable overlay for monitoring frame rate, frame time and heap size memory. |
| VamBoop v1.0 | Boop the boob with your mouse pointer! |
If you like this plugin, consider giving it a thumbs up or posting a review. Thanks!
Performance Overlay
What it looks like when showing all data (min/max enabled, frame times enabled, heap size enabled):
The main purpose I built this was to accurately monitor the heap size and detect memory leaks. But you can just use it as a frame rate overlay as well. There's a lot of potential ways to extend this plugin with additional features - if there's something you think would be particularly useful, let me know!
You can configure how often the overlay updates, what data is shown, how many decimals are used, and you can also position the overlay in any corner of the screen with a customizable margin.
Frame rates and frame times can show either just the average value, or the average, min and max values. The values are calculated within an interval defined by the "Data buffer length" slider, so e.g. if that's 1 second, you always see the average, min and max values over the past second.
The overlay is also shown on the monitor view in VR (regardless of whether the Monitor is enabled!) - this can be toggled off.
About overhead
The overlay's own impact on heap size is not zero, but it's very minimal. Using default settings in an empty scene with no other plugins, you'll see the heap size build up slowly at a rate of about 0.1 MB per 15-20 seconds. I suspect most of this is due to VAM itself. It's impossible to get this down to zero, unfortunately. If you show more data, more decimal places and reduce update interval, heap size will build up more quickly. Regardless, it'll pale in comparison to actual memory leaks and to large bumps in memory use when adding/loading something, which is the purpose of showing the heap size in the overlay.
