When the code for a custom trigger volume is changed and a hot reload is preformed, the green bounds of the volume disappear and the volume can no longer be interacted with. The bounds do not reappear after restarting the project, causing the custom volume to be unusable and requires the instance of the volume to be replaced.
Workaround: Compiling with the project closed or switching to a level without the custom volume and then preforming the hot reload will allow the bounds to remain when the project/level is reloaded.
No - This behavior exists on 4.13.2 as well as 4.14.0
The green bounds of My Volume instance in the level will disappear. Switching level / restarting the project do not
Hot reload is preformed and custom trigger volume bounds remains usable.
Head over to the existing Questions & Answers thread and let us know what's up.