Having trouble making my own procedural fairing

[MrMeeb]

Hi guys,

I've been trying to make my own procedural fairing, with a custom texture (yet to be implemented, of course), and I have started off by moving @MainSailor's fairing cfg and fairing texture into my own file, and changing the path. Everything loaded in and looked as I expected. I then changed the name and title of the part to be more suitable for what the fairing would be for, and suddenly it stopped loading. After a bit of trial and error, I've found that it will load into the game with the name changed, but if I change the title, it stops loading in. Below you can see two configs of the fairing that will load into the game:

Spoiler

The default cfg that MainSailor came up with:

PART
{
name = MainSailorFairingConicWht
module = Part
author = e-dog

MODEL
{
	model = MrMeeb/ISS Modules/Russian Orbital Segment/Zarya/Fairings/sideModel
	texture = fairing1, MrMeeb/ISS Modules/Russian Orbital Segment/Zarya/Fairings/White/fairing1wht
}

//scale = 1
rescaleFactor = 1

node_stack_connect = 0, 0.5, 0, 0, -1, 0, 0

TechRequired = aviation
cost = 100
entryCost = 4600
category = Aero
subcategory = 0
title = MainSailor Conic Fairing (White)
manufacturer = Keramzit Engineering
description = Just a conic fairing for Mr. Meeb ;)
attachRules = 1,0,0,1,1

mass = 0
dragModelType = default
maximum_drag = 0.1
minimum_drag = 0.1
angularDrag = 2
crashTolerance = 8
breakingForce = 200
breakingTorque = 200
maxTemp = 3200
thermalMassModifier = 2.0
skinMassPerArea = 4.0
skinInternalConductionMult = 0.25
emissiveConstant = 0.8
fuelCrossFeed = False

stagingIcon = DECOUPLER_HOR

stageOffset = 1
childStageOffset = 1

MODULE
{
  name = ProceduralFairingSide

  density=0.1
  costPerTonne=5000
  specificBreakingForce =2000
  specificBreakingTorque=2000

  noseHeightRatio=2
  baseConeShape=0.3, 0.3, 0.7, 0.7
  noseConeShape=0.1, 0, 0.7, 0.667
  baseConeSegments=3
  noseConeSegments=11

  mappingScale=1024, 1024
  stripMapping=992, 1024
  horMapping=10, 490, 500, 980
  vertMapping=10, 170, 694, 1014
}
MODULE
{
  name = ProceduralFairingDecoupler
}

}

With the name (but not the title) changed: 

PART
{
name = ZaryaFairingLower
module = Part
author = e-dog

MODEL
{
	model = MrMeeb/ISS Modules/Russian Orbital Segment/Zarya/Fairings/sideModel
	texture = fairing1, MrMeeb/ISS Modules/Russian Orbital Segment/Zarya/Fairings/White/fairing1wht
}

//scale = 1
rescaleFactor = 1

node_stack_connect = 0, 0.5, 0, 0, -1, 0, 0

TechRequired = aviation
cost = 100
entryCost = 4600
category = Aero
subcategory = 0
title = MainSailor Conic Fairing (White)
manufacturer = Keramzit Engineering
description = Just a conic fairing for Mr. Meeb ;)
attachRules = 1,0,0,1,1

mass = 0
dragModelType = default
maximum_drag = 0.1
minimum_drag = 0.1
angularDrag = 2
crashTolerance = 8
breakingForce = 200
breakingTorque = 200
maxTemp = 3200
thermalMassModifier = 2.0
skinMassPerArea = 4.0
skinInternalConductionMult = 0.25
emissiveConstant = 0.8
fuelCrossFeed = False

stagingIcon = DECOUPLER_HOR

stageOffset = 1
childStageOffset = 1

MODULE
{
  name = ProceduralFairingSide

  density=0.1
  costPerTonne=5000
  specificBreakingForce =2000
  specificBreakingTorque=2000

  noseHeightRatio=2
  baseConeShape=0.3, 0.3, 0.7, 0.7
  noseConeShape=0.1, 0, 0.7, 0.667
  baseConeSegments=3
  noseConeSegments=11

  mappingScale=1024, 1024
  stripMapping=992, 1024
  horMapping=10, 490, 500, 980
  vertMapping=10, 170, 694, 1014
}
MODULE
{
  name = ProceduralFairingDecoupler
}

}

However, this config (where both the name and title are changed) does not load into the game.

Spoiler

PART
{
name = ZaryaFairingLower
module = Part
author = e-dog

MODEL
{
	model = MrMeeb/ISS Modules/Russian Orbital Segment/Zarya/Fairings/sideModel
	texture = fairing1, MrMeeb/ISS Modules/Russian Orbital Segment/Zarya/Fairings/White/fairing1wht
}

//scale = 1
rescaleFactor = 1

node_stack_connect = 0, 0.5, 0, 0, -1, 0, 0

TechRequired = aviation
cost = 100
entryCost = 4600
category = Aero
subcategory = 0
title = Zarya Fairing Lower
manufacturer = Keramzit Engineering
description = Just a conic fairing for Mr. Meeb ;)
attachRules = 1,0,0,1,1

mass = 0
dragModelType = default
maximum_drag = 0.1
minimum_drag = 0.1
angularDrag = 2
crashTolerance = 8
breakingForce = 200
breakingTorque = 200
maxTemp = 3200
thermalMassModifier = 2.0
skinMassPerArea = 4.0
skinInternalConductionMult = 0.25
emissiveConstant = 0.8
fuelCrossFeed = False

stagingIcon = DECOUPLER_HOR

stageOffset = 1
childStageOffset = 1

MODULE
{
  name = ProceduralFairingSide

  density=0.1
  costPerTonne=5000
  specificBreakingForce =2000
  specificBreakingTorque=2000

  noseHeightRatio=2
  baseConeShape=0.3, 0.3, 0.7, 0.7
  noseConeShape=0.1, 0, 0.7, 0.667
  baseConeSegments=3
  noseConeSegments=11

  mappingScale=1024, 1024
  stripMapping=992, 1024
  horMapping=10, 490, 500, 980
  vertMapping=10, 170, 694, 1014
}
MODULE
{
  name = ProceduralFairingDecoupler
}

}

 

What have I done wrong here?

 

[MainSailor]

The way that fairing config works is to have a blank placeholder texture in the Fairings folder along with the model file (fairing1.png) and the individual textures in subfolders (as not to duplicate the shared textures and model file for each variant.) Did you keep the fairing1.png file in the same folder that your sideModel.mu file is in? You really only need one copy of the mu file which is referenced in each cfg. Changing the title should have no effect on part loading (it could be blank for all KSP cares.)

 

Also, I don't know about the newer Unity 5 builds of KSP, but I know from back in the .25-era, Unity did not like parsing file names that contained spaces. I'd at the very least replace the spaces with a dash or underscore (i.e., ISS_Modules). It's completely possible that this is no longer an issue, but if we're troubleshooting, its worth considering.

[MrMeeb]

11 hours ago, MainSailor said:

The way that fairing config works is to have a blank placeholder texture in the Fairings folder along with the model file (fairing1.png) and the individual textures in subfolders (as not to duplicate the shared textures and model file for each variant.) Did you keep the fairing1.png file in the same folder that your sideModel.mu file is in? You really only need one copy of the mu file which is referenced in each cfg. Changing the title should have no effect on part loading (it could be blank for all KSP cares.)

 

Also, I don't know about the newer Unity 5 builds of KSP, but I know from back in the .25-era, Unity did not like parsing file names that contained spaces. I'd at the very least replace the spaces with a dash or underscore (i.e., ISS_Modules). It's completely possible that this is no longer an issue, but if we're troubleshooting, its worth considering.

It turns out that I totally forgot about the fact that the parts list is alphabetically ordered. The fairing was there all along, it just moved to the bottom of the list. This is why you need sleep, kids 

Everything is working fine now. Let's never talk about this again