Professor K

Well, it's going to be difficult, maybe even impossible, to diagnose the issue without details, but here's a trick that might get you past it for your current ship. You can change what loop both radiators and heat producers are part of while in flight, so change your engine's heat loop to a higher number, then change enough radiators to that same number and see if you can get it to work. -K

No, not at all. I'm very much enjoying the mod. It's the fact that I like it that has me posting, tracking down/trying to fix bugs, submitting Github issues, etc. If I didn't like it I wouldn't bother with all that! -K

They have transparency, but the ones I have examples of are all a few pixels wide and a few thousand high, with the image running from the inner edge of the ring to the outside, repeated many times, so transparent areas produce a gap in the entire ring at that point. -K

Does anyone know if it would be possible to do a "broken" ring setup ala the planet Moth in Alan Dean Foster's Commonwealth novels and if so, how to go about it? "Its name originates from its incomplete ring system, which has led to it being referred to as a winged planet." Here's a (bad) illustration from one of the older novel covers: -K

It seems odd to set/change the SMAs in the OPX-S body configs and then change them again with a patch. As an example: OPM Hale.cfg: SMA = 10488231 OPX-S 03-Hale.cfg: SMA = 12169413 After MoonDistance.cfg: SMA = 20359427.949 Wouldn't it have been simpler to just set it to the final number in the 03-Hale.cfg file? -K

I tracked down the issue with this. It's not the elliptical orbit of the asteroids, but the duplicate SMAs of multiple bodies across OPM and OPX-*. There is a notation of an issue (as yet unresolved) on the Kopernicus GitHub, Issue 605 that explains that if there is more than one celestial body with the exact same SMA, the stock KSP code that runs the Sentinel Telescope will throw an exception and stop working. Between OPM and the OPX-* series, there are multiple sets of duplicate SMAs: Kerbin & Kret (OPX-Inner) Bop & Klip (OPX-Jool) Polta & Priax (OPX-Urlum) Jool, Euribanne & Palloocus (OPX-Jool) I fixed the issue for my system by adjusting the SMA of one of each pair by 1 meter. (Up by one for the one of Jool threesome and down by one for the other). The Sentinel scopes immediately started working again. -K

Is the MoonDistance.cfg file in OPX-SarnusPlus\KopernicusConfigs supposed to be for use with a specific mod? It's increasing the SMA of a bunch of Sarnus's moons via a multiplier (rather than a specific number), but only a couple are tagged with a "NEEDS" for a specific mod. -K

I've narrowed this down to using the Uniform distributionType. When using Uniform I get the errors above and the overlays do not appear on the map view or in the tracking station for those bodies. When I switch the config to use the Spherical distributionType with the altUpperBound set to the body's SOI minus it's Radius, everything works as expected. -K

That seems to have done the trick, thank you! -K

I'm seeing an error in my logs from Waterfall during startup: [ERR 11:34:28.526] [Waterfall][Template Libary]: Exception loading template waterfall-srb-smoke-1. This is likely a config error Has anyone else seen this one (and better yet, have a fix?) The file (waterfall-srb-smoke-1.cfg) is present, doesn't seem to be corrupt, truncated, etc and all the brackets are balanced.

But you can re-texture or even replace (which is what OPX does) a planet without renaming it, that's why I'm unsure of the reason for the rename. Hopefully the mod author will stop by and let us know. -K

I'll second the Jool vs BetterJool issue, I've noticed a number of errors popping up in my logs related to the name change, mainly around Parallax and Scatterer. Nothing that's stopped the game from loading (although I've yet to visit Jool in this save) but I find myself wondering as to the purpose of the rename. -K

I had a new set of errors pop up in my KSP log yesterday which looks like they're coming from Spacedust. I have not added or modified any Spacedust configs recently, but I did move a probe with a gas scanner on it to a new body. The move was from a moon of Kerbin added by the Outer Kerbin mod called Phybi to it's moon, Iszmi (from a moon of Kerbin to that moon's moon). The scanner appeared to be working correctly. I don't think I checked the overlays at the time. At the moment I'm just looking for advice on whether this is something I need to trouble shoot with the Spacedust config for the body or if this is an internal error I should put in an issue report for. -K [ERR 12:42:41.291] Exception handling event OnMapFocusChange in class MapOverlay:System.InvalidCastException: Specified cast is not valid. at SpaceDust.FieldCollision.CreateCollision (SpaceDust.ResourceBand band, UnityEngine.Transform parent) [0x0007e] in <4258eaadb1df4e0b910cd13847f31a48>:0 at SpaceDust.ParticleField.CreateField (SpaceDust.ResourceBand band, System.String resourceName, System.Boolean discovered, System.Boolean identified, UnityEngine.Vector3 scaledSpacePosition) [0x000a5] in <4258eaadb1df4e0b910cd13847f31a48>:0 at SpaceDust.MapOverlay.GenerateBodyField (System.String resourceName, CelestialBody body) [0x00184] in <4258eaadb1df4e0b910cd13847f31a48>:0 at SpaceDust.MapOverlay.RegenerateBodyFields (CelestialBody targetObject) [0x0002e] in <4258eaadb1df4e0b910cd13847f31a48>:0 at SpaceDust.MapOverlay.OnMapFocusChange (MapObject mapObject) [0x0004a] in <4258eaadb1df4e0b910cd13847f31a48>:0 at EventData`1[T].Fire (T data) [0x000b0] in <4b449f2841f84227adfaad3149c8fdba>:0 [EXC 12:42:41.291] InvalidCastException: Specified cast is not valid. SpaceDust.FieldCollision.CreateCollision (SpaceDust.ResourceBand band, UnityEngine.Transform parent) (at <4258eaadb1df4e0b910cd13847f31a48>:0) SpaceDust.ParticleField.CreateField (SpaceDust.ResourceBand band, System.String resourceName, System.Boolean discovered, System.Boolean identified, UnityEngine.Vector3 scaledSpacePosition) (at <4258eaadb1df4e0b910cd13847f31a48>:0) SpaceDust.MapOverlay.GenerateBodyField (System.String resourceName, CelestialBody body) (at <4258eaadb1df4e0b910cd13847f31a48>:0) SpaceDust.MapOverlay.RegenerateBodyFields (CelestialBody targetObject) (at <4258eaadb1df4e0b910cd13847f31a48>:0) SpaceDust.MapOverlay.OnMapFocusChange (MapObject mapObject) (at <4258eaadb1df4e0b910cd13847f31a48>:0) EventData`1[T].Fire (T data) (at <4b449f2841f84227adfaad3149c8fdba>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) KSPe.Util.Log.UnityLogDecorator:UnityEngine.ILogHandler.LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:LogException(Exception) EventData`1:Fire(MapObject) PlanetariumCamera:SetTarget(MapObject) KSP.UI.Screens.SpaceTracking:SetVessel(Vessel, Boolean) KSP.UI.Screens.SpaceTracking:OnSceneLoadRequested(GameScenes) EventData`1:Fire(GameScenes) HighLogic:SetLoadSceneEventsAndFlags(GameScenes, Boolean) HighLogic:LoadScene(GameScenes) FlightDriver:StartAndFocusVessel(String, Int32) KSP.UI.Screens.SpaceTracking:FlyVessel(Vessel) KSP.UI.Screens.SpaceTracking:BtnOnClick_FlySelectedVessel() UnityEngine.EventSystems.EventSystem:Update() Config file:

That may have been about right. I've since started a different save and haven't gotten to that many bodies yet, but I'm getting the error below in KSP.LOG even with only 4 or 5 bodies in the list. I "think" it's coming from the Better Tracking code. [ERR 12:15:07.340] Exception loading ScenarioModule Tracking_Persistence: System.ArgumentOutOfRangeException: Index must be within the bounds of the List. Parameter name: index at System.ThrowHelper.ThrowArgumentOutOfRangeException (System.ExceptionArgument argument, System.ExceptionResource resource) [0x00029] in <9577ac7a62ef43179789031239ba8798>:0 at System.Collections.Generic.List`1[T].Insert (System.Int32 index, T item) [0x00009] in <9577ac7a62ef43179789031239ba8798>:0 at BetterTracking.Tracking_Persistence.GetBodyOrder (System.Int32 index, System.Int32 fallback) [0x00019] in <cb40b1189d71419681afcc0060740214>:0 at BetterTracking.Tracking_Persistence.FallbackBodyCheck () [0x000b7] in <cb40b1189d71419681afcc0060740214>:0 at BetterTracking.Tracking_Persistence.OnLoad (ConfigNode node) [0x0015a] in <cb40b1189d71419681afcc0060740214>:0 at ScenarioModule.Load (ConfigNode node) [0x0000e] in <4b449f2841f84227adfaad3149c8fdba>:0 at ScenarioRunner.AddModule (ConfigNode node) [0x0005e] in <4b449f2841f84227adfaad3149c8fdba>:0 -K

Very nice info mod! I'm seeing some errors in the log though, looks like the code is trying to process a few things it probably shouldn't (as we don't manipulate these "parts"). [LOG 12:12:28.521] [PartInfoInPAW] Trying to load settings from GameData/PartInfoInPAW/Settings.cfg [LOG 12:12:28.521] [PartInfoInPAW] Settings file found [LOG 12:12:28.523] [PartInfoInPAW] Finished loading settings [ERR 12:12:28.528] [PartInfoInPAW] Couldn't get config value name for part kerbalEVA: Sequence contains more than one matching element [ERR 12:12:28.531] [PartInfoInPAW] Couldn't get config value name for part kerbalEVAfemaleVintage: Sequence contains more than one matching element [ERR 12:12:28.533] [PartInfoInPAW] Couldn't get config value name for part kerbalEVAVintage: Sequence contains more than one matching element [ERR 12:12:28.534] [PartInfoInPAW] Couldn't get config value name for part kerbalEVAfemaleVintage: Sequence contains more than one matching element [ERR 12:12:28.537] [PartInfoInPAW] Couldn't get config value name for part kerbalEVASlimSuit: Sequence contains more than one matching element [ERR 12:12:28.538] [PartInfoInPAW] Couldn't get config value name for part kerbalEVASlimSuitFemale: Sequence contains more than one matching element -K

It would be easier to try and assist you if you could provide the error you're seeing. -K

Has anyone else had an issue with the Asteroids, etc in the inner system preventing the Sentinel Telescope from activating due to not being between Kerbin and "the next body inwards" due to the eccentric orbit of bodies like 3190 - Phaekay that cross multiple orbits? -K

It looks like the archive for OPX-InnerWorlds 0.2.5 on Spacedock is corrupt. It's only about 2 meg instead of 50 meg and is missing most of the files. (re- downloaded several times to rule out issues on my side) The copy on Github appears to be fine. -K

Did the pass specifier warnings get fixed yet? I'm getting three of them from the latest release of Nedion Plus (0.7.1, freshly downloaded from Spacedock this morning). [WRN 09:25:42.152] more than one pass specifier detected, ignoring all but the first: OPX-NeidonPlus/KopernicusConfigs/01-Nito/@Kopernicus:FOR[OPX-NeidonPlus]:AFTER[OPM] [WRN 09:25:42.152] more than one pass specifier detected, ignoring all but the first: OPX-NeidonPlus/KopernicusConfigs/02-Tito/@Kopernicus:FOR[OPX-NeidonPlus]:AFTER[OPM] [WRN 09:25:42.152] more than one pass specifier detected, ignoring all but the first: OPX-NeidonPlus/KopernicusConfigs/05-Chymere/@Kopernicus:FOR[OPX-NeidonPlus]:AFTER[OPM] -K

Very nice, just installed and whipped up configs for Dwarf Planets Plus , Ghekta and Outer Kerbin. Have you considered an icon for Ice Giants? (DPP has one). -K

Thanks Nertea! I installed the updated version and can confirm that it fixed the issue for me. -K

@DMagic Are you still supporting this mod? I'm having similar issues to @ngx. It seems as if there may be a limit to how many bodies the By Celestial Body view can display. I'm using both OPM and another mod that adds bodies closer to the sun (DPP) and I don't see anything further out than Jool. KSP 1.12.5 w/ MH & BG TSE 7.0 OPM 2.2.11 Dwarf Planets Plus 1.1 -K

That may well be the issue for me then. While I realize it's more realistic and understand why you set it up that way, my personal play style doesn't usually involve the time warping through very long stretchs to have things happen that I see many others use. It's an easy enough thing to patch for myself though now that that I understand how the system works and I thank you for taking the time to look into it for me and explain the system. While I've only started using Spacedust and FFT with this playthrough, I've been using your NFT mods for quite a while and they are some of my favorites. -K

This is the config file that appears to trigger the issue. Without it I get the stock Kerbin atmospheric OX band, with it I get two identical exospheric OX bands and no atmospheric band. Please ignore the units, the screenshots were taken before fixing the labeling issue. I can't seem to figure out how to attach a file in this forum, so here's the config file in a code block. // Defines Oxidizer definitions for Kerbin exosphere // KERBIN // So many fuel tanks have been vented and otherwise lost around Kerbin that it has low concentrations of gasified oxidizer to collect // ============= SPACEDUST_RESOURCE:NEEDS[SpaceDust] { resourceName = Oxidizer body = Kerbin RESOURCEBAND { name = kerbinOrbit title = #LOC_SpaceDust_Band_Orbit // Discoverability Data // -------------- alwaysDiscovered = true alwaysIdentified = true allowRemoteDiscovery = true allowRemoteIdentification = true bandType = Exosphere // Maximum and minimum abundances (variation is by game seed) // In t/m^3 minAbundance = 0.0000000000276 maxAbundance = 0.0000000000306 // Scale abundances by air density useAirDensity = false // Distribution Data // -------------- // Distribution model to use, can be Uniform or Spherical distributionType = Spherical // These parameters are specific to the Spherical model // ------- // Altitudes are in km from sea level // Maximum altitude for a distribution altUpperBound = 650000 // minimum altitude for a distribution altLowerBound = 80000 // peak of a distribution altPeak = 300000 // maximum variation of these altitudes (variation is by game seed) altVariability = 5 // Falloff for altitude, can be Linear or None altFalloffType = Linear // lats in degrees // Maximum latitude for a distribution latUpperBound = 10 // Minimum latitude for a distribution latLowerBound = -10 // peak of a distribution latPeak = 0 // maximum variation of these latitudes (variation is by game seed) latVariability = 1 // Falloff for latitude, can be Linear or None latFalloffType = Linear } } -K

I know the feeling on the forums. As to my issue... Well, the old labeling is gone, but the numbers themselves haven't changed. I'm still seeing concentrations that require game years of harvesting to gather usable quantities of basic resources like LiqHydrogen. I've "solved" it for myself by simply patching the concentrations in the config files with my own MM patches to increase the levels to where they work for me. If you're interested in researching it further, just let me know what data you need and I'll do my best to put it together. -K Oh, I am still having the issue with the ExoSphere OX band somehow overwriting the planetary OX band as well. I haven't found a solution to that.