I had this issue like many others, but I finally had an epiphany and finally figured out when it happens for me. I don't know why, but I can make it happen and avoid it 100% of the time now.

So this might be important information, but I have:

• 1.0 Base stations
• They are connected by cable and thus are in A/B mode
• I have G2 Reverb
• I have Vive controllers, Index controllers and Vive Trackers. The device doesn't seem to matter.

The glitch happens whenever the FIRST tracking device (Vive/Index Controllers or Vive Trackers) is being detected by one of the base stations. Whichever the base station detects it first, that will determine if everything will be loaded in correctly and if the devices ( chaperone?) are loaded in correctly.

In my specific case, if 1.0 Base Station [A] detects my device first, everything loads in correctly (and will be maintained as long as a device is in the tracking range).

If 1.0 Base Station [B] detects a device first, the devices will spawn in wrong location and rotation. (And it appears absolutely no chaperone gets loaded in).

Additionally, everything is maintained as long as the lighthouse/SteamVR can detect a device, but if you move everything out of the detection range, then move a device back in, then we're back to square 1; it'll depend which base station detects your device first.

The same goes for turning all devices off and turning 1 back on again, the first base station that detects the device will make sure it'll be loaded correctly or incorrectly.

Finally, I'm not sure if 'universes' plays a role here, I deleted all my universes, except for 1 in chaperone_info.vrchap and it had no effect.

Edit 2: So my hypothesis is, 1 of the base station lighthouse will become the 'main' one being used for the play space and all the devices. And it'll be the main reference point. But it seems the HMD is only calibrated to one of the two base station (basically when you calibrate it at THAT point in time, whichever of the two was the 'main' back then).

Because the HMD is a foreign entity technically, and calibrated to 1 basestation, when the wrong base station becomes the main, 'it' doesn't take the HMD's the new position and rotation into account. Here's a visualization of what I think is happening, when the 'main' base station switches from one to another. https://youtu.be/33CfkRzThCk