feat(net/rdr3): physical player extension

[Ehbw]

Goal of this PR

Introduce support for RedM to support up 128 physical players inside a players scope. From the RAGE limit of 32, this PR is still very experimental and still needs extra work done, but is in a state where it can be tested on a feature branch with 32+ clients.

How is this PR achieving the goal

(still work in progress, will provide detailed explanation when finished)

This PR applies to the following area(s)

RedM

Successfully tested on

Game builds: 1491.50

Platforms: Windows, Linux

Checklist

• [ ] Code compiles and has been tested successfully.
• [x] Code explains itself well and/or is documented.
• [ ] My commit message explains what the changes do and what they are for.
• [x] No extra compilation warnings are added by these changes.

Fixes issues

closes #2932

[outsider31000]

requesting a feature branch to the team when possible please.

[Z-eus]

N1

[rsrspokerakisrsrs-ux]

do we have any news about fixing the problem ??/

[Ehbw]

do we have any news about fixing the problem ??/

The memory corruption issue (The one I'm assuming you're referring to) is still being worked on and should have a fix for that soon.

[Gregorsaur]

Just adding my comment as support, to say how HUGE this feature would be for RedM. Please the gods that be, make this happen.

[ExerGGs]

Adding my comment of support. God bless you guys #RedM for life

[Gregorsaur]

Progress seems to be going well

[gurkansahinn]

Hello, and thanks again for the work on this PR.

After reading through the discussion, I understand that the extended player support breaks assumptions in the current voice subsystem (32-sized arrays, stack usage, migration behavior), which is why voice had to be disabled.

For RedM communities that run text-roleplay or already rely on external voice, this isn’t really an issue. The benefits of stable replication with more than 32 players (fewer ghost entities, no mid-session index reuse, improved scalability) would be substantial.

If this can be tested on real servers, even behind a feature flag, in a state where it can be tested, that might help gather data faster than waiting for a full review cycle.

Something like:

sv_rdr3ExtendedPlayers 1

I’m mainly asking because I’d genuinely like to help test or contribute where possible. Understanding the current stance and any specific blockers would be helpful.

Thanks again for pushing this forward.

@Ehbw

[Ehbw]

Hello, and thanks again for the work on this PR.

After reading through the discussion, I understand that the extended player support breaks assumptions in the current voice subsystem (32-sized arrays, stack usage, migration behavior), which is why voice had to be disabled.

For RedM communities that run text-roleplay or already rely on external voice, this isn’t really an issue. The benefits of stable replication with more than 32 players (fewer ghost entities, no mid-session index reuse, improved scalability) would be substantial.

If this can be tested on real servers, even behind a feature flag, in a state where it can be tested, that might help gather data faster than waiting for a full review cycle.

Something like:

sv_rdr3ExtendedPlayers 1

I’m mainly asking because I’d genuinely like to help test or contribute where possible. Understanding the current stance and any specific blockers would be helpful.

Thanks again for pushing this forward.

@Ehbw

Disabling voice was an experimental change and will be re-enabled soon. As for testing there is a decent size testing group organised for testing new changes when I make them (although due to time constraints + not having any new changes pushed to be tested there hasn't been a test in a few weeks).