[1.12.x] [Planet Pack] Outer Planets Expansion (OPX)

[gdsafArby]

1 hour ago, Professor K said:

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'm pretty sure the purpose of BetterJool is to retexture Jool, otherwise I see no reason. I never found Jool to be a particularly ugly planet anyways, it is just a green gas giant.

[Professor K]

5 hours ago, gdsafArby said:

I'm pretty sure the purpose of BetterJool is to retexture Jool, otherwise I see no reason. I never found Jool to be a particularly ugly planet anyways, it is just a green gas giant.

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

[Interplanet Janet]

On 12/8/2024 at 4:33 PM, Professor K said:

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

Basically Jool's HD texture is hardcoded into the game, so if you want to do another texture it's easier to just kill-and-replace it than try to do any textural code-changing shenanigans.

[Professor 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

[Mr. Kerbin]

41 minutes ago, Professor K said:

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 don't think so, but I THINK this was to accomadate the fact that Sarnus (had to stop myself from spelling Sarkin) is much larger then OPM Sarnus.

[theogameren]

15 hours ago, Mr. Kerbin said:

I don't think so, but I THINK this was to accomadate the fact that Sarnus (had to stop myself from spelling Sarkin) is much larger then OPM Sarnus.

Yeah, OPX Sarnus is bigger than OPM Sarnus.

 

16 hours ago, Professor K said:

Is the MoonDistance.cfg file in OPX-SarnusPlus\KopernicusConfigs supposed to be for use with a specific mod?

Yes, it is for OPX-SarnusPlus.

[Professor K]

On 12/1/2024 at 6:47 PM, Professor K said:

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

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

 

Edited 2 hours ago by Professor K

[Professor K]

12 hours ago, theogameren said:

Yes, it is for OPX-SarnusPlus.

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

[Mr. Kerbin]

Maybe @The Minmus Derp knows why?