Windows Pro 8.1
32 GIG DDR3 800mhz
Intel Core i7 3820
Graphics: Radeon HD 7970
My citizens were doing a bit of running around collecting resources and food when the system crashed to desktop without messages. This has happened several times.
I have been seeing this error often in the log as well.
Just some info:
When this happens it should be automatically sending Radiant the crash dump file.
In a recent stream it was stated that they are looking at these crash dumps to find the bugs responsible.
I’ve found out that creating 700 entities with 900 model variants each will pretty reliably reproduce this error. Then again, that’s not exactly a “common thing to do”.
I think they’re all 1x1x1 differently-coloured voxels is all (“all”… hah…), ie for use in fancy coloured structures and the like (been talking to @RepeatPan via Steam occasionally as his sounding board ).
Paging @Sdee, I think it’s important the guys know that 630k entities/variants is too much for the game ATM. Optimisation fun ahead …
To create custom voxel geometry, it’s much more efficient to use _radiant.client.create_voxel_node on the client. See the ConstructionDataRenderer class for an example. It’s used to create custom voxel geometry from the region_collision_shape of an entity and is what we use for drawing buildings. You can get one created by creating your own component and adding your renderer class to the “component_renderers” key in the manifest (again, see how construction_data works).
. Could use your PC’s specs, and exactly what happened when the crash occurred.
).
…