26 replies to this topic

[TheMeddlingMage]

The glitch must be caused by something on the owner's PC, seeing as it occurs on different times and different places for everyone. The real problem here is tracking down the evildoer on the system.

[fun]

Okay I think I should have posted this is along time ago so here I go , now noticing how this glitch seems to pop up out of the blue I figured that it must primarily be caused from monster's Picking up a raider so i disabled the monster's ability to pick up and threw this was in Baz's Mod 1.5 so then i tried erode works again but I suffered the same glitch only this time it was worse , The monster's came out and they disappeared to my raider were stuck in running a mode too I was like OMG so used the debug key E on a wall to spawn a Monster and it vanished into thin air it seems this glitch can be more destructive then we thought . So finally i disabled the Monster's ability to scare hoping that would fix it well it did not same glitch happened so it seems it must be caused from something else :facepalm: but that could be a clue to this

[TGP1994]

Just wanted to contribute my two cents to this topic;

I, for the first time ever, experienced this exact glitch. I was playing "Don't Panic!" in Baz's mod, and after pausing the game for about an hour and coming back to it, I noticed that all of my rock raiders had disappeared, save for one that was driving a transport truck. The transport truck had instead disappeared, but the driver was left in some strange falling animation in the same position that the truck used to be in before it disappeared.

I could click on the driver (and end up selecting the truck). When I tried to go into first person view, I received the well known view of "rock raider hell", with the camera bugging out. Upon leaving first or second person view, my camera would be placed at one of the corners of the level.

I had gotten pretty far into this level, too. Darn.

[Extreme110]

TGP1994, on 19 May 2012 - 12:53 AM, said:

Just wanted to contribute my two cents to this topic;

I, for the first time ever, experienced this exact glitch. I was playing "Don't Panic!" in Baz's mod, and after pausing the game for about an hour and coming back to it, I noticed that all of my rock raiders had disappeared, save for one that was driving a transport truck. The transport truck had instead disappeared, but the driver was left in some strange falling animation in the same position that the truck used to be in before it disappeared.

I could click on the driver (and end up selecting the truck). When I tried to go into first person view, I received the well known view of "rock raider hell", with the camera bugging out. Upon leaving first or second person view, my camera would be placed at one of the corners of the level.

I had gotten pretty far into this level, too. Darn.

How much RAM do you have, and what version of Baz's mod? Sounds like you simply had too much going on in the level, so it attempted to flush itself.

[TGP1994]

I had 1024MB of ram allocated to the VM that was running lego rock raiders, and version 1.5 of Baz's mod. Hmm, too much going on? I just played it again, and I was able to complete the level without problems, with even more going on, I think.

[Cirevam]

How much was allocated to LRR? There's a line in the Lego.CFG file that determines how much memory the game is allowed to use. It's TextureUsage, and by default it allocates 32 MB. If you turn it up you can teleport in more raiders and the game runs more smoothly overall. In fact, I was playing a mostly vanilla setup last night and my raiders started to show signs of idleness syndrome. That might have had to do with how I didn't change TextureUsage for that setup since it rarely ever happens in my modded games.

[Phoenyx]

Reading through this thread, the whole issue might actually be an unintended effect of an intended part of the game's code, where the game might despawn entities (read: Raiders, Monsters, Vehicles, Resource Objects, maybe Buildings?) if the RAM allocation can't handle the amount of onscreen objects. I've seen other games do similar things, though I myself haven't encountered this Glitch/Bug/Issue.