Level Design Performance Limit of ROStaticMeshDestructibles

[Nightingale]

In the TWI Wiki, it says that going over 500 ROStaticMeshDestructibles in a single map is inadvisable. Could a dev please elaborate on exactly how this number was derived? I ask because I noticed that Red October Factory has something like 670 destructibles in it, so it seems to me like this number is sort of flexible. If I wished to make a map with, say, 1000 destructibles in it, what kind of sacrifices in other aspects would I have to make in order to compensate for the performance penalty?

 

[-=}WoLvErInE{=-]

I can't recall anyone saying anything about the max per map, but if my memory serves me right, I remember someone from TWI telling me not to use more than 300 or 400 per actor. I want to say 400.

 

[PsychoPigeon]

It's 300 per replica actor, I don't know of an actual destructible limit per map though

 

[Nightingale]

Hmm, if that's the case I won't pay too much heed to this hard limit of 500 then. I am certainly aware of the 300 per replication actor thing, but I won't need to worry about that yet as it's only a server optimization feature.

If someone from TWI could comment on this it would be very helpful. I'm still not really sure how expensive destructibles are, relative to simple static meshes.

 

[danh]

You have to calculate shadow for each destruction. Say you have 10000 actors, then you have to calculate shadow for each one before and after destruction which increases the file size of your map.

 

[Nightingale]

Ah, so destructibles only add filesize? They don't lower FPS any more than static meshes do?

 

[Zetsumei]

I believe they do not necessarily effect client fps that much, but they do have an effect on server fps. As in that every tick they must check if an object has been destroyed or not. (could be wrong here).