Summary
If you have a hole (“hole 1”) setup so that the pocket piece is inside of a camera volume, it will not play the minigolf intro for the next hole (“hole 2.”) Instead, it will spin around the flag of hole 1, as the intro for hole 2.
Steps to Reproduce
- Make a minigolf hole (just a start and pocket and some way to get there.)
- Put camera volume encompassing the general area around the flag, including coverage of the whole inside pocket.
- Attach cam-vol to a camera.
- Make a second hole (start and pocket), set up an intro camera for that hole, assign it to that hole.
- Launch gameworld, play through the first hole.
- When second intro is supposed to start, notice that instead of playing, it spins around hole 1’s flag, and abruptly starts hole 2 from there.
What I expected to happen
To exit the camera-volume camera after hole 1 fully ends, and enter hole 2’s minigolf intro camera when that should start.
However, I do I expect it to, like current, stay in the camera if you personally have pocketed but not everyone is done with the level yet.
What happened
No introduction camera for hole 2 is possible without shenanigans, when one would be ending in a camera volume.
Notes
I think this could be related to minigolf balls not actually “despawning” in hole 1’s pocket, as far as I am aware they sit there until “the moment you can start putting” in hole 2.
Intro cameras seem to be a weird setup where you are actually still sort of, functionally, the previous hole. I assume the intention of this is to make the intro look better with no golf ball mash sitting on the start pad.
If one fixes this by making it so golf balls are “marked” to not be affected by camera volumes on pocket, that’s probably workable as long as it doesn’t conflict with “onpocket” IO directing back to the exact same camera.
Otherwise I feel the fix could be moreso pointed at making sure the minigolf intro camera always has priority.