Limo Estaĵa

From Valve Developer Community
< Eo
Jump to navigation Jump to search
English (en)Esperanto (eo)中文 (zh)Translate (Translate)
Info content.png
This page has not been fully translated.

You can help by finishing the translation.

Also, please make sure the article tries to comply with the alternate languages guide.

Formito el rezonoj de memorasigno, estas limigo al kvantito de estaĵoj(en) ke povate estrebliĝi de Source.

The combined size (in bytes) of a map's entity data should also be considered, even if the number of entities is within safe limits. Multaj kvantitoj da entdata povas noteble longtempe ŝutiĝi el servilo al malservilo. Tio eble kaŭzi erarhaltojn.

Tip.pngSugesto:Kiam kreas tre grandajn aŭ artecajn mapojn, rememoru ke pli estaĵoj ekzistos dum agtempo ol dum komputigaĵtempo. Aĵoj kvazaŭ vundiloj portis de ludantoj, elĵetoj kaj mortaj dikkorpoj, ĉiuj ankaŭ estas estaĵoj. Se vi vidi "no free edicts" erarojn vi bezonu komenci malkreigadon!

GoldSrc GoldSrc limoj

Etaĉo

This article or section is a stub. You can help by expanding it.

The default edict limit is 900, but this can be raised to 2048 by editing the mod's liblist.gam(en) to include edicts "2048".
This can safely be done for singleplayer mods, but should not be relied upon for multiplayer maps for existing games.[Klarigu]

In Sven Co-op Sven Co-op, the limit has been raised to 8192.

Source Source limoj

Maksimumo de 4096 estaĵoj povas ekzisti unuope. Tiu sumo disiĝos al du grupoj de 2048:

  1. Non-networked entities, which exist only on the client or server (e.g. death ragdolls on client, logicals(en) on server).
  2. Estaĵoj kun asociaj edict(en)-oj, kiuj povas transiri la dividon de kliento/servilo.
Faru: Check other Source engine games.


If the game tries to assign a 2049th edict it will exit with an error message, but if it tries to create a 2049th non-networked entity it will merely refuse and print a warning to the console. The logic behind this may be that an entity spawned dynamically (i.e. not present in the map) but not assigned an edict probably isn't too important.

The two entity lists are created by CBaseEntityList::CBaseEntityList() using NUM_ENT_ENTRIES and MAX_EDICTS. Neither of those values can be changed without breaking compatibility with the engine.

Tip.pngSugesto:Temporary entities(en) and static(en), sprite_clientside(en), or detail(en) props do not count toward either limit.
Tip.pngSugesto:If you're creating lots of individual objects all the time, consider rolling them all into a single manager entity.
Tip.pngSugesto:In-game, use console commands like report_entities and cl_showents to get an idea of how many entities are present at that current state.
Tip.pngSugesto:Prop entities that use a model with $collisionjoints will generate one phys_bone_follower for every convex piece of their collision model(en). These can quickly eat up the edict count! Enabling the "Disable Bone Followers" keyvalue on the prop will disable bone followers, although the prop will no longer have a functioning collision model, and the model will not be able to ragdoll(en).

VMF limoj

Hammer itself has no entity limit, but VBSP(en)'s is 8192 (16384 in Eksterterula Svarmo Eksterterula Svarmo, 2048 in Counter-Strike: Global Offensive Counter-Strike: Global Offensive).

Note.pngNoto:This is a soft limit; a modded VBSP(en) is capable of adding as many entities as memory allows.

This is double the combined total accepted by the engine, which may be because it at first treats internal entities(en) (such as prop_static and env_cubemap) like normal entities, or perhaps because it generates a lot of detail props(en).

VBSP also recommends an entdata size limit of 384KB, but this is in no way enforced.

Source 2 Source 2 limoj

In Source 2 Source 2, specifically S&box S&box, networked entity limit is 16384.

Ne ekzistas apere limo por mapkomputigaĵoj aŭ ĝi ligis retan estaĵan limon.

Vidu ankaŭ

Eksteraj ligiloj