This is the same issue as in K1. It appears that racetex variants 2-5 of the War Droid forcibly override the texture for the integrated blaster these droids carry.
This is the same problem you get when trying to apply a texture variant via appearance.2da to any other model with more than one texture (like a full body model with separate head and body textures). I thought there must be some hard-coded exception for the War Droid, similar to Bao Dur's robo arm, but apparently not. I guess this carried over from K1 without anyone picking up on it.
There are three avenues for a fix. The first is to alter the UVs of the model and merge both droid and blaster meshes into a single texture. The second approach is to create separate models for each War Droid variant and edit the appropriate appearance.2da rows to point to these. The third approach is to edit the base model and swap out the incorporated blaster mesh for a reference object, which will pull in an external blaster model, thus exempting it from the texture override (which is the fix implemented in the K1 Community Patch).
The first approach is the least ideal. It would break compatibility with any modded textures for the droids or the blaster. The second approach would be the "standard" way to do it, but it could be vulnerable to 2DA edits and would not support expanded texture variants. The third approach has the benefit of only requiring a single model edit and no appearance.2da changes, making it the most compatible with third-party changes, with the additional added flexibility of now dynamically utilising modded weapons. One downside, however, is that the bullethook is fixed in the droid model itself, which may lead to visual VFX offset issues with modded weapons (albeit a minor issue).
Reported by Sith Holocron in relation to Sithspecter's HQ Blaster mod, but it also happens with the vanilla War Droid models.
This is the same issue as in K1. It appears that racetex variants 2-5 of the War Droid forcibly override the texture for the integrated blaster these droids carry.
This is the same problem you get when trying to apply a texture variant via appearance.2da to any other model with more than one texture (like a full body model with separate head and body textures). I thought there must be some hard-coded exception for the War Droid, similar to Bao Dur's robo arm, but apparently not. I guess this carried over from K1 without anyone picking up on it.
There are three avenues for a fix. The first is to alter the UVs of the model and merge both droid and blaster meshes into a single texture. The second approach is to create separate models for each War Droid variant and edit the appropriate appearance.2da rows to point to these. The third approach is to edit the base model and swap out the incorporated blaster mesh for a reference object, which will pull in an external blaster model, thus exempting it from the texture override (which is the fix implemented in the K1 Community Patch).
The first approach is the least ideal. It would break compatibility with any modded textures for the droids or the blaster. The second approach would be the "standard" way to do it, but it could be vulnerable to 2DA edits and would not support expanded texture variants. The third approach has the benefit of only requiring a single model edit and no appearance.2da changes, making it the most compatible with third-party changes, with the additional added flexibility of now dynamically utilising modded weapons. One downside, however, is that the bullethook is fixed in the droid model itself, which may lead to visual VFX offset issues with modded weapons (albeit a minor issue).
Reported by Sith Holocron in relation to Sithspecter's HQ Blaster mod, but it also happens with the vanilla War Droid models.