Wrong hair / appearance when in proximity of a lot of players

[dGxxxx]

Description of the problem

the issue is that when there are around 100 players at the same position, things start going a bit wrong. the hair color keep resetting to pink / green, the player face (ageing, head blend, etc) started reseting to the default one, etc.

all of these are occuring with 0 mods and all the player stuff were set on server-side.

Let's assume the red circle is the place where the 100 players are, and the blue circle as the max steaming range. Usually the hair goes pink when the users are going from the red circle to the blue one.

Also worth mentioning is that the streaming range is the default value from stream.toml, and the max value of entities streamed are also the default one (128 peds). Also there were like ~300 players at the same spot, but due to the streaming settings, there were only 128 shown on the player screen.

From my testing it is reproducible even with 3 players, but not as common. The key to reproducing it is to be at the limit of the streaming range, and thats when things start going wrong.

Reproduction steps

Mentioned above.

Expected behaviour

There should be no problems with the appearance.

Additional context

No response

Operating system

Windows / Linux

Version

From september 2024 - till current16.3.2

Crashdump ID

No response

Confirmation of issue's presence

• By submitting this ticket, I affirm that I have verified the presence of this issue on the latest RC (Release Candidate) version available at the time of writing this ticket.

[GVMP]

It's a common issue with RAGE so alt:V limited it to a max. range without letting the client crash.

Afaik someone already started working on it years ago and use isPointOnScreen to set the appearance. But the transition was garbage and integrate it into existing systems is kinda impossible without breaking other neccessary systems. (Client stability > Client functionality)

Expect that nothing will change here until R* increases game engine limits and alt:V adapt to it.

[dGxxxx]

It's a common issue with RAGE so alt:V limited it to a max. range without letting the client crash.

Afaik someone already started working on it years ago and use isPointOnScreen to set the appearance. But the transition was garbage and integrate it into existing systems is kinda impossible without breaking other neccessary systems. (Client stability > Client functionality)

I'm not fully sure, but didnt the other platforms somehow fix this issue? I think that the last time I checked out one of them, the issue didnt seem to be present there. However, again, I'm not fully sure about this.

But from a point of view, some platforms even managed to play around a bit with more complex stuff about the engine via RE, so not sure but I think theoretically it could be possible for them to somehow solve the issue.

[GVMP]

It's possible, for sure. Since the "big leak" everything is way more clear now and you don't need to spent weeks to decrypt memory patterns anymore.

Creating a working feature like this shouldn't take that much time for someone who knows what he's doing, but you have to test it if any other problems may occur due this feature.
Changes to the client stability won't get accepted by the communities :P

[dGxxxx]

It's possible, for sure. Since the "big leak" everything is way more clear now and you don't need to spent weeks to decrypt memory patterns anymore.

Creating a working feature like this shouldn't take that much time for someone who knows what he's doing, but you have to test it if any other problems may occur due this feature. Changes to the client stability won't get accepted by the communities :P

Gotta try at least 😆