#Problem with placing star

15 messages · Page 1 of 1 (latest)

fickle wind
#

So, i have 2 stars: i want them to be at the distance of ~3ly. 1 parsec ≈ 3ly, so I copied the script from 1 star, and changed "Dist" parameter from n to n+1. But, the second star spawns right at the first one (see screenshots). I tried to change RA, Dist and Dec, but second star was either too far (900+ ly from the first star) or right at the first one

limpid dragonBOT
#

Thank you for posting in the modding forums, lutayovich!
These forums are community-driven, and while the SE Team may reply here from time to time, it is not to be expected.

Thank you to all the awesome people who contribute their time to help others in their modding adventures.

crude summit
#

you can spawn second star with planet parameters and place semimajor axis to match 3 lightyears

#

ra dec is busted that way i think, there not really much precise way to place them close to each other that ima ware of

#

other method is make barycenter with 1 star and place it near that star

fickle wind
crude summit
#

is this 9.8 version?

#

im not much familiar with system modding there

fickle wind
fickle wind
lilac mountain
#

For multiple-star systems, you should define a StarBarycenter in a script in /catalogs/stars/MyBarycenter.sc, and then define your stars in a separate script in /catalogs/planets/MyStars.sc.

#

The filenames obviously don't matter, and you can either keep your star scripts separate or in the same file, up to you

#

Both stars should list "MyBarycenter" as their ParentBody

#

I also see you had another help post about coordinates in other galaxies-- This is far enough away from the origin that you will start to see significant errors caused by floating point precision, which is why making small changes to the distance doesn't seem to work until it's obscenely far away. Try working in a nearby galaxy, or just working inside the Milky Way. I also know a way to remove all catalog objects so you can start in an "empty" universe, if that would work

#

Although I'm not 100% sure if it would work in 0.980. It should, it's just untested