3 Commando Brigade

I've moved the posts, we are now in the public server feedback thread:)

v6 ready to go up on next restart. Changelog in mission thread.

However, Tuesday will see a new mission from Kryklin on the public server set in Chernarus.

Mission: Kryklin_DeathStalker_v7.Chernarus
Server Mod Line and Repo: unchanged

 @Cupcake: The FPS are obviously an issue but the impossibly hard south is by design. Don't go there if you have <1 mechanized troop.

Air units shouldn't be spawning anything in on the ground. It is one of the major causes of FPS loss if you have helicopters flying around the map spawning in enemies well away from the player infantry. It should be limited to ground units only, like it is in the majority of public server missions.

I dont know the setting used on the map but usually ALIVE is spawning everything on startup and will just start to display units if a player is in a certain range. You can set a seperate setting for air units, but this needs some fine tuning to not kill the performance.

On Previous mission I used 2000-3000m for ground units, depending on the general performance of the map. For air units, I usually did use 2000m.
 

good feedback...

We always set ALiVE to not spawn units from air traffic - causes serious stuttering and FPS lag for 99% of players.

HOWEVER UAV's WILL spawn Ai - as that's kind of the point - worth noting that as it could cause lag if abused.

We use a std spawn radii of 800m to 1500m (was 800 Max last time I checked) any more and it will again bring the 3CB interwebs to its knees. Server can handle it - but web traffic cannot.

Issue comes from the total area of spawn - two groups 5km apart - which isn't unusual - would generate more than 25km Squared of Spawned units at 2000m radii - That's definitely not cool

With an 800m spawn the total area is just over 4km squared, more manageable

We also use @alive's function to restrict the total number of AI physical spawns, regardless of how many are virtualised.

So it is not necessarily true to say that if every area on the map was occupied by a player/UAV that all AI would be spawned and that the server performance would suffer. This is in reference to military and civilian objective module placed units; CQB units do not have a spawn limit, but as they are handled by the headless client, it's not such an issue.

In the example of players in multiple heavy AO's, what does happen which can be a problem, is that as AI die they are replaced, up to the spawn limit, by virtualised units which suddenly pop into view, possibly at close range to players. However, for BEST server performance it is wise to stick with one AO.

Pilots need to be aware that on some missions there are also non-Alive controlled permanent anti-air units placed on the map in strategic locations to make their life more 'interesting'. These don't just pop up, but are always on duty looking for unwary 3CB pilots. Also, ON NO ACCOUNT should a pilot fly off the edges of the map. This, in my book, is cheating.

As SJ says, all of my missions have
- no spawn from air units
- 800m spawn distance
- between 30 and 50 group spawn limit, approximates to 200 to 400 units physically spawned at any one time
- virtualised AI, probably in the range 1000-2000 with about a 1000+ on reinforcement standby

Sorry! You can blame SJ, it was his idea.  :-)

mwah ha ha ha

It's a darn sight easier than when I built them - I had interlocking fields of fire - Cannon supported by man-pad emplacements...

Infantry had to do some serious recce before a fly-over was possible... Did slow the server down a bit though with 345 Shilka on the map....