Reply: Crashing error: "isn't properly out of the bins!" (according to console.log)

Hello, thanks for reporting this bug. We'll investigate the levels you mentioned.
That error message is usually when an object is unusually large or far away as compared to the rest of the objects. Though it shouldn't cause crashes, but will check anyways.

Some old-school MB custom levels crash the game upon loading them. I've had this happen with levels such as Battle of the Gems (1), Secret Room 1, 2 and 3, and Cool House. (You can find these on Marbleland.) I've updated PQ to the latest version and this still happens with those custom levels. In console.log, many lines read, "Error, a (StaticShape, InteriorInstance, Item, etc.) isn't properly out of the bins!" after the game crashes. I have no clue what that means.

I also tried removing some useless "new ScriptObject" codes from the .mis file for Cool House but that didn't prevent it from crashing either.

I can no longer use the original MBG to play those as MBG currently has this other, horrible glitch where my computer will be soft-locked for a long time if I exit the game or move the mouse cursor outside the game's window (probably due to a very recent update to Windows 11 software, on Windows 10 hardware), and I assume the unmodified MBG isn't supported at all by the PQ team, so I'd better focus on these individual levels.

Any idea what could be causing certain MBG custom levels to crash in PQ? If the levels mentioned above still work for anyone, I'll try obtaining them from Marbleland (as I currently use unmodified versions of the mission files from long ago), but I'll wait for replies first.