Hey Cheesy, so I've been plagued by the nefarious "Object set to a Null Reference" error log spam with BL fora while now, though it's intermittent. Anyhow, I decided to finally try to track down the cause, poking around the JSON storables in my custom scene where this is happening, and managed to track down the actual cause of the bug.
It has to do with the "Fill Me Up" plugin specifically, and the thrust system. I've been experimenting with different setups, female + male atoms, female + dildos, etc... And the problem can crop up when you cross these two streams:
In the thrust system, you can flag the male + female thrusts to synch with each other. Which I enabled. All well and good.
The problem is that at some point, I deleted the male atom and started seeing how the triggers worked with a stock, native dildo atom. Here's where it comes apart. Since both the male and female thrust systems had "Synch Movement" toggled on, that bool got stored in the JSON. But now that the male is gone, and there's just a plain dildo in the scene (not even a Dildo language powered CUA dildo, just a basic one), you do a smart thing and hide the 'Synch Movement' toggle. However, the bool value still exists in the JSON. So when I go to use the dildo, I get the Object Set to a Null Reference error spam.
Anyhow, going into the JSON and setting this flag to false for both the male and female thrust storables fixed the error and everything works again. One of the side effects of this bug, is that because the toggle is hidden when in this mixed up state, there's no easy way to disable it, or even know that it's on, other than inspecting the JOSN, so the fix is very opaque to probably anyone who encounters it.
So, I guess if the condition occurs where you need to hide, or re-hide that toggle, you might want to reset its state to default, or at least check if there are any valid atoms in the scene for the synch movement function to use, even if it is hidden.
Regardless, thanks for making a terrific suite of plugins, my VaM experience would be much poorer with out them!
- Metix
EDIT - So the problem is actually a bit more pervasive than what I described. Somehow the Synch On toggle keeps turning back on, even after clearing it out of the JSON. I noticed that the Dildo atom name is being stored in the Speak to Me plugin, perhaps that's repopulating it somehow?