[SoulWeaver16]

A small mistake, oh, and with 20 bots, there is still an overflow, but I suppose that more cannot be optimized, unless it is loaded by proximity, because when the round starts, it renders both teams even if it is not visible

[EFFx]

Which mistake are you talking about? The weapon icon?

About the proximity idea for rendering, it can be added as another feature to help with the overflow when there are loads of players as well. Currently it has the loop splitter but it happens when the server has more than 20 players (defined as MIN_LOOP_NUMBER).

Instead of the proximity, is_visible or is_in_viewcone should be enough, avoids issues with players in a distance longer than the proximity, but visible.

[SoulWeaver16]

Originally Posted by EFFx Which mistake are you talking about? The weapon icon? About the proximity idea for rendering, it can be added as another feature to help with the overflow when there are loads of players as well. Currently it has the loop splitter but it happens when the server has more than 20 players (defined as MIN_LOOP_NUMBER). Instead of the proximity, is_visible or is_in_viewcone should be enough, avoids issues with players in a distance longer than the proximity, but visible.

Yes, error in the icon said
And that plugin worked much better, since there are exceptional cases that there is a spam message from overflow
And don't let it look laggy in the first person over your head

[EFFx]

So it is better than before? I wasn't able to test since I wasn't getting any overflow whatsoever. I will take a look about the icon issue.

[SoulWeaver16]

Originally Posted by EFFx So it is better than before? I wasn't able to test since I wasn't getting any overflow whatsoever. I will take a look about the icon issue.

It certainly avoids the overflow at the beginning of the round or during the whole game, but in the spectator, if you change players, even though you don't see the icons, it will stop the server for 0.1 seconds with 25 overflow messages, but it is quickly solved without problems

[EFFx]

Skipping spectators should be the quickest way. It happens as soon as you change players? Like everytime? First person view only or any camera mode it happens?

[SoulWeaver16]

Originally Posted by EFFx Skipping spectators should be the quickest way. It happens as soon as you change players? Like everytime? First person view only or any camera mode it happens?

I think it would be better if I show you on video, wait for me to record it and upload it
https://youtu.be/sKYHQFIuRlM

[georgik57]

Optimization ideas regarding the overflow(checked code a bit):

1. Get the team with the most players at round start and only create those much entities. Since you're already using AddToFullPack, do everything you did in entity creation there, based on teams. Store entity IDs in a variable instead of checking for class name in ATFP. This will lower the number of entities by half at best.

2. Merge cash and 10000 sprites together to get rid of 1 more entity. You can do the same with arrow and 100 by adding double the number frames: one with the arrow and one without. This will prevent from coloring them differently though so only do it if you think it's worth it.

3. Use pev_vuser for storing colors(although i didn't quite see the point of changing them after creation)

[EFFx]

I will put some effort into the first two suggestions. About the third, does it actually make any difference?
Also, the purpose was to make it change instantly, instead of waiting for a new round, some servers doesn't have rounds.

[deprale]

Originally Posted by EFFx Also, the purpose was to make it change instantly, instead of waiting for a new round, some servers doesn't have rounds.

Make it a cvar