[1.8.1] DaMichels Parts [1.1.0.0](2020 02 17)

[JadeOfMaar]

@zer0Kerbal @Jiraiyah I fixed that for ya.

@PART[DM-SphericalTank-*]:NEEDS[B9PartSwitch,CommunityResourcePack,UmbraSpaceIndustries]
{
	@MODULE[ModuleB9PartSwitch]:HAS[#moduleID[SphericalTankFuelSwitch]]
	{
		SUBTYPE:NEEDS[UmbraSpaceIndustries/Karbonite]
		{
			name = #DST_name_karbonite // = Karbonite
			title = #DST_title_karbonite // = Karbonite
			tankType = DSTKarbonite
		}
		SUBTYPE:NEEDS[UmbraSpaceIndustries/KarbonitePlus]
		{
			name = #DST_name_karborundum // = Karborundum
			title = #DST_title_karborundum // = Karborundum
			tankType = DSTKarborundum
		}
	}
}

There's no point in setting a NEEDS for the same mod that it's a part of. And the AFTER is invalid. AFTER[SphericalTanks] assumes that GameData/SphericalTanks/ exists, which it does not and is not part of this mod. The target parts array is condensed since all the target parts have a very large common section in their names.

On 2/18/2020 at 11:06 PM, shdwlrd said:

Ooo… spherical tanks that aren't associated with USI, now I have to start playing with those.

I know, right?

16 hours ago, shdwlrd said:

almost spot on for the Mk1 parts, the max temps are a little high.

They should be 2000K. 2900K is higher than the Mk3 plane parts and entering heatshield or fairing territory.

I like that the fuselage parts have a bicoupler thing going on. I could add nodes for those if anyone wants them.

[zer0Kerbal]

question:

I can add more tanks - 1.875 / 2.5 / 3.75 etc. - currently supported by TweakScale; however would it be better to have actual parts, or just parts that appear if TweakScale isn't installed?

 

I was planning on pushing a set of releases today, but the sheer volume of suggestions - plus having a few more mods added to my VAB set my timing back. Still planning to have them out this weekend.

I have thought about doing a B9node switch for the bicoupler fuselage pieces - it would be switch between current, or two (1 | 2 nodes).

and how about more cargo bays? larger smaller?

also - keep or ditch the xmitter in the tail boom?

 

DM-fuselage-cone

basing stats on: Advanced Nose Cone - Type B (pointyNoseConeB)

Spoiler

 

scale = 0.9375, 0.9375, 0.9375 // 1.0, 0.9375, 1.0 noted by Kottabo

entryCost = 8000 // 1600
cost = 400

mass = 0.1
dragModelType = default
maximum_drag = 0.1 // 0.11
minimum_drag = 0.1
angularDrag = 0.25 // 0.5
crashTolerance = 10
breakingForce = 50
breakingTorque = 50
maxTemp = 2000 // 2900

bulkheadProfiles = mk1, size2, srf // added size2

// added

explosionPotential = 0.5

CoMOffset = 0.0, 0.0, -0.313

CoPOffset = 0.0, 0.0, -0.313

CoLOffset = 0.0, 0.0, -0.313

CenterOfDisplacement = 0.0, -0.2, 0.0

thermalMassModifier = 6.0

emissiveConstant = 0.95

ModuleAnimateHeat

 

 DM-fuselage-tailboom

Based upon Tail Connector A [airplaneTailB]

Spoiler

 

• entryCost = 2500 // 1600
• cost = 500 // 200
•  
• mass = 0.02
• dragModelType = default
• maximum_drag = 0.2
• minimum_drag = 0.3
• angularDrag = 1
• crashTolerance = 8 // 20
• maxTemp = 2200 // 2900
•  
• thermalMassModifier = 6.0
• emissiveConstant = 0.95
•  
• explosionPotential = 0.5
• CoMOffset = 0.0, -1.5, 0.0
• CoPOffset = 0.0, -1.5, 0.0
• CoLOffset = 0.0, -1.5, 0.0
• CenterOfDisplacement = 0.0, -1.5, 0.0
• buoyancy = 0.1
• explosionPotential = 0.5
• ModuleAnimateHeat

 

DM-fuselage-X1

based upon Mk2 Rocket Fuel Fuselage Short(mk2FuselageShortLFO)

Spoiler

 

• mirrorRefAxis = 0, 0, -1
• TechRequired = aerodynamicSystems
• entryCost = 15000 // 1600
• cost = 500
• mass = 0.125
• dragModelType = default
• maximum_drag = 0.2
• minimum_drag = 0.3
• angularDrag = 1
• crashTolerance = 50 // 10
• breakingForce = 200
• breakingTorque = 200
• maxTemp = 2500 // 2900
• bulkheadProfiles = mk1, srf
• buoyancy = 0.1
• ModuleLiftingSurface
• explosionPotential = 0.5
• LiquidFuel = 72
• Oxidizer = 88

 

DM-fuselage-X2

based upon Mk2 Rocket Fuel Fuselage(mk2FuselageLongLFO)

Spoiler

 

• mirrorRefAxis = 0, 0, -1
• TechRequired = aerodynamicSystems
• entryCost = 18000 // 1600
• cost = 900
• mass = 0.125
• dragModelType = default
• maximum_drag = 0.2
• minimum_drag = 0.3
• angularDrag = 1
• crashTolerance = 50 // 10
• breakingForce = 200
• breakingTorque = 200
• maxTemp = 2500 // 2900
• buoyancy = 0.1
• bulkheadProfiles = mk1, srf
• ModuleLiftingSurface
• explosionPotential = 0.5
• LiquidFuel = 144
• Oxidizer = 176

 

 DM-fuselage-adapter

based upon (mk2SpacePlaneAdapter) Mk2 to 1.25m Adapter

Spoiler

 

• TechRequired = aerodynamicSystems
• entryCost = 14000 // 1600
• cost = 500
• mass = 0.14
• dragModelType = default
• maximum_drag = 0.2
• minimum_drag = 0.1 // 0.3
• angularDrag = 2 // 1
• crashTolerance = 50 // 10
• breakingForce = 50 // 200
• breakingTorque = 50 // 200
• maxTemp = 2500 // 2900
• emissiveConstant = 0.8
• bulkheadProfiles = mk1, size1, srf
• buoyancy = 0.1
• explosionPotential = 0.5
• ModuleLiftingSurface
• LiquidFuel = 90
• Oxidizer = 110

 

DM-fuselage-front

based upon (noseConeAdapter) NCS Adapter

 

Spoiler

 

• TechRequired = aerodynamicSystems
• entryCost = 8000 // 600
• cost = 400
• mass = 0.1 // 0.11
• dragModelType = default
• maximum_drag = 0.1
• minimum_drag = 0.1
• angularDrag = 0.25 // 0.5
• crashTolerance = 10
• breakingForce = 200
• breakingTorque = 200
• maxTemp = 2400 // 2900
• explosionPotential = 0.5
• CenterOfDisplacement = 0.0, -0.2, 0.0
• thermalMassModifier = 6.0
• emissiveConstant = 0.95
• buoyancy = 0.1
• bulkheadProfiles = mk1, size0
• ModuleAnimateHeat
• LiquidFuel = 45
• Oxidizer = 55

 

 

Edited February 22, 2020 by zer0Kerbal

[zer0Kerbal]

with B9 installed, will choose between either the side two or the central; will be able to select top/bottom separately. (1.1.0.2 - not released yet)

 

@JadeOfMaar

Edited February 23, 2020 by zer0Kerbal

[zer0Kerbal]

 

DaMichel's Fuselage Version 1.1.0.1 - Spit'n'Polish

zer0Kerbal released this 2020 02 22

Spoiler

 

DaMichel's Fuselage Version 1.1.0.1 - Spit'n'Polish

zer0Kerbal released this 2020 02 22

Version 1.1.0.1 - Spit'n'Polish

• thank you to KottabosGames for the review and suggestions!
• thank you to BenjaminCronin for pointed out decorative right brace in changelogs. wite-out applied.
• Also dangling VERSION. superglued applied.
• adjusted strength and temperatures of all parts.
• added explosionPotential = 0.5
• added missing buoyancy = 0.1
• [DM-fuselage-intake.cfg] has the same specs like the Ram Air Intake.
  • added missing thermalMassModifier = 12.0
  • added missing machcurve to ModuleResourceIntake on intake
  • adjusted intakeSpeed from 10 to 15
  • adjusted RESOURCE IntakeAir amount/maxAmount from 0.2 to 2.0
  • adjusted cost/entryCost from 2000/1600 to 2680/14000
  • adjusted maximum_drag from 0.2 to 0.3
  • adjusted minimum_drag from 0.2 to 0.3
  • added missing ModuleAnimateHeat
  • added missing stackSymmetry = 2
• [DM-fuselage-cone]
• basing stats on: Advanced Nose Cone - Type B (pointyNoseConeB)
  • adjusted scale = 0.9375, 0.9375, 0.9375 from 1.0, 0.9375, 1.0 noted by Kottabo
  • adjusted entryCost to 8000 from 1600
  • corrected typo on maximum_drag should have been 0.1 instead it was 0.11
  • adjusted angularDrag to 0.25 from 0.5
  • adjusted maxTemp to 2000 from 2900
  • added: size2 to bulkheadProfiles = mk1, size2, srf
  • added: explosionPotential = 0.5
  • added: CoMOffset = 0.0, 0.0, -0.313
  • added: CoPOffset = 0.0, 0.0, -0.313
  • added: CoLOffset = 0.0, 0.0, -0.313
  • added: CenterOfDisplacement = 0.0, -0.2, 0.0
  • added: thermalMassModifier = 6.0
  • added: emissiveConstant = 0.95
  • added: buoyancy = 0.1
  • added ModuleAnimateHeat
• [DM-fuselage-tailboom]
• Based upon Tail Connector A (airplaneTailB)
  • adjusted entryCost to 2500 from 1600
  • adjusted cost to 500 from 200
  • adjusted crashTolerance to 8 from 20
  • adjusted maxTemp to 2200 from 2900
  • added: thermalMassModifier = 6.0
  • added: emissiveConstant = 0.95
  • added: explosionPotential = 0.5
  • added: CoMOffset = 0.0, -1.5, 0.0
  • added: CoPOffset = 0.0, -1.5, 0.0
  • added: CoLOffset = 0.0, -1.5, 0.0
  • added: CenterOfDisplacement = 0.0, -1.5, 0.0
  • added: buoyancy = 0.1
  • added: explosionPotential = 0.5
  • added: ModuleAnimateHeat
• [DM-fuselage-X1] DMF - Flat Fuel Tank X1
• based upon Mk2 Rocket Fuel Fuselage Short(mk2FuselageShortLFO)
  • adjusted: entryCost to 15000 from 1600
  • adjusted: crashTolerance to 50 from 10
  • adjusted: maxTemp to 2500 from 2900
  • added: buoyancy = 0.1
  • added: srf to bulkheadProfiles = mk1, srf
  • added: mirrorRefAxis = 0, 0, -1
  • added: ModuleLiftingSurface
• [DM-fuselage-X2] DMF - Flat Fuel Tank X2
• based upon Mk2 Rocket Fuel Fuselage(mk2FuselageLongLFO)
  • adjusted: entryCost to 18000 from 1600
  • adjusted: crashTolerance to 50 from 10
  • adjusted: maxTemp to 2500 from 2900
  • added: buoyancy = 0.1
  • added: srf to bulkheadProfiles = mk1, srf
  • added: mirrorRefAxis = 0, 0, -1
  • added: ModuleLiftingSurface
• [DM-fuselage-front] DMF - Flat End
• based upon (noseConeAdapter) NCS Adapter
  • adjusted: entryCost to 8000 from 600
  • adjusted: mass to 0.1 from 0.11
  • adjusted: angularDrag from 0.25 // 0.5
  • adjusted: maxTemp to 2400 from 2900
  • added: explosionPotential = 0.5
  • added: CenterOfDisplacement = 0.0, -0.2, 0.0
  • added: thermalMassModifier = 6.0
  • added: emissiveConstant = 0.95
  • added: buoyancy = 0.1
  • added: bulkheadProfiles = mk1, size0
  • added: ModuleAnimateHeat
• [DM-fuselage-adapter] DMF - Flat to 1.25m Round Adapter
• based upon (mk2SpacePlaneAdapter) Mk2 to 1.25m Adapter
  • adjusted: entryCost to 14000 from 1600
  • adjusted: minimum_drag to 0.1 from 0.3
  • adjusted: angularDrag to 2 from 1
  • adjusted: crashTolerance to 50 from 10
  • adjusted: breakingForce to 50 from 200
  • adjusted: breakingTorque to 50 from 200
  • adjusted: maxTemp to 2500 from 2900
  • added: srf to bulkheadProfiles = mk1, size1, srf
  • added: buoyancy = 0.1
  • added: emissiveConstant = 0.8
  • added: explosionPotential = 0.5
  • added: ModuleLiftingSurface
• adjusted breakingForce on all parts from 50 to 200 (except where noted)
• adjusted breakingTorque on all parts from 50 to 200(except where noted)
• adjusted B9fuelswitch to have LF come after Structural instead of LFO

#2

• ---

  Kerbal Space Program 1.8.1

 

[zer0Kerbal]

DaMichel's AeroRadial

Version 1.1.0.1 - Spit'n'Polish

Spoiler

 

zer0Kerbal released this 23 Feb 2020

Version 1.1.0.1 - Spit'n'Polish

• thank you to BenjaminCronin for pointed out decorative right brace in changelogs. wite-out applied.
• Also dangling VERSION. superglue applied.
• added attach node to the back (rear) of the parts
• updated the DM-RFC texture.
• RTG: adjusted cost/entryCost from 34950/58000 to 20000/50000
• RTG: adjusted TechRequired from experimentalElectrics to largeElectrics
• removed tags.cfg (redundant patch since tags now in localization)
• updated product hero shots
• created SpaceDock header

---

Kerbal Space Program 1.8.1

 

 

Edited February 24, 2020 by zer0Kerbal

[jimmymcgoochie]

Found the 2.5m cargo bays a few days ago and they're very useful, but the highlights on them are completely wrong and will randomly be bright/dark regardless of where the light is coming from in KSP 1.8.1. 

I also found the cargo doors to be slightly too narrow and managed to create a perpetual energy machine by getting a wheel stuck outside the bay after opening the doors with said wheel deployed, resulting in unplanned disassembly and much explosions. If the doors were hinged the other way and both parts opened outwards then that would be an improvement to me.

[zer0Kerbal]

8 hours ago, jimmymcgoochie said:

Found the 2.5m cargo bays a few days ago and they're very useful, but the highlights on them are completely wrong and will randomly be bright/dark regardless of where the light is coming from in KSP 1.8.1.

thank you.

it is a model issue, and there is nothing I can do about it personally since the models were inherited and I am not a modeler.

If somebody wants to fix it, I will gladly accept a PR on github to update them. Hopefully somebody will, like they did for DaMichel's SphericalTanks (which created a texture issue, as in needed new ones )

8 hours ago, jimmymcgoochie said:

I also found the cargo doors to be slightly too narrow and managed to create a perpetual energy machine by getting a wheel stuck outside the bay after opening the doors with said wheel deployed, resulting in unplanned disassembly and much explosions. If the doors were hinged the other way and both parts opened outwards then that would be an improvement to me

the doors are too narrow. hmmm.... the actual cargo bays are very close to being the correct size (size2) for a 2.5m stack. Well, there are drawbacks to accordion-folding doors.

Again, I personally cannot do anything about the models since I enherited them, and my blender/unity skills are just barely being able to import things to look at the pretty pictures; even rotating the 3D models often exceeds my abilities.

I am more than willing to accept PR's on github for updated models/textures/patches.

What I can do, and am working on is including a 3.75m, 1.875m and 5.0m versions of these CargoBays, and have permission from the Original Author of SImpleCargoSolutions to adopt and modernize and curate that set of cargobays; which are also for rockets and not planes.

Wish I could be of more help on this.

[zer0Kerbal]

DaMichel's Fuselage Version 1.1.0.2

Superglue and Dusting

zer0Kerbal released this 08 Mar 2020

Version 1.1.0.2 -Superglue and Dusting

• cleaned part.cfg's of extraneous // comments
• added side nodes in a B9partswitch patch
• updated changelog to use updated KERBALCHANGELOG formatting.
• updated B9PartSwitch patches to use localization

---

Kerbal Space Program 1.8.1

 

#3

[zer0Kerbal]

Version 1.1.0.1 - Spit'n'Polish: CargoBays

zer0Kerbal released this 08 Mar 2020

Version 1.1.0.1 - Spit'n'Polish: CargoBays

• Introducing the 3.75m models!
  • 1.5m, 3m, 6m lengths
  • TechRequired = largeVolumeContainment
• thank you to BenjaminCronin for pointed out decorative right brace in changelogs. wite-out applied.
• Also dangling VERSION. superglued applied.
• url's updated and updated to 2.5m
• corrected several small typo's in the localization dictionary
• updated to new KERBALCHANGELOG formating (hopefully I got it right this time )
• ghostparts.cfg introduced. original three parts have had their internal part names changed. this file should prevent any Kraken attacks.
• added automatic GitHub action: Validate AVC .version files and corresponding shield to Readme's. Thank you @DasSkelett, and @HebaruSan
• moved FSAnimateGeneric into patch
• Updated integrated TweakScale patches (if you don't have TweakScale installed, won't show up and won't hurt anything)
• corrected tweakscale scale module (reduced scales available)
  • 2.5m parts : techRequired = largeVolumeContainment, specializedConstruction, largeVolumeContainment
  • 3.75m parts: techRequired = metaMaterials, largeVolumeContainment, metaMaterials

---

Kerbal Space Program 1.8.1

Edited March 9, 2020 by zer0Kerbal

[StarkRG]

I'm having a bit of an issue that I've tracked down to this mod and possibly (probably? prossibly?) is the result of running it in 1.9.1 when you've clearly stated that it's for 1.8.1 (that said, this is the only mod built for 1.8.1 that seems to be having problems, presumably there are others, they're just minor). B9 Part Switch throws an error when attempting to load parts from this mod, in particular it says "No tank type named 'KGExSupport' exists". I tracked down the offending ModuleManager config to the B9FuelSwitch configs for this mod which do have a "tankType = KGExSupport" line, however it's in a "SUBTYPE:NEEDS[KGEx]". This confused me because I didn't think I had any mods which might be labelled "KGEx" and should therefore not be loaded, however I did find a directory called that which contained "DockingPortDescriptions" and "ShieldedPicoPort" which I did just install, so I assume that's what it's picking up on, however neither of those have a plugin which could create such a tankType and, therefore, there's no "KGExSupport" for it to find. Since such a plugin doesn't exist, I've gone ahead and removed those sections from the config (as well as the others looking for KGEx for good measure, even though they weren't causing an issue) and it seems to now be working. I assume changing the name of that directory, or just moving them to be directly under GameData would also have solved it, but that would have been problematic for CKAN.

Complete exception follows (in case that's helpful, though I kinda doubt it):

 

 

 

 

Spoiler

Module ModuleB9PartSwitch threw during OnLoad: System.Exception: Fatal exception while loading fields on module ModuleB9PartSwitch on part  ---> System.Exception: Exception while loading field subtypes on type B9PartSwitch.ModuleB9PartSwitch ---> System.Exception: Exception while loading fields on subtype PartSubtype EC+MP ---> System.Exception: Exception while loading field tankType on type B9PartSwitch.PartSubtype ---> System.Collections.Generic.KeyNotFoundException: No tank type named 'KGExSupport' exists
  at B9PartSwitch.B9TankSettings.GetTankType (System.String name) [0x00030] in <9d3fe92d8f32452f86b4a1298323bc91>:0 
  at B9PartSwitch.TankTypeValueParser.Parse (System.String value) [0x0000b] in <9d3fe92d8f32452f86b4a1298323bc91>:0 
  at B9PartSwitch.Fishbones.NodeDataMappers.ValueScalarMapper.Load (System.Object& fieldValue, ConfigNode node, B9PartSwitch.Fishbones.Context.OperationContext context) [0x00022] in <9d3fe92d8f32452f86b4a1298323bc91>:0 
  at B9PartSwitch.Fishbones.NodeDataField.Load (ConfigNode node, B9PartSwitch.Fishbones.Context.OperationContext context) [0x00043] in <9d3fe92d8f32452f86b4a1298323bc91>:0 
  at B9PartSwitch.Fishbones.NodeDataList.Load (ConfigNode node, B9PartSwitch.Fishbones.Context.OperationContext context) [0x00025] in <9d3fe92d8f32452f86b4a1298323bc91>:0 
   --- End of inner exception stack trace ---
  at B9PartSwitch.Fishbones.NodeDataList.Load (ConfigNode node, B9PartSwitch.Fishbones.Context.OperationContext context) [0x00058] in <9d3fe92d8f32452f86b4a1298323bc91>:0 
  at B9PartSwitch.Fishbones.NodeDataObjectExtensions.LoadFields (System.Object obj, ConfigNode node, B9PartSwitch.Fishbones.Context.OperationContext context) [0x00033] in <9d3fe92d8f32452f86b4a1298323bc91>:0 
  at B9PartSwitch.PartSubtype.Load (ConfigNode node, B9PartSwitch.Fishbones.Context.OperationContext context) [0x00000] in <9d3fe92d8f32452f86b4a1298323bc91>:0 
   --- End of inner exception stack trace ---
  at B9PartSwitch.PartSubtype.Load (ConfigNode node, B9PartSwitch.Fishbones.Context.OperationContext context) [0x0001d] in <9d3fe92d8f32452f86b4a1298323bc91>:0 
  at B9PartSwitch.Fishbones.Parsers.NodeObjectWrapperIContextualNode.Load (System.Object& obj, ConfigNode node, B9PartSwitch.Fishbones.Context.OperationContext context) [0x00038] in <9d3fe92d8f32452f86b4a1298323bc91>:0 
  at B9PartSwitch.Fishbones.NodeDataMappers.NodeListMapper.Load (System.Object& fieldValue, ConfigNode node, B9PartSwitch.Fishbones.Context.OperationContext context) [0x0009e] in <9d3fe92d8f32452f86b4a1298323bc91>:0 
  at B9PartSwitch.Fishbones.NodeDataField.Load (ConfigNode node, B9PartSwitch.Fishbones.Context.OperationContext context) [0x00043] in <9d3fe92d8f32452f86b4a1298323bc91>:0 
  at B9PartSwitch.Fishbones.NodeDataList.Load (ConfigNode node, B9PartSwitch.Fishbones.Context.OperationContext context) [0x00025] in <9d3fe92d8f32452f86b4a1298323bc91>:0 
   --- End of inner exception stack trace ---
  at B9PartSwitch.Fishbones.NodeDataList.Load (ConfigNode node, B9PartSwitch.Fishbones.Context.OperationContext context) [0x00058] in <9d3fe92d8f32452f86b4a1298323bc91>:0 
  at B9PartSwitch.Fishbones.NodeDataObjectExtensions.LoadFields (System.Object obj, ConfigNode node, B9PartSwitch.Fishbones.Context.OperationContext context) [0x00033] in <9d3fe92d8f32452f86b4a1298323bc91>:0 
  at B9PartSwitch.CustomPartModule.OnLoad (ConfigNode node) [0x000ea] in <9d3fe92d8f32452f86b4a1298323bc91>:0 
   --- End of inner exception stack trace ---
  at B9PartSwitch.CustomPartModule.OnLoad (ConfigNode node) [0x0010f] in <9d3fe92d8f32452f86b4a1298323bc91>:0 
  at PartModule.Load (ConfigNode node) [0x001ab] in <ac04291822974a138f007b85091a10d0>:0 

 

 

[zer0Kerbal]

7 hours ago, StarkRG said:

I'm having a bit of an issue

thank you.

interesting.

• Which of the 4 DaMichel's (AeroRadial, Fuselage, CargoBays, SphericalTanks) (or all) do you have installed?
• which version?
• installed manually or via CKAN?
•  

I have been procrastinating releasing KGEx, which is just a small mod that contains one or two .cfg's that add functionality to my mods. I have been procrastinating its release.

Normally there shouldn't be any issue with this - but since I have at least three other mods that install into GameData/KGex/, it does become an issue.

MM :NEEDS [KGEx] looks for a .dll named 'KGEx', a :FOR[KGEx], or (the offending issue) a directory in GameData named, you guessed it 'KGEx'.

I will fix this; until it is released you can do what you did or

install this(Now on Spacedock/Curseforge/CKAN):

https://github.com/zer0Kerbal/KGEx/releases/tag/1.0.0.0

SOURCE: GitHub
LICENSE:

Edited March 15, 2020 by zer0Kerbal

[StarkRG]

I have all installed through CKAN, so whatever versions are currently listed there.

[zer0Kerbal]

1 hour ago, StarkRG said:

I have all installed through CKAN, so whatever versions are currently listed there.

Thank you - was just being thorough.

 

[TrueMetis]

On 2/19/2020 at 9:58 AM, Jiraiyah said:

5 errors related to SphericalTanks/Patches/B9FuelSwitch-Karbonite.cfg

is there any importance into this or not? @zer0Kerbal

I'm having the same issue though with 5 errors related to SphericalTanks/Patches/B9FuelSwitch-Kerbalism.cfg

It's not causing any serious issue afaict, but it's still somewhat annoying and I can't figure out how to deal with it.

[zer0Kerbal]

9 hours ago, TrueMetis said:

I'm having the same issue though with 5 errors related to SphericalTanks/Patches/B9FuelSwitch-Kerbalism.cfg

It's not causing any serious issue afaict, but it's still somewhat annoying and I can't figure out how to deal with it.

I've been meaning to release an update for DST - let's see if I can cut the mustard and get it out by the weekend.

[Corax]

Seeing the issue has already been reported by TrueMetis, here is the offending part of the patch:

@PART[DM-SphericalTank-125-70,DM-SphericalTank-125-140,DM-SphericalTank-125-111,DM-SphericalTank-125-88,DM-SphericalTank-125-55]:NEEDS[B9PartSwitch,Kerbalism,DaMichel/SphericalTanks]:AFTER[SphericalTanks]
{
@MODULE[ModuleB9PartSwitch]:HAS[#moduleID[SphericalTankFuelSwitch]
{



':HAS[#moduleID[SphericalTankFuelSwitch]' is missing its closing ']' bracket



Sorry for (probably, can't even preview ATM) lousy formatting, the lovely InvisionForum software is acting weird again...

[KIMCHI]

[ERR 07:53:14.379] Error - Skipping a patch subnode with unbalanced square brackets or a space (replace them with a '?') in @PART[DM-SphericalTank-125-70,DM-SphericalTank-125-140,DM-SphericalTank-125-111,DM-SphericalTank-125-88,DM-SphericalTank-125-55]:NEEDS[B9PartSwitch,Karbonite,DaMichel/SphericalTanks]:AFTER[SphericalTanks] : 
@MODULE[ModuleB9PartSwitch]:HAS[#moduleID[SphericalTankFuelSwitch]

 

This is the error log

[CFYL]

Is this an issue or just shaders?

cuz it happens when I first lands, and it failed, so I tried again, and the black and white stripes occur again.

as you see in the middle of the cargo bay, weird colors.

the bay doors opened normally and my rover successfully drove out, it’s just the color.

1.8.1 manually installed.

currently no other of my vessels use these bays so I wanna ask if it was just fine, regarding codes, though it doesn’t look nice.

will upload log a bit later.

EDIT:LOG. Searched for DaMichel in the KSP.log

I saw no ERR or WRN when I scrolled through it though.

DaMichel
[LOG 18:37:01.910] Load(Texture): DaMichel/CargoBays/Assets/bay_colormap
[LOG 18:37:01.965] Load(Texture): DaMichel/CargoBays/Assets/bay_normals_NRM
[LOG 18:38:10.090] Load(Model): DaMichel/CargoBays/Assets/dm-round-cargo-bay1
[LOG 18:38:10.385] Load(Model): DaMichel/CargoBays/Assets/dm-round-cargo-bay2
[LOG 18:38:10.417] Load(Model): DaMichel/CargoBays/Assets/dm-round-cargo-bay3
[LOG 18:38:43.797] Config(KERBALCHANGELOG) DaMichel/CargoBays/Changelog/KERBALCHANGELOG
[LOG 18:38:43.797] Config(Localization) DaMichel/CargoBays/Localization/en-us/Localization
[LOG 18:38:43.797] Config(Localization) DaMichel/CargoBays/Localization/es-es/Localization
[LOG 18:38:43.797] Config(Localization) DaMichel/CargoBays/Localization/fr-fr/Localization
[LOG 18:38:43.797] Config(Localization) DaMichel/CargoBays/Localization/it-it/Localization
[LOG 18:38:43.797] Config(PART) DaMichel/CargoBays/Parts/250/dm-round-cargobay250-1/dm-round-cargobay250-1
[LOG 18:38:43.797] Config(PART) DaMichel/CargoBays/Parts/250/dm-round-cargobay250-2/dm-round-cargobay250-2
[LOG 18:38:43.797] Config(PART) DaMichel/CargoBays/Parts/250/dm-round-cargobay250-4/dm-round-cargobay250-4
[LOG 18:38:43.797] Config(PART) DaMichel/CargoBays/Parts/375/dm-round-cargobay375-1/dm-round-cargobay375-1
[LOG 18:38:43.797] Config(PART) DaMichel/CargoBays/Parts/375/dm-round-cargobay375-2/dm-round-cargobay375-2
[LOG 18:38:43.797] Config(PART) DaMichel/CargoBays/Parts/375/dm-round-cargobay375-4/dm-round-cargobay375-4
[LOG 18:38:43.797] Config(@PART[dm-round-cargobay???-1]:NEEDS[FireSpitter,DaMichel/CargoBays]:FOR[CargoBays]) DaMichel/CargoBays/Patches/FSAnimate/@PART[dm-round-cargobay???-1]:NEEDS[FireSpitter,DaMichel/CargoBays]:FOR[CargoBays]
[LOG 18:38:43.797] Config(+PART[dm-round-cargobay250-1,dm-round-cargobay250-2,dm-round-cargobay250-3]:NEEDS[DaMichel/CargoBays]:FOR[CargoBays]) DaMichel/CargoBays/Patches/ghostparts/+PART[dm-round-cargobay250-1,dm-round-cargobay250-2,dm-round-cargobay250-3]:NEEDS[DaMichel/CargoBays]:FOR[CargoBays]
  DaMichel
[LOG 20:26:24.585] Deleting root node in file DaMichel/CargoBays/Patches/FSAnimate node: @PART[dm-round-cargobay???-1]:NEEDS[FireSpitter,DaMichel/CargoBays]:FOR[CargoBays] as it can't satisfy its NEEDS
[LOG 20:26:25.243] Applying update FerramAerospaceResearch/_FARPartModule/@PART[*]:HAS[@MODULE[ModuleCargoBay]] to DaMichel/CargoBays/Parts/250/dm-round-cargobay250-1.cfg/PART[dm-round-cargobay250-1]
[LOG 20:26:25.244] Applying update FerramAerospaceResearch/_FARPartModule/@PART[*]:HAS[@MODULE[ModuleCargoBay]] to DaMichel/CargoBays/Parts/250/dm-round-cargobay250-2.cfg/PART[dm-round-cargobay250-2]
[LOG 20:26:25.245] Applying update FerramAerospaceResearch/_FARPartModule/@PART[*]:HAS[@MODULE[ModuleCargoBay]] to DaMichel/CargoBays/Parts/250/dm-round-cargobay250-4.cfg/PART[dm-round-cargobay250-4]
[LOG 20:26:25.245] Applying update FerramAerospaceResearch/_FARPartModule/@PART[*]:HAS[@MODULE[ModuleCargoBay]] to DaMichel/CargoBays/Parts/375/dm-round-cargobay375-1.cfg/PART[dm-round-cargobay375-1]
[LOG 20:26:25.245] Applying update FerramAerospaceResearch/_FARPartModule/@PART[*]:HAS[@MODULE[ModuleCargoBay]] to DaMichel/CargoBays/Parts/375/dm-round-cargobay375-2.cfg/PART[dm-round-cargobay375-2]
[LOG 20:26:25.245] Applying update FerramAerospaceResearch/_FARPartModule/@PART[*]:HAS[@MODULE[ModuleCargoBay]] to DaMichel/CargoBays/Parts/375/dm-round-cargobay375-4.cfg/PART[dm-round-cargobay375-4]
[LOG 20:26:31.203] Applying copy DaMichel/CargoBays/Patches/ghostparts/+PART[dm-round-cargobay250-1,dm-round-cargobay250-2,dm-round-cargobay250-3]:NEEDS[DaMichel/CargoBays]:FOR[CargoBays] to DaMichel/CargoBays/Parts/250/dm-round-cargobay250-1.cfg/PART[dm-round-cargobay250-1]
[LOG 20:26:31.204] Applying copy DaMichel/CargoBays/Patches/ghostparts/+PART[dm-round-cargobay250-1,dm-round-cargobay250-2,dm-round-cargobay250-3]:NEEDS[DaMichel/CargoBays]:FOR[CargoBays] to DaMichel/CargoBays/Parts/250/dm-round-cargobay250-2.cfg/PART[dm-round-cargobay250-2]
[LOG 20:26:31.206] :BEFORE[DAMICHEL] pass
[LOG 20:26:31.206] :FOR[DAMICHEL] pass
[LOG 20:26:31.206] :AFTER[DAMICHEL] pass
[LOG 20:26:31.513] Applying update FerramAerospaceResearch/_FARPartModule/@PART[*]:HAS[!MODULE[LaunchClamp]]:FOR[FerramAerospaceResearch] to DaMichel/CargoBays/Parts/250/dm-round-cargobay250-1.cfg/PART[dm-round-cargobay250-1]
[LOG 20:26:31.514] Applying update FerramAerospaceResearch/_FARPartModule/@PART[*]:HAS[!MODULE[LaunchClamp]]:FOR[FerramAerospaceResearch] to DaMichel/CargoBays/Parts/250/dm-round-cargobay250-1.cfg/PART[dm-round-cargobay-1]
[LOG 20:26:31.514] Applying update FerramAerospaceResearch/_FARPartModule/@PART[*]:HAS[!MODULE[LaunchClamp]]:FOR[FerramAerospaceResearch] to DaMichel/CargoBays/Parts/250/dm-round-cargobay250-2.cfg/PART[dm-round-cargobay250-2]
[LOG 20:26:31.515] Applying update FerramAerospaceResearch/_FARPartModule/@PART[*]:HAS[!MODULE[LaunchClamp]]:FOR[FerramAerospaceResearch] to DaMichel/CargoBays/Parts/250/dm-round-cargobay250-2.cfg/PART[dm-round-cargobay-2]
[LOG 20:26:31.516] Applying update FerramAerospaceResearch/_FARPartModule/@PART[*]:HAS[!MODULE[LaunchClamp]]:FOR[FerramAerospaceResearch] to DaMichel/CargoBays/Parts/250/dm-round-cargobay250-4.cfg/PART[dm-round-cargobay250-4]
[LOG 20:26:31.517] Applying update FerramAerospaceResearch/_FARPartModule/@PART[*]:HAS[!MODULE[LaunchClamp]]:FOR[FerramAerospaceResearch] to DaMichel/CargoBays/Parts/375/dm-round-cargobay375-1.cfg/PART[dm-round-cargobay375-1]
[LOG 20:26:31.517] Applying update FerramAerospaceResearch/_FARPartModule/@PART[*]:HAS[!MODULE[LaunchClamp]]:FOR[FerramAerospaceResearch] to DaMichel/CargoBays/Parts/375/dm-round-cargobay375-2.cfg/PART[dm-round-cargobay375-2]
[LOG 20:26:31.517] Applying update FerramAerospaceResearch/_FARPartModule/@PART[*]:HAS[!MODULE[LaunchClamp]]:FOR[FerramAerospaceResearch] to DaMichel/CargoBays/Parts/375/dm-round-cargobay375-4.cfg/PART[dm-round-cargobay375-4]
[LOG 20:26:32.222] Applying update FerramAerospaceResearch/_FARPartModule/@PART[*]:HAS[!MODULE[FARWingAerodynamicModel],!MODULE[FARControllableSurface]]:AFTER[FerramAerospaceResearch] to DaMichel/CargoBays/Parts/250/dm-round-cargobay250-1.cfg/PART[dm-round-cargobay250-1]
[LOG 20:26:32.223] Applying update FerramAerospaceResearch/_FARPartModule/@PART[*]:HAS[!MODULE[FARWingAerodynamicModel],!MODULE[FARControllableSurface]]:AFTER[FerramAerospaceResearch] to DaMichel/CargoBays/Parts/250/dm-round-cargobay250-1.cfg/PART[dm-round-cargobay-1]
[LOG 20:26:32.223] Applying update FerramAerospaceResearch/_FARPartModule/@PART[*]:HAS[!MODULE[FARWingAerodynamicModel],!MODULE[FARControllableSurface]]:AFTER[FerramAerospaceResearch] to DaMichel/CargoBays/Parts/250/dm-round-cargobay250-2.cfg/PART[dm-round-cargobay250-2]
[LOG 20:26:32.223] Applying update FerramAerospaceResearch/_FARPartModule/@PART[*]:HAS[!MODULE[FARWingAerodynamicModel],!MODULE[FARControllableSurface]]:AFTER[FerramAerospaceResearch] to DaMichel/CargoBays/Parts/250/dm-round-cargobay250-2.cfg/PART[dm-round-cargobay-2]
[LOG 20:26:32.223] Applying update FerramAerospaceResearch/_FARPartModule/@PART[*]:HAS[!MODULE[FARWingAerodynamicModel],!MODULE[FARControllableSurface]]:AFTER[FerramAerospaceResearch] to DaMichel/CargoBays/Parts/250/dm-round-cargobay250-4.cfg/PART[dm-round-cargobay250-4]
[LOG 20:26:32.224] Applying update FerramAerospaceResearch/_FARPartModule/@PART[*]:HAS[!MODULE[FARWingAerodynamicModel],!MODULE[FARControllableSurface]]:AFTER[FerramAerospaceResearch] to DaMichel/CargoBays/Parts/375/dm-round-cargobay375-1.cfg/PART[dm-round-cargobay375-1]
[LOG 20:26:32.224] Applying update FerramAerospaceResearch/_FARPartModule/@PART[*]:HAS[!MODULE[FARWingAerodynamicModel],!MODULE[FARControllableSurface]]:AFTER[FerramAerospaceResearch] to DaMichel/CargoBays/Parts/375/dm-round-cargobay375-2.cfg/PART[dm-round-cargobay375-2]
[LOG 20:26:32.224] Applying update FerramAerospaceResearch/_FARPartModule/@PART[*]:HAS[!MODULE[FARWingAerodynamicModel],!MODULE[FARControllableSurface]]:AFTER[FerramAerospaceResearch] to DaMichel/CargoBays/Parts/375/dm-round-cargobay375-4.cfg/PART[dm-round-cargobay375-4]
[LOG 20:26:33.395] :LAST[DAMICHEL] pass
[LOG 18:38:48.119] PartLoader: Compiling Part 'DaMichel/CargoBays/Parts/250/dm-round-cargobay250-1/dm-round-cargobay250-1'
[LOG 18:38:48.415] PartLoader: Compiling Part 'DaMichel/CargoBays/Parts/250/dm-round-cargobay250-1/dm-round-cargobay-1'
[LOG 18:38:48.441] PartLoader: Compiling Part 'DaMichel/CargoBays/Parts/250/dm-round-cargobay250-2/dm-round-cargobay250-2'
[LOG 18:38:48.468] PartLoader: Compiling Part 'DaMichel/CargoBays/Parts/250/dm-round-cargobay250-2/dm-round-cargobay-2'
[LOG 18:38:48.493] PartLoader: Compiling Part 'DaMichel/CargoBays/Parts/250/dm-round-cargobay250-4/dm-round-cargobay250-4'
[LOG 18:38:48.524] PartLoader: Compiling Part 'DaMichel/CargoBays/Parts/375/dm-round-cargobay375-1/dm-round-cargobay375-1'
[LOG 18:38:48.550] PartLoader: Compiling Part 'DaMichel/CargoBays/Parts/375/dm-round-cargobay375-2/dm-round-cargobay375-2'
[LOG 18:38:48.573] PartLoader: Compiling Part 'DaMichel/CargoBays/Parts/375/dm-round-cargobay375-4/dm-round-cargobay375-4'
 

Version is 1.1.0.1, downloaded via space dock.

EDIT2: I tried again, removing all other mods as this has no dependencies. happened again for all of the 6 cargo bays as I launched them on a SRB into the atmosphere for clearer views. Full log this time:

[Full log file removed by a moderator]

I don't have much spare space in my computer so I could only move mods out of the KSP directory, but not able to use an all-clear version. Pictures shown here: Weird stripes of black and white.

Edited August 29, 2021 by James Kerman
Full log snipped to prevent issues

[SkiRich]

Hi, I found an issue with your Cargo Bay mod.

Latest game 1.9.1 version

When loaded with Hangar Extender and Tweakscale, if I attach a cargo bay to my model, the right click context menu never opens anymore and I need to restart.

Looking at the log file, it looks like Hangar extender goes into a virtual error exception after that.

It doesnt happen when tweekscale is not loaded.  So I dont know where the issue is.  Could be tweakscale, or hangar extender with your mod.

I had to de-install your mod to have my game work right.

If you can look into it that would be great, I like your cargo bays.

[Lisias]

On 5/19/2020 at 6:56 PM, SkiRich said:

Hi, I found an issue with your Cargo Bay mod.

Latest game 1.9.1 version

When loaded with Hangar Extender and Tweakscale, if I attach a cargo bay to my model, the right click context menu never opens anymore and I need to restart.

Looking at the log file, it looks like Hangar extender goes into a virtual error exception after that.

It doesnt happen when tweekscale is not loaded.  So I dont know where the issue is.  Could be tweakscale, or hangar extender with your mod.

I had to de-install your mod to have my game work right.

If you can look into it that would be great, I like your cargo bays.

Publish the KSP.log and I will give it a look.

[zer0Kerbal]

On 5/12/2020 at 2:33 PM, AllenLi said:

Is this an issue or just shaders?

thank you - have looked and here is what I found:

1. I need to move tweakscale out to separate patch - love to include it - hate to have ANY error messages in log files - even innocuous ones like 'module not found'
2. I need to fix the drag cubes on dm-round-cargobay250-1 and dm-round-cargobay375-1 need correction
3. [ModuleCargoBay]: Module ModuleToggleCrossfeed is not an IScalarModule -> this is new to me and will look into
4. don't have a clue about this one (spoiler) - and don't believe is related to DM Cargo Bays - just included it to try and be helpful:
   Spoiler

   [LOG 09:40:43.966] [PlanetariumCamera]: Focus: Kerbin
   [ERR 09:40:44.072] Exception handling event onPlanetariumTargetChange in class KnowledgeBase:System.NullReferenceException
     at (wrapper managed-to-native) UnityEngine.Component.get_transform(UnityEngine.Component)
     at KSP.UI.Screens.KbApp_PlanetResources.ActivateApp (MapObject target) [0x0007d] in <394a98b9c7624adc895c04290da62640>:0
     at KSP.UI.Screens.KnowledgeBase.ActivateApps (KSP.UI.Screens.KnowledgeBase+KbTargetType targetType, MapObject target) [0x000fa] in <394a98b9c7624adc895c04290da62640>:0
     at KSP.UI.Screens.KnowledgeBase.OnMapFocusChange (MapObject target) [0x000f4] in <394a98b9c7624adc895c04290da62640>:0
     at EventData`1[T].Fire (T data) [0x000b0] in <394a98b9c7624adc895c04290da62640>:0

   [EXC 09:40:44.222] NullReferenceException
       KSP.UI.Screens.KbApp_PlanetResources.ActivateApp (MapObject target) (at <394a98b9c7624adc895c04290da62640>:0)
       KSP.UI.Screens.KnowledgeBase.ActivateApps (KSP.UI.Screens.KnowledgeBase+KbTargetType targetType, MapObject target) (at <394a98b9c7624adc895c04290da62640>:0)
       KSP.UI.Screens.KnowledgeBase.OnMapFocusChange (MapObject target) (at <394a98b9c7624adc895c04290da62640>:0)
       EventData`1[T].Fire (T data) (at <394a98b9c7624adc895c04290da62640>:0)
       UnityEngine.Debug:LogException(Exception)
       EventData`1:Fire(MapObject)
       PlanetariumCamera:SetTarget(MapObject)
       PlanetariumCamera:RemoveTarget(MapObject)
       MapView:OnDestroy()

5. that is all.

None of these explain what is going on. It has to be an outside issue or a texture issue. Since these are old textures - (really old) that might be the issue. I will look and see if I can update them, but my texturefu is weak and pathetic.      

On 5/19/2020 at 9:56 PM, SkiRich said:

Hi, I found an issue with your Cargo Bay mod.

Latest game 1.9.1 version

When loaded with Hangar Extender and Tweakscale, if I attach a cargo bay to my model, the right click context menu never opens anymore and I need to restart.

Looking at the log file, it looks like Hangar extender goes into a virtual error exception after that.

It doesnt happen when tweekscale is not loaded.  So I dont know where the issue is.  Could be tweakscale, or hangar extender with your mod.

I had to de-install your mod to have my game work right.

If you can look into it that would be great, I like your cargo bays.

hmmm.. interesting. Logs would be helpful.

On 5/21/2020 at 4:03 AM, Lisias said:

Publish the KSP.log and I will give it a look.

Appreciate @Lisias

[Lisias]

3 hours ago, zer0Kerbal said:

Appreciate @Lisias

Welcome! Kick me if you need some assistance on understanding the TweakScale interaction on the bug. If the thing explodes inside TweakScale, I can diagnose the Exception easily!

[CFYL]

On 5/23/2020 at 1:19 AM, zer0Kerbal said:

•  
• don't have a clue about this one (spoiler) - and don't believe is related to DM Cargo Bays - just included it to try and be helpful:
    Reveal hidden contents

  [LOG 09:40:43.966] [PlanetariumCamera]: Focus: Kerbin
  [ERR 09:40:44.072] Exception handling event onPlanetariumTargetChange in class KnowledgeBase:System.NullReferenceException
    at (wrapper managed-to-native) UnityEngine.Component.get_transform(UnityEngine.Component)
    at KSP.UI.Screens.KbApp_PlanetResources.ActivateApp (MapObject target) [0x0007d] in <394a98b9c7624adc895c04290da62640>:0
    at KSP.UI.Screens.KnowledgeBase.ActivateApps (KSP.UI.Screens.KnowledgeBase+KbTargetType targetType, MapObject target) [0x000fa] in <394a98b9c7624adc895c04290da62640>:0
    at KSP.UI.Screens.KnowledgeBase.OnMapFocusChange (MapObject target) [0x000f4] in <394a98b9c7624adc895c04290da62640>:0
    at EventData`1[T].Fire (T data) [0x000b0] in <394a98b9c7624adc895c04290da62640>:0

  [EXC 09:40:44.222] NullReferenceException
      KSP.UI.Screens.KbApp_PlanetResources.ActivateApp (MapObject target) (at <394a98b9c7624adc895c04290da62640>:0)
      KSP.UI.Screens.KnowledgeBase.ActivateApps (KSP.UI.Screens.KnowledgeBase+KbTargetType targetType, MapObject target) (at <394a98b9c7624adc895c04290da62640>:0)
      KSP.UI.Screens.KnowledgeBase.OnMapFocusChange (MapObject target) (at <394a98b9c7624adc895c04290da62640>:0)
      EventData`1[T].Fire (T data) (at <394a98b9c7624adc895c04290da62640>:0)
      UnityEngine.Debug:LogException(Exception)
      EventData`1:Fire(MapObject)
      PlanetariumCamera:SetTarget(MapObject)
      PlanetariumCamera:RemoveTarget(MapObject)
      MapView:OnDestroy()

• that is all.

I think this is because I forced quit KSP, but I don't know about such codes.

[zer0Kerbal]

33 minutes ago, AllenLi said:

I think this is because I forced quit KSP, but I don't know about such codes.

I don't think so - I force quit (<ALT><F4>) all the time and don't see codes like this. Will file it away in the back of my brain and see what it stumbles across.

[Falco01]

I noticed some visual issues on the fuselage parts, I won't bother with screenshots as they are already reported. 
The cause is a normal issue on the model, they are facing the wrong way thus KSP treat it as the back of a face, not the front if that make sense. This either comes from the normal map itself or the model packed in the .mu. What need to be done is to load the model into a 3d modeling software like Blender and recalculate the normals.
I'd do it but I lack the knowledge to put back the edited model into a usable format for the game using Unity or tweak/bake a normal map properly (nor do I have the time to learn due to my thesis)