With a Camera IO set to a Camera Volume, using the Camera Volume as an output for a Counter Module (and possible other items as well) breaks the original Camera IO object and requires you to stash it and place a new one to restore functionality.
Steps to Reproduce
Place a Camera IO and a Camera Volume.
Edit the Camera IO and set its Camera to the Camera Volume.
Walk into the camera volume, and notice that it works when you walk into it.
Walk back out of the volume.
Place a Counter Module and set one of its outputs to the Camera Volume.
Walk into the volume again.
What I expected to happen
The Camera IO should still function - i.e. your camera should still change to it when you walk into the Camera Volume.
What happened
Your camera remains in first person.
Notes / Media
This bug is minor but makes working with camera IO for a project I’m doing annoying, with the only workaround being to wait until after a counter is set up to place and hook up the camera IO object, when I’d prefer to do it the other way around.
You’re connecting a non-Persistent Output to a Persistent Input which is breaking it (Camera volumes are only allowed to have one Persistent camera so it’s likely just disconnecting the camera).
If you want to control the camera using a Counter, either connect it to Activate / Deactivate on the Volume or use EnterCamera on the Camera.
You really shouldn’t be able to make hybrid connections like this, but I made a band-aid fix by just moving the Persistent connection to the last spot on the list so it isn’t the default thing your glove chooses.
I’m not using the glove at all though, I’m just right clicking → Edit. I’m also not putting additional cameras onto the volume, just one per.
I don’t think I am actually connecting a non-Persistent Output to a Persistent Input - the Camera IO’s only output (“Camera” under the connections tab) is set to the volume, and is the only Persistent connection in the mix. I can share some screenshots of the setup later if it would be helpful.