• Happy Holidays Guest!

    We want to announce that we will be working at reduced staffing for the holidays. Specifically Monday the 23rd until Jan 2nd.

    This will affect approval queue times and responses to support tickets. Please adjust your plans accordingly and enjoy yourselves this holiday season!

  • Hi Guest!

    Please be aware that we have released a critical security patch for VaM. We strongly recommend updating to version 1.22.0.7 using the VaM_Updater found in your installation folder.

    Details about the security patch can be found here.
FloatParamRandomizerEE

Plugins FloatParamRandomizerEE

Fixed subscene compatibility. Somehow the previous fixes did not work... I must've tested them back then. Anyway, should work now :)

Previously saved subscenes containing an earlier version won't magically work though, you need to save a new subscene with this version.
  • fix issue with the plugin not changing the value of target float param after loading a scene
  • fixed issue where the plugin didn't initialize correctly on a disabled atom
  • fix issue where selecting a target parameter would unnecessarily animate a transition from the previous parameter's value to the new parameter's value (or from 0 to parameter's value when selecting the first parameter after initializing)
  • receiver popup options are refreshed on opening the popup to prevent having to reselect the atom to see newly added storables (e.g. clothing storables, new plugins)
  • target popup options are refreshed on opening the popup to prevent having to reselect the receiver to see newly added targets (some plugins might register new float parameters dynamically rather than just during initialization)
  • minor UI tweaks
Fixed issue where the previous subscene compatibility fixes didn't work correctly with multiple subscenes having the same atom names, e.g. SubScene/InvisibleLight and SubScene#2/InvisibleLight. When in a SubScene, the plugin now correctly identifies the target atom that belongs to the same SubScene.

It might work incorrectly if the plugin targets an atom that is in a different SubScene than the plugin itself (or not part of a SubScene), but that's bad practice anyway - SubScenes are meant to be fully self-contained.
Fixed issue where the plugin didn't work when loading an older scene where the plugin's containing atom is part of a sub scene.
  • Subscene fix: the plugin now works correctly when saved to a Subscene and loading the Subscene file
  • Atom popup options are immediately updated when an atom is renamed
  • Lower value must be lower than upper value, upper value must be higher than lower value
  • The plugin is paused when the Atom or Receiver is changed and a new target float parameter is not yet selected
Just a tiny patch:
  • Enable Randomness now saves with the scene/preset and can be toggled with a trigger.
FloatParamRandomizerEE v1 is now out of early access!
Back
Top Bottom