You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm confused on what the actual issue is here, it looks like you try to call it on a player (who notably isn't the entity owner) and it doesn't sync to the driver (who is the entity owner).
That would be expected behavior, non-owning entities can't change sync nodes for an entity not owned by them
I'm confused on what the actual issue is here, it looks like you try to call it on a player (who notably isn't the entity owner) and it doesn't sync to the driver (who is the entity owner).
That would be expected behavior, non-owning entities can't change sync nodes for an entity not owned by them
Oh yes, I should have specified that.
This is an administrative tool designed for playful interactions with players. Specifically, it triggers a server-side event that retrieves the owner of the entity to apply this native to the vehicle. In other words, it’s as if the client (the driver) was executing this action directly. I should have clarified this earlier, and I apologize
RegisterCommand("test", function()
localped=PlayerPedId();
if (notped) thenreturnprint('ped not found')
endlocalentity=GetVehiclePedIsIn(ped, false)
if (notDoesEntityExist(entity)) thenreturnprint('player not in vehicle')
endSetHeliMainRotorHealth(entity, 0)
end)
If you execute this as the driver, you will notice the same issue as shown in the videos.
What happened?
Synchronization issue with helicopter blade breaking using the native
SetHeliMainRotorHealth
Entity owner's POV (driver): https://streamable.com/oonw7j
Another player's POV: https://streamable.com/2ab34k
Expected result
That the rotors are correctly synchronized for the helicopter driver.
Reproduction steps
Importancy
Slight inconvenience
Area(s)
FiveM, FXServer
Specific version(s)
FiveM 3095 / FXServer-master SERVER v1.0.0.11840 win32
Additional information
I remain available for any additional information or to answer your questions if needed.
The text was updated successfully, but these errors were encountered: