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

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.

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.

I've just confirmed that these levels won't crash when obtained from Marbleland, so this seems like the solution! So glad Marbleland's built in to PQ. I also noticed that clone marbles function properly instead of being suspended in mid-air, like in "Marble Runway", when played via Marbleland.

Thanks anyway for reading! Since fewer people probably know about the unmodified versions of the mission files (circa 2006-07), I suppose this could be marked as resolved.

Do share those mis files anyway, I was under the impression that it was the Marbleland version of these levels that were broken.

Five examples below. coolhouse.mis was modified a bit to remove some extraneous script objects with nothing but variables and definitions in them, but nothing improved or declined from that.

I just tried copying a mis file ("Turbo Race", another custom level that acts this way) as provided by the Marbleland site to play offline (in missions/custom) and it still crashes the game. So the issue may actually be playing these specific levels offline as opposed to playing via Community > Custom Levels.

This is rather strange, I'm unable to replicate the bug at all.
I have played the levels you provided by installing them offline and they all worked fine.
Even the console message of "object isn't properly out of the bins" error is not showing up.
Can you check if you face the issue on a freshly installed copy of PQ? I suspect that your existing copy of PQ may have become polluted due to manual installation of levels at any point of time.
The custom level ecosystem was quite a mess prior to Marbleland since there were loads of unique textures and dif files that shared the same file name, so it is possible that you may have replaced any one of the existing resources with a broken resource that may be causing the game to crash. The in-game Marbleland integration aims to mitigate this by not modifying the game's file system directly but instead have the game load the resources for a level from its special package format. (which is either downloaded onto memory, or saved to disk depending on the setting in Advanced Options)

You're right; a fresh copy of PQ allows levels such as "Cool House", "Maze of Houses" and "Battle of the Gems" to work offline, whether the mission files are from Marbleland, or unmodified from somewhere on the old MBP forums. Many thanks! Since we have two solutions I confirmed to work, I think this can be marked as resolved now