• When using the experimental 'Render'-toggle (Control + R) in scenes with VAMStory- or VAMCUI-UI by hazmhox this plugin will now detect them on each atom and they will stay visible. (show-filter is enabled by default).
  • known bug:
    The combined use of some UI-plugins and the experimental 'Render'-toggle can cause the standard VAM-UI to partially disappear. Press the 'U'-key twice to restore it.
Changes:
(to previous "Version 5 experimental 2" only)
  • CUAs that have a linked Rigidbody will now be excluded for the 'Render'-toggle. So CUA hair, wings or anything linked to a person stays visible.
  • Added missing "UISlider" to the list of atom types to exclude by default.
  • The 'Render'-toggle now generates a filter for each atom on the right side of the UI. Use them to manually toggle atom visibility. This filter list will not stay in sync if you add or remove atoms to the scene. For now this can only be refreshed by reloading the plugin. None of the filters or the 'Render'-toggle state is stored! This is intentional because I do not want to see users creating scenes where atoms are hidden by default. I believe sooner or later scene could and up on the hub and this would cause confusion for users who are not familiar with plugin.
  • Custom UIs that are being generated/rendered at runtime in 3D space (VAMStory) cannot be filtered by atom type. However it's now possible to toggle the filter for whatever atom holds the UI now.
  • There was an error on my bank account showing me that I am very poor. In an attempt to fix this problem I've added a proper Patreon button.

The 'Render'-toggle will stay marked as experimental. It's a very hackish feature that will never work perfectly. But it is still better than going over every atom manually to set up a scene for passthrough.

Known bug:
This happens for multiple copies of the same CUA in the scene:
If the filter is set to 'show' and the 'Render'-toggle gets disabled they will not stay visible as intended. In that case re-toggle the filter for this CUA and it will show up again. I suspect this happens because only one is the main-object and the other ones are clones / instances internally to save resources/memory.
  • Merged session- and scene-plugin versions.
  • Fixed logic related to enabled / disabled state. The UI is no longer accessible in disabled state. Important for creators: In disabled state it's no longer possible to set a color or toggle the skybox with scene triggers or the UI.
  • Fixed error for scenes without WindowCamera atom
  • Fixed OnEnable()-NullReferenceException appearing in VAMs logfile
  • A warning will now show if multiple CameraBackgroundColor plugins where loaded (excludes check for old standalone Session Plugin version)
The skybox will now be disabled automatically by default. This should prevent users from falling into the 'skybox pitfall' - leaving them confused and thinking that this Plugin does not work. I think in this case it is safe to assume we want it disabled to prevent it from blocking the view on the background color.
  • Added 'Show Skybox' Toggle [default=off]
Creators: In cases where a scene does use the Plugin and you want to keep the Skybox on you can either save the scene with the 'Show Skybox'-toggle on or simply keep using Version 2.
  • Added the color to the Screenshot-, Thumbnail- and Window-Camera (M-key).
  • Added functions to make the Enable / Disable Plugin checkbox work.
Back
Top Bottom