model{} pretty random if it works or not?

[K3-Chris]

I can't find any good documentation on it, but even so I'm pretty sure I'm doing it right, and, it's not working most of the time.

Log:

PartLoader: Compiling Part 'B9_Aerospace/Parts/Cockpit_MK1/part/B9_Cockpit_MK1'

(Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

NullReferenceException: Object reference not set to an instance of an object
  at PartLoader.ReplaceTextures (UnityEngine.GameObject model, System.Collections.Generic.List`1 textureNames, System.Collections.Generic.List`1 newTextures) [0x00000] in <filename unknown>:0 

  at PartLoader.CompileModel (.UrlConfig cfg, .ConfigNode partCfg, Single scaleFactor) [0x00000] in <filename unknown>:0 

  at PartLoader.ParsePart (.UrlConfig urlConfig, .ConfigNode node) [0x00000] in <filename unknown>:0 

  at PartLoader+
.MoveNext () [0x00000] in <filename unknown>:0 

(Filename:  Line: -1)

relevant part of .cfg:

MODEL
{
	model = B9_Aerospace/Parts/Cockpit_MK1/model
	texture = model_cockpit_mk2 , B9_Aerospace/Parts/Cockpit_MK2/model_cockpit_mk2
	texture = model_cockpit_mk2_emissive , B9_Aerospace/Parts/Cockpit_MK2/model_cockpit_mk2_emissive
}

The paths are correct, the filenames are correct both sides the , the model works, I get a white part if the game loads which it does if I don't have the textures unity puts in the folder, if they're there game crashes on loading the part.

I don't get it, and I'm not sure how much longer I want to bash my skull against this brick wall. This isn't the first time I've had completely unexplained to me failure of MODEL{texture}

[raidernick]

This is not the right area to post this

[K3-Chris]

Only area that seems applicable?

[nli2work]

there's a texture name mismatch somewhere. check extention case and file name case. dummy textures need to named same as the texture the MU is referring to. I get this pretty often because I have dozens of models referring to single set of textures, and always fixed when I made sure the texture names matched up 100%

[K3-Chris]

Trust me the names are right, I don't make those kinds of mistakes, I copied the names.

[nli2work]

is the model line referring to the correct model? I use MODEL{} for just about everything: Props, IVA, Externals, and with textures I didn't create. every time there was a problem it was a mistake I made.

Edited September 8, 2014 by nli2work

[K3-Chris]

is the model line referring to the correct model?

... No, I obviously put in the wrong model expecting it to work.

[Orionkermin]

I've found that at times I had to put "dummy" textures in the same file as the model. A 1x1 pixel works, I'm not sure why it seems to need this but it does usually work when I have issues. Something to try at least

Edit: This is of course if you're not keeping the models and textures all in one file like Kerbin Shuttle Orbiter does.

[nli2work]

well, not much more I can help then. never had the issue you are having.

[MOARdV]

relevant part of .cfg:

MODEL
{
	model = B9_Aerospace/Parts/Cockpit_MK1/model
	texture = model_cockpit_mk2 , B9_Aerospace/Parts/Cockpit_MK2/model_cockpit_mk2
	texture = model_cockpit_mk2_emissive , B9_Aerospace/Parts/Cockpit_MK2/model_cockpit_mk2_emissive
}

Stupid question, maybe, but are the spaces before the comma present in the CFG? I recall seeing something like that happen in one of the reskins I did locally, and I am pretty sure it's because I had spaces before the comma / after the first texture name.

[Gaalidas]

... No, I obviously put in the wrong model expecting it to work.

Seriously, or are you messing with us? I have experienced a few limited cases of this model reference not working, but it's been a long time since that happened last. I did notice something however... the textures you are trying to replace have the same name as the textures you are trying to replace them with. however, the model you are referencing is a MK1 model, and the textures you are replacing are named as if the MK1 model was referencing MK2 textures originally. My thought would be that the model was originally trying to use MK1 textures, and thus those are the texture names which should be in the first part of the "texture =" line. I'm too lazy right now to check this out myself, but that's my only bit of advice right now.

Stupid question, maybe, but are the spaces before the comma present in the CFG? I recall seeing something like that happen in one of the reskins I did locally, and I am pretty sure it's because I had spaces before the comma / after the first texture name.

That actually isn't an issue as far as I am aware, and from my own experience of taking un-optimized mods I have downloaded and giving them common-texture swaps to help my memory load.

Edited September 8, 2014 by Gaalidas

[Lack]

I've found that at times I had to put "dummy" textures in the same file as the model. A 1x1 pixel works, I'm not sure why it seems to need this but it does usually work when I have issues. Something to try at least

Yeah, this is what I had to do; very occasionally it still doesn't work, then I use a 5x5 and that seems to solve it.

[K3-Chris]

I'm giving up, this makes no sense what so ever:

    MODEL
    {
		model = B9_Aerospace/Parts/Cockpit_MK1/model
		texture = model_cockpit_mk2, B9_Aerospace/Parts/Cockpit_MK2/model_cockpit_mk2
		texture = model_cockpit_mk2_emissive, B9_Aerospace/Parts/Cockpit_MK2/model_cockpit_mk2_emissive
    }

If I have that in the .cfg I get a nullref that stops KSP from loading, remove it and replace with model = model.mu and copy the textures over from the mk2 folder and tada, it loads.

I have dummy files, or even the proper files, the paths and names are copied from the system, they can't have typos, they exist, KSP still does this:

PartLoader: Compiling Part 'B9_Aerospace/Parts/Cockpit_MK1/part/B9_Cockpit_MK1'

(Filename: C:/BuildAgent/work/d63dfc6385190b60/artifacts/StandalonePlayerGenerated/UnityEngineDebug.cpp Line: 49)

NullReferenceException: Object reference not set to an instance of an object
  at PartLoader.ReplaceTextures (UnityEngine.GameObject model, System.Collections.Generic.List`1 textureNames, System.Collections.Generic.List`1 newTextures) [0x00000] in <filename unknown>:0 

  at PartLoader.CompileModel (.UrlConfig cfg, .ConfigNode partCfg, Single scaleFactor) [0x00000] in <filename unknown>:0 

  at PartLoader.ParsePart (.UrlConfig urlConfig, .ConfigNode node) [0x00000] in <filename unknown>:0 

  at PartLoader+
.MoveNext () [0x00000] in <filename unknown>:0 

(Filename:  Line: -1)

Edited September 8, 2014 by K3|Chris

[nli2work]

what textures were exported with "Cockpit_MK1/model"?

[K3-Chris]

model_cockpit_mk2.tga

model_cockpit_mk2_emissive.tga

[K3-Chris]

*facedesk* really? REALLY? that would be an excellent explanation for the problem, all textures I've ever had problems with had _s in them because that's how B9 textures are named, oh god, so many hours and so much cranium lost to that brick wall...

[nli2work]

I don't think underscore is the problem. FS docs says it only matters if the MU name has underscore. I use underscore in texture names and never had this issue.

My MODEL{} blocks look like this

MODEL
	{
		model = NohArksPnP/Parts/Engines/jeyTew/jeyTew
		texture = UHB_props_DIF, NohArksPnP/Parts/Engines/noseMountUHB/UHB_props_DIF
		texture = UHB_props_EMI, NohArksPnP/Parts/Engines/noseMountUHB/UHB_props_EMI
		texture = UHB_props_NRM, NohArksPnP/Parts/Engines/noseMountUHB/UHB_props_NRM
		texture = rectFuselage_NRM, NohArksPnP/Parts/rectFuel/rectFuselage_NRM
		texture = rectFuselage_DIF, NohArksPnP/Parts/rectFuel/rectFuselage_DIF
		texture = rotorDisc, NohArksPnP/Parts/Engines/noseMountUHB/rotorDisc
	}

is there a flag transform? does it have a dummy texture assigned?

Edited September 8, 2014 by nli2work

[Gaalidas]

Actually, I'm a bit worried that this is more serious than we're all seeing here. If he's getting nullrefs from a model not finding its textures, then there's more going on here than a problematic configuration. Usually if a model cannot find a texture, the game simply doesn't use that texture and instead displays the white layer for whatever use that texture was intended for. For a diffuse, that means a while model... for a normal that would simply mean a non-functioning normal map. In the most extreme case, the part will simply not compile properly and the part will be absent from the list. Critical errors do not occur for this kind of configuration issue.

As to the underscores, I have not experienced any issues with textures containing them.

[NathanKell]

Make sure that the textures appear sooner, in path-alphabetical order, than the model and cfg.

That's why SXT is named SXT, so it loads after the Squad folder.

[K3-Chris]

Make sure that the textures appear sooner, in path-alphabetical order, than the model and cfg.

That's why SXT is named SXT, so it loads after the Squad folder.

So models and .cfg go in /x/ textures go in /a/ ?

[NathanKell]

That should work, yeah. Just a guess, but the NRE might well be that it's trying to reference a texture whose GDB entry doesn't exist yet.

If that doesn't work, let me know and I'll poke around a bit.

[Gaalidas]

I think it's getting a bit over complicated now... but it would explain why the program's reaction is so over the top.