New functions setWeaponRenderEnabled & isWeaponRenderEnabled

[FileEX]

This PR adds functions that allow disabling the rendering of weapons. Some servers do not use the original weapons and replace them with their own system. To remove the original weapons, they need to replace the model with an empty one or manipulate the weapon model's LOD distance. The function only toggles the rendering of the weapon object, so shooting, aiming, etc., can still be done

bool setWeaponRenderEnabled(bool enabled)
bool isWeaponRenderEnabled()

Thanks to @ds1-e for idea

[ds1-e]

On a side note regarding why it should be used instead of other ways to hide weapon model, see this comment

[lynconsix]

This PR adds functions that allow disabling the rendering of weapons. Some servers do not use the original weapons and replace them with their own system. To remove the original weapons, they need to replace the model with an empty one or manipulate the weapon model's LOD distance. The function only toggles the rendering of the weapon object, so shooting, aiming, etc., can still be done

bool setWeaponRenderEnabled(bool enabled)
bool isWeaponRenderEnabled()

Thanks to @ds1-e for idea

It's much better this way instead of replacing models, because replacing models for “new” weapons consumes memory.

[botder]

You have to reset the state after quit/on server join.

[lynconsix]

@FileEX
You could add another function, resetWeaponRender(int modelid) and instead of disabling all weapon rendering, identify the model of the weapon you want to disable.
setWeaponRenderEnabled(int modelid, bool enabled) & isWeaponRenderEnabled(int modelid)

[ds1-e]

@lynconsix I disagree. See my previous comment for details, there's no need to add extra steps on top of already horribly performing GTA function. If you want to selectively disable certain weapons, just use old methods (after all you should still rather use something like pAttach for any weapon, considering it's more smoother alternative)

[FileEX]

You have to reset the state after quit/on server join.

Done

[derxgbb]

I do agree with @lynconsix to have a modelid param for obvious reasons. Without that this new feature will only be used by servers where every weapon model is changed. (if this PR gets merged like this - it is still nice)

off topic:
This reminds me of weapon properties.
You can't set a given player's weapon property because the func doesn't have a player/ped param so it changes for everyone and there is no real clientside variant of this function. The current clientside version of this func only works on custom weapons so the func name should be setCustomWeaponProperty

[ds1-e]

I do agree with @lynconsix to have a modelid param for obvious reasons. Without that this new feature will only be used by servers where every weapon model is changed. (if this PR gets merged like this - it is still nice)

off topic: This reminds me of weapon properties. You can't set a given player's weapon property because the func doesn't have a player/ped param so it changes for everyone and there is no real clientside variant of this function. The current clientside version of this func only works on custom weapons so the func name should be setCustomWeaponProperty

This can already be done using:

engineSetModelLODDistance(weaponModelID, 0.001)

What can't be done however, is disabling GTA function call which i've already mentioned twice (and seems to be totally ignored), being secondary purpose of it. Adding selectivity would force it to process anyways, which completely excludes it.