Plugins VAMAtmosphere

Occlusion

• Added support of all types of Image Panels (ImagePanel, ImagePanelTransparent... etc) for @VAMFantasy (it is a nice way to make TVs with a proper occlusion!)

Thunder

• Fixed a log I forgot :x

Big update for people who like to listen!

Note: version 1.13 has never been uploaded. Don't look for it. 1.14 contains all the changes.

1.14
===================================

Thunder

• Fixed an error that was triggered on enabling the plugin.
• Fixed a bug preventing the thunder loop to resume if the atom was put in a off state. (it is now possible to simply on/off the atom to control its activation)
• Fixed misc conditions to prevent errors
• Cleared audio clip when disabling to avoid playback when enabling

Neighbors

• Added a bunch of new sex sounds
• Fixed a bug preventing the neighbor loop to resume if the atom was put in a off state. (it is now possible to simply on/off the atom to control its activation)
• Cleared audio clip when disabling to avoid playback when enabling

1.13
===================================

ReverbZone

• Fixed waiting time (pushed to 36000 like the other plugins)

Neighbors

• Added a bunch of new sex sounds
• Fixed volume not restoring/saving properly
• Fixed volume not initializing properly
• Optimized playback: sound not playing if volume is at zero

Thunder

• Fixed the missing timeout update in the thunder plugin

Neighbors (thank you for the report @VAMFantasy)

• Fixed a missing check for sex only option which would result in a critical error crashing the plugin
• Fixed a missing check during initialization which would result in a critical error crashing the plugin

All VAMAtmosphere plugins

• Updated the "timeout" period to 36000 tries (which is 10minutes at 60fps). It will help people with less powerful PCs to not have the plugin timeout (and fail to initialize) during the loading process of the scene.

• Thanks to @VamMoose , fixed a couple of bugs for VAMA Atmosphere occuring if the scene had a lot of assets, stalled during loading, or if the async loading process was too long. Thank you buddy!

• Thanks to my fellow @Spacedog who does not do anything like anybody else (love ya ), the occlusion system on VAMA Ambience now keeps the Ambience Low Pass settings as the default value before occlusion. In simpler terms it means you can muffle a sound by default, and enable the occlusion system on top of it.
• Updated the help section to give some more informations for the multiple settings
• Fixed a couple of typos and obsolete help sections.
• Added presets to use the different components of VAMAtmosphere with ease:
  
  Add a Custom Unity Asset, go to Preset tab then select existing...
  
  
  
  
  Select vamatmosphere .var in the left column then your plugin in the list:
  
  
  
  
  VAMA Occlusion is not included since it needs to be put on an AudioSource or a Person, no preset is needed for that.
  
  All plugins are configured with their default state, so for some of them you would need to finish your configuration (for instance, you need to select your light for the Thunder, or place your spots with the Neighbors simulator).

• Added the occlusion plugin (see the documentation for more information)
• Fixed a critical bug where VAMA Ambiences could make VaM crash to desktop after several scene loads or when using the reload button.
• Removed demos from the package, moved them to HZMDemos ( a new "desktop compliant" demo is available for the occlusion )

• Added new amb_city_urban ( Urban city ambience )
• Added new amb_scifi_03 ( Exterior scifi ambience, for the upcoming The Hideout enviro )
• Added new amb_vent_01 ( Interior vent ambience, for the upcoming The Hideout enviro )

• Added new sex samples to the third neighbor.
• Update the mix of a few samples
• Added a new option that will allow you to only play sex sounds with the neighbor simulator (perfect to simulate a whorehouse!)

• Added 4 new shower ambiences. Each shower sounds are different with subtle variations on what type of surface or the distance of the audio recording.
• Tweaked scripts for @Spacedog and @Acid Bubbles who pressured me like crazy to remove the init messages ( It is true ! They even hired the VaM Mafia to break my knees ! ). Initialization messages are gone... Acid raised a valid point saying that if every plugin was doing that, it would be a constant log flood.