Page MenuHomeFeedback Tracker

setObjectTextureGlobal is not global during init.
Closed, ResolvedPublic

Description

The setObjectTextureGlobal script command is not global during initialisation of init boxes of units. This has a knock on effect on effecting BIS_fnc_setUnitInsignia as it uses this command. So to reproduce it we will mimic setting an insignia on a soldier. I believe as the command says it is global it should be global all the time and not just during the mission. Note if someone joins in progress (JIP) later, they will see the texture fine, but any clients connected at the start will not see the texture.

Details

Legacy ID
2687725806
Severity
None
Resolution
Fixed
Reproducibility
Always
Category
Scripting
Steps To Reproduce
  • Create an empty mission with a character for yourself and a NATO Rifleman (They have the texture slot for arm patchs) on the NATO rifleman place the following on their init:

if (isServer) then { this setObjectTextureGlobal [1,"\a3\UI_F_Bootcamp\Data\CfgUnitInsignia\bi_ca.paa"] };

  • Observe in the editor, that the unit patch shows.
  • Export to MPMissions and place on a dedicated server/someone else hosting.
  • Observe that the texture is not set.

Event Timeline

Snippers edited Steps To Reproduce. (Show Details)Jul 27 2014, 5:19 PM
Snippers edited Additional Information. (Show Details)
Snippers set Category to Scripting.
Snippers set Reproducibility to Always.
Snippers set Severity to None.
Snippers set Resolution to Fixed.
Snippers set Legacy ID to 2687725806.May 7 2016, 7:05 PM

This is now fixed in 1.32 as it was mentioned in SPOTREP #00034
Fixed: Init message for setObjectTexture saved in MP serialization