Підпишіться, аби завантажити
Trithorne Cluster ("Real Solar Systems" World)

i've been trying to get the real orbits mod to work on this star system, though it doesnt seem to work on this world, any clue why?

There is ONE thing you can add that will make this even more amazing: the Caldari Space Skybox. https://steamproxy.net/sharedfiles/filedetails/?id=3392714099

@xAzural it seems to work fine with MES. Been playing with most of those mods and things are spawning fine, at least on the starting planet.

You should be able to change that in the world settings after you create the world.

Any way to launch this scenario in a way that allows creative mode? Admin tools can't seem to switch my mode anymore. Love the map so far.

Ive done some limited comparison between 3 versions of PAM. The OG version just wont work, at least for me, in a world with orbital mechanics. Alignment issues with docking and sensor fields. SenX version is better. Docking alignment is resolved but sensor fields are still offset. The Echthros version of PAM (available on his Discord) seems to resolve all these issues. At least for me. I have only tested on a planet, short distance only, but that is just where I am in this world right now. I hope this helps someone.

I can confirm having issues with a PAM operated mining ship. Specifically when trying to dock. The ship seems to be approx 2 meters off of the connector. The direction it is off alignment seems random in that the direction of offset changes from job to job. Also of interest is that the sensor field is also offset. I hope some of this information might help.

@Echthros I will try the version of PAM you altered and report here any results i have.

it's by design so the planets are easily reachable distance wise

..i think

as for orbit speeds
it's a game get over it lol
also i don't know why it bugs you since it would be too hard to match every planets orbit volocity

The planets in this solar system do not obey Kepler's Third Law, which states that relation (a^3)/(T^2) is constant for all planets (and other bodies) orbiting a star or all moons (and other bodies) orbiting a planet, where a is the semi-major axis and T is the orbital period. For example, Ohova is orbiting the Nyph-Ea/Wyrdel barycenter with a=5814km with T=161000s, while Frosti is orbiting the same pair of stars with a=7848km and T=41237s. You can tell already that this is unrealistic, because Frosti is orbiting Nyph-Ea/Wyrdel farther away and faster than Ohova.

I also found that Frosti is so close to Ohova that Onglax (Frosti's moon) could potentially crash into the Ohova-Qaale system.

Are these choices by design?

PAM may have issues with precision for planets that are too far from the origin (it uses Vector3 and float instead of Vector3D and double for a lot of things). I posted an edited version of the PAM script that in the real-solar-systems channel on my Discord if you want to see if that works. I know very little about the script and pretty much just did some search and replace of text, so you're welcome to try it out if you want. I won't be publishing the script unless I get permission and verification from people that it works.