VenVen / Stock-Revamp

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Overlapping textures on the MK 1-2 CM

lynwoodm opened this issue · comments

I've used this mod in the past, but since the update, I've gotten this strange quirk with the texturing of this command module.
screenshot from 2015-12-11 10 31 20
screenshot from 2015-12-11 10 31 28

I don't know what I've done wrong to get the textures to appear to overlap on the old model, but it's there. Any clues onto how I can fix this?

Something is re-adding the old command pod, what mods do you have installed?

Squad is the only mk 1-2 texture I have. I don't have any other mods, other than yours that has anything to do with texture revamping on this pod. I took your mod out to kind of narrow it down to this pod alone and it seems as the original squad file loads two external texture files. Not sure if they are responsible for the results posted.

[LOG 01:18:38.783] Load(Texture): Squad/Parts/Command/Mk1-2Pod/mk 1-2 external shell Variant-Hatch NRM
[LOG 01:18:38.816] Load(Texture): Squad/Parts/Command/Mk1-2Pod/mk 1-2 external shell Variant-Hatch

As far as mods go, I have a lot of them. AVC tells me I have 42 (with yours included)

Oh sure, I have the aset interior revamp, but I feel that has nothing to do with the external part. If you are wondering what mods I have that revamp squad parts, I only have yours that does anything to squad parts. Always used your revamp mod.

screenshot from 2015-12-14 03 01 46
screenshot from 2015-12-14 03 02 01

No, point is, something is adding a MODEL to the part's cfg, via a ModuleManager patch. You need to find all patches that reference PART[Mark1-2Pod]

I'd place my bet on SDHI Service module System, that mod re-adds the stock 1-2 command model along with its umbilical socket.

You are bingo on that mod, Ven. And thanks, Nathan, that string of text help me out on this. So, what's the fix? Either delete the mod or have the patch not point back to the original texture losing the umbilical texture? I'm wondering if anyone else has had a problem with this?

For now, I'd either delete the problem model node or comment it out with //.

I just removed the patch file and it's looking like xmas with that new pod design. Thank you both for your help. Your work is very much appreciated and keep it up. Over and Out!