i cant vote 1 million times yes on this ticket, but i want to, i really hate to see that the same vehicle will spawn with a different color every time i restart the game

I would really prefer to see disabled vehicle color randomization by vehicle classes like suggested in "Additional Information", also it would be better if check would be made on "init" event hander rather than in randomize script itself so it wouldn't even start another script thread with execVM.

C_Offroad_01_F >> EventHandlers:

init = '(_this select 0) execVM "\A3\soft_F\Offroad_01\scripts\randomize.sqf"';

change to

init = 'if(({(_this select 0) isKindOf _x} count (missionNamespace getVariable ["BIS_noVehicleRandomization", []])) == 0) then {(_this select 0) execVM "\A3\soft_F\Offroad_01\scripts\randomize.sqf";};';

related http://feedback.arma3.com/view.php?id=16017

related: https://www.youtube.com/watch?v=FhUmIEFXlsQ

Please for god's sake sort this out!!!! :))

Here is the summary http://killzonekid.com/arma-annoyances-say-no-to-randomize/

Ack that stuff like this is excellent for those who want to drop and play with vehicles/civvies/etc that aren't clones, but this is incredibly frustrating for mission authors.

I recall getting equally pissed off with the randomisation for the PMC DLC in ArmA 2. I'm irritated to see that this is now of a greater scale in ArmA 3, still without a way to nip it in the bud without running another script to override it.

while i understand why the FIA are having offroads without doors or rear view mirrors, there are some instances were i would like to be able to control that permanently for a mission

I have added some new functionality that may help:
http://forums.bistudio.com/showthread.php?149636-Development-Branch-Changelog&p=2668894&viewfull=1#post2668894

Definitely a step in the right direction. However there needs to be a way to disable the setTexture functionality of a vehicles altogether (exit the script).

This change is barely useful as you still cannot change vehicle texture right away.

_vehicle = createVehicle ["C_Offroad_01_F", getPos player, [], 0, ""]; _vehicle setObjectTexture [0, ""];

Will not remove first texture. Issue is not solved.

SaMatra is right (of course), since setVehicleInit was removed, there is no way to script a properly textured vehicle.

Ok guys, reopening the issue. Since there is a feedback needed, could you please specify what exactly your proposes are so our Encoding master pettka has easier job to do?
Thank you very much!

Well, I think he would have to extend setObjectTextureGlobal/setObjectTexture to work with the built-in textures.

The setVariable workaround is not an option for vehicles created by script (i.e. createVehicle).

Another way would be to extend createVehicle (array) by a new, optional parameter to include a texture index of built-in textures.

Well looking at the randomize scripts, you probably need a delay when you execute setObjectTexture[Global] after the creation.

Or are you SaMatra saying this doesn't work, or that setting an "empty texture" does not work?

You might still run into a JIP problem with the above depending on the execution order. Make sure to double check this.

Well looking at the randomize scripts, you probably need a delay when you execute setObjectTexture[Global] after the creation.

This is exactly the problem, at the moment I have to spawn scheduled threads that sleep for a second and only then apply needed texture. Before it was even worse with execVM as it sometimes executed randomization script after my scheduled thread overwriting my texture changes.

My suggestion is following: Let us handle randomization ourselves, give us a choice to disable BIS randomization scripts all together, no default texture setting, no nothing, just don't execute anything and let us handle this ourselves. I already provided an easy solution in the ticket. Wrap all inits that have randomization scripts with following code:

init = 'if(({(_this select 0) isKindOf _x} count (missionNamespace getVariable ["BIS_noVehicleRandomization", []])) == 0) then {(_this select 0) execVM "\A3\soft_F\Offroad_01\scripts\randomize.sqf";};';

That's it. If mission designer will need to disable randomization for all Offroads they will just add:

BIS_noVehicleRandomization = ["Offroad_01_base_F"];

This is assumed to be added somewhere on mission init and not during the mission.

Alternatively this can be moved into description.ext and read with getArray(missionConfigFile >> "noVehicleRandomization")

The new vehicle customization should be all over the game, feel free to provide feedback at https://forums.bistudio.com/topic/179469-vhc-vehicle-customization-dev-branch/
If it suits You well, close the issue, please. Thanks a lot for the valuable feedback that made us to do the whole feature.