When a server is running a mission directly from a bare folder (<b>without a PBO</b>), and for all <b>Steam Workshop missions</b>, using the setObjectTextureGlobal command from the server to assign a texture from the mission files always results in a "Cannot load texture" error being displayed to all players connected to the server and anyone joining later as well.
This problem is caused by the fact that setObjectTextureGlobal is broadcasting the raw server-side MPMissions path resolving to the texture, which for example looks like "<b>mpmissions\MyMission.Altis</b>\textures\image.jpg". However, for clients, the MPMissions path is different from the server; in the cases described above, it often ends up being "<b>mpmissions\__CUR_MP.Altis</b>".
Therefore, whenever clients receive a broadcast from setObjectTextureGlobal called from the server, the game tries to resolves textures in "mpmissions\MyMission.Altis", while they are located in "mpmissions\__CUR_MP.Altis", which causes the "Cannot load texture" error being displayed, and the affected vehicles looking partially invisible. {F25402}