My Companion Cubes Have Betrayed My Graphics Card
Part of the intro includes a room full of many companion cubes, so I did that and made them all prop_static.
When I compiled, it said that the cube model couldn't be used as static so I made them all prop_physics.
Big mistake...when I go in game, the game freezes every microsecond. It took my game literally two minutes to get up the elevator shaft.
I know that this is because of the huge amount of prop_physics because I have gotten board before and spawned in a huge amount of companion cubes before my game froze [long story] but anyways, is there any way to keep this huge amount of lag from happening?
TeamSpen210 wrote:
Make sure they are sitting on top of each other, then check the flag "motion disabled". This'll stop them from moving or doing physics calculations. If the player can interact with the room in any way, set the flag "start asleep" instead. This does the same thing until something else interacts with a cube.
However, if the player interacts with all the cubes, the same problem would occur.
Use a bunch of prop_dynamic_overrides.
You might need to polish the shape a bit to avoid a too-square shape and to make it look more close to the prop_weight_cube shape.
Another possibility could be to decompile the cube model and add the $propstatic to the .QC file, then compile again, then use it as a prop_static. I bet it works, but I haven't tried, someone correct me if I'm wrong.
Ultiman9711 wrote:
Make the companion cubes prop_static_override.
FelixGriffin wrote:
None of these will work if a physics object touches the cubes. There is no prop_static_override and I think cubes are physics-only.Use a bunch of prop_dynamic_overrides.
Oh wow! I must've been half asleep when I wrote, "prop_STATIC_override." Oops. I meant dynamic_override!
@Felix: Thanks, that's fine because the player isn't interacting with them at all. I mean, what kind of map would it be if the player got a room full of companion cubes, other than just a tantalizing glimpse at one?