Add engineReinitMarkers()

[TFP-dev]

This function will reinit 3D markers. This can be useful if you want to replace marker 3D model. Fixes closed issue #2213.

API:
engineReinitMarkers()

Test resource:
This resource replaces "arrow" marker and adds command reinitMarkers.
marker_test_resource.zip

Screenshot:

[CrosRoad95]

". This can be useful if you want to replace marker 3D model."
so, make if you replace 3d model of marker -> call "engineReinitMarkers", we don't use "reinitVehicles", "reinitObjects" ect after element will be replaced

[TFP-dev]

". This can be useful if you want to replace marker 3D model." so, make if you replace 3d model of marker -> call "engineReinitMarkers", we don't use "reinitVehicles", "reinitObjects" ect after element will be replaced

But we use engineRestreamWorld. Currently servers can use fact that you can't replace marker model so engineReinitMarkers is backwards compatible.

[CrosRoad95]

you actually fixing a bug, everyone will happy if suddenly markers will work as intended

[TFP-dev]

you actually fixing a bug, everyone will happy if suddenly markers will work as intended

Check issue #2213

[sbx320]

Wouldn't it be more useful to apply this whenever we replac a marker model? That way scripters wouldn't need to work around it.

[TFP-dev]

Wouldn't it be more useful to apply this whenever we replac a marker model? That way scripters wouldn't need to work around it.

Currently you can use fact that you can't replace markers, for example you can replace id 1559 with the building model and use it instead of allocating new model id with engineRequestModel and markers will stay intact.

[sbx320]

Some minor comments regarding argparser usage

Resolved

[lopezloo]

Wouldn't it be more useful to apply this whenever we replac a marker model? That way scripters wouldn't need to work around it.

Maybe that could be implemented and documented as 1.6 backwards incompatible change.

[botder]

Superseded by pull request #3059.