OneSync ‘Infinity’: how to use it – FiveM Announcements

Some time in the past, the FiveM consumer/server obtained help for ‘Infinity’ mode for OneSync, which mixes participant entity culling, participant culling and (hopefully momentary) removing of automatically-generated inhabitants.

This publish seeks to rapidly element some commonly-asked questions.

• A mode permitting (as much as) 1024 gamers at the moment. Now we have solely examined 600-ish in load exams since we couldn’t get any extra gamers, but it surely held up fairly properly ultimately (on a server with minimal assets)
• To perform this, it makes use of the next technological adjustments:
  • Removing of inhabitants to avoid wasting object ID pool area. You may nonetheless create (some) synced/networked peds utilizing script, nonetheless.
  • Participant ped/car culling. No entities will likely be created on purchasers outdoors a ‘focus zone’, which presently is hardcoded to 300 models round a participant. We’re nonetheless searching for a greater algorithm.
  • Participant culling. No gamers will likely be created/deleted domestically outdoors of the main focus zone too. Because of this all participant iteration should occur server-side.
• It additionally has a bit higher efficiency than ‘plain’ OneSync at the moment as a consequence of participant ped culling, and works across the so-called ‘head mix bug’.

• A brand new frequent crash: kilo-xray-tango. It’s fairly uncommon relying on how densely packed gamers are, determining a constant repro could be very welcomed!
• Computerized inhabitants is disabled as in any other case you’d run out of object IDs round 200-300 gamers. (a world most of 8192 spawned entities exists at the moment)
• You want a Platinum subscription, or a ‘manually granted Infinity’ group membership at the moment. As soon as it’s developed additional, we might contemplate permitting tiered participant caps for decrease Patreon subscriber tiers.
• Quite a lot of scripts will want altering. Admin menus, ‘teleport to participant’ UI and scoreboards undoubtedly received’t work instantly. Loops are nonetheless as much as 256 max (or utilizing GET_ACTIVE_PLAYERS), however will solely discover close by gamers.

• Add +set onesync on to your server startup command line – it received’t work should you add it within the .cfg.
• Make certain onesync_enabled and sv_maxclients are set appropriately.
• Repair scripts that find yourself displaying incomplete lists.

Everybody’s instanced, I solely see myself?

That’s imagined to occur. Get nearer to different gamers, and repair your participant itemizing scripts.

How do I get all gamers on the consumer?

Not at the moment, we’re nonetheless investigating environment friendly methods to ship this knowledge alongside. Presently, it’s best to use server/latent server occasions for this.

We anticipate individuals to launch a couple of useful helpers within the #growth:releases part for this.

Why is X built-in function displaying an incomplete record?

Report it! #general-discussion:1s-reports

Why is that this paid?

It simply is. This may change after the Commerce launch.

?

Sure, !