Project Reality Forums

Alright so, I'm close to finishing my map Prizrak, but have decided to put it on hold for a while, Now I'm working on an urban map and making it as detailed and as realistic as I can, so far I've finished alot on it.

But before doing that I wanted to make sure that it won't have any negative effects, or atleast if it did, it wouldn't be so bad.

1. Does a higher number of static objects affect performance?

2. Does a higher number dynamic or destroyable objects affect performance?

3. What kind of objects increase the risk of a server crash?

4. What is the maximum number of statics you can place on a map.

5. What are "networkables"?

6. What are the things that could lower performance on a map.

I just want to make my map as detailed as I can by adding stuff such as furniture to each and every room and such, adding debris, you know.. all the small details that make the map look more real and each area unique, making the map enjoyable, realistic and giving the players the best performance they can get on it.

1. yes
2. yes
3. destroyables
4. there is no maximum
5. everything that can move, get destroyed or change its status is a networkable (players, vehicles, destroyable objects, etc)
6. overgrowth, many different pallettextures


thats what i can think about atm

Understood, thanks alot.

tbh I wouldn't start another map before finishing another map, epically since you dont have that much experience, all new mappers always drastically underestimate how much work is left to finish a map once they "think its near to being finished". If you really want your map to get finished, the sooner you finish it the better.

Anyways as for your points.

1. Yes, the more objects have have to be "drawn" can drastically affect performance. Its easier for the CPU/GPU to process one huge static than lots and lots of small statics making up the same size of object. So avoid using the "Afghan" statics that have each wall in there own bit etc and building "unique statics" with lots of blocks of concrete stacked up together etc. You will also find lots of small objects are much harder to lightmap. Try to following the motto "less is more" in a lot of cases, trying to use as few objects as possible to archive what you want.

2. Yes, "destroyable objects" (including dest objects that have been made into "non-destroyable" via code) really class as two statics in one, since you have two models for them, the complete model (before its destroyed) and the wreck model which is shown once its been destroyed (although some dest objects like explosive barrels dont have a wreck model and vanish from the map after they are destroyed). Both the complete and wreck models need there own lightmaps, so a destroyable object needs twice as much lightmap space as a normal static of the same size and complication, which also isn't good for performance. All in all, try and only use destroyable objects where your going to have a real gameplay advantage from them.

3. & 5. you can only have up to 1024 networkables on a map before the server will crash (although exceeding 1024 networkables is fine for local servers, but not good if you want to play the map online ). Networkables are basically things the server needs to keep track of, vehicles, players, destroyable objects etc. We advise you keep your destroyable/dynamic objects below 350 to leave room for all the other networkables. The lower your networkables, the better.

4. No limit, but keep note of point 1.

6. Use as few "types" of static as possible. For example, dont start mixing Middle-East statics with Russian statics, as they both use there own unique texture pallets and its a really bad move to start mixing the two as then the player needs to load many more textures into his ram and also the CPU needs to process many more draw calls. Try and use as few unique objects and different type of objects as possible, only using a type of object if your going to be using that type of object a lot and its necessary for the map. Also like I said in point 1, dont use lots of little statics to make big statics, one big unique object is far better than lots of small tiny objects making up the same thing. Also only really place down objects that are going to mean something to the map and or its gameplay, dont place down things just because they look cool. Think about what there purpose is and are they really worth having etc. Try and just keep your map as simple as possible in terms of the statics you use and how you use them and always think is there a better way I could be doing this?

Alright, thanks alot for the very helpful and detailed answer Rhino.

I'll follow your advice and finish my other map as well.
I'm just having a few problems atm and I'll ask on how to fix those on my map thread.