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
engineRequestModel("vehicle") gives you a new vehicle model ID. Logically this ID needs to be applied to an element using setElementModel. You may also want to use engineFreeModel when the element streams out to save memory at some point.
Door & panel damage that you can obtain on a vehicle by damaging it yourself or using setVehicleDoorState & setVehiclePanelState resets after the vehicle's model is changed.
This is problematic and can strongly be considered a bug as it's some unintended behavior.
Serverside sync should fix this issue.
Version
r21135
The text was updated successfully, but these errors were encountered:
Fernando-A-Rocha
changed the title
Door & panel states not syncing after model change (related to engineRequestModel & engineFreeModel features)
Door & panel states (damage) not syncing for vehicles with custom model IDs
Feb 1, 2023
@TheNormalnij Possible to fix this? Sorry for ping but this was created in march 2022 and more bugs related to allocated model IDs have been fixed recently, so this could be too?
engineRequestModel("vehicle")
gives you a new vehicle model ID. Logically this ID needs to be applied to an element using setElementModel. You may also want to use engineFreeModel when the element streams out to save memory at some point.I've noticed an issue while testing my newmodels resource related to visible damage on the vehicle not staying.
Door & panel damage that you can obtain on a vehicle by damaging it yourself or using
setVehicleDoorState
&setVehiclePanelState
resets after the vehicle's model is changed.This is problematic and can strongly be considered a bug as it's some unintended behavior.
Serverside sync should fix this issue.
Version
r21135
The text was updated successfully, but these errors were encountered: