I had this problem before. You want to make sure you have " and not “ . If you have a binary system you must create a barycenter in the stars folder and make the actual stars in the planets folder revolve around that barycenter
I had this problem before. You want to make sure you have " and not “ . If you have a binary system you must create a barycenter in the stars folder and make the actual stars in the planets folder revolve around that barycenter
As aFinapple said: The script with the 'StarBarycenter' belongs in 'addons\catalogs\stars' and the script with the two stars belongs in 'addons\catalogs\planets'.
To make a binary star system or a binary planet system, make sure that the following parameters are the same for both bodies in the system: Eccentricity, Inclination, AscendingNode, MeanAnomaly. The ArgOfPericenter parameter of the first body must differ by 180 degrees from the same parameter of the second body. It’s also necessary to calculate the SemiMajorAxis parameter for each body based on their masses using these simple formulae:
Windows 10 seems particularly picky about read/write permissions with software installed under Program Files folder. If you did install SpaceEngine under that folder, you could try by installing the program in a folder manually created by you, like c:\SpaceEngine instead.
Still? how do I create a star cluster or remove this weird star called "No name"As aFinapple said: The script with the 'StarBarycenter' belongs in 'addons\catalogs\stars' and the script with the two stars belongs in 'addons\catalogs\planets'.
Then your scripts will work.
But your orbital data are wrong.
Quote SpaceEngineer in: CREATING A PLANET in section 'Orbit {}'To make a binary star system or a binary planet system, make sure that the following parameters are the same for both bodies in the system: Eccentricity, Inclination, AscendingNode, MeanAnomaly. The ArgOfPericenter parameter of the first body must differ by 180 degrees from the same parameter of the second body. It’s also necessary to calculate the SemiMajorAxis parameter for each body based on their masses using these simple formulae:
also, how do you calculate the semi major axis?As aFinapple said: The script with the 'StarBarycenter' belongs in 'addons\catalogs\stars' and the script with the two stars belongs in 'addons\catalogs\planets'.
Then your scripts will work.
But your orbital data are wrong.
Quote SpaceEngineer in: CREATING A PLANET in section 'Orbit {}'To make a binary star system or a binary planet system, make sure that the following parameters are the same for both bodies in the system: Eccentricity, Inclination, AscendingNode, MeanAnomaly. The ArgOfPericenter parameter of the first body must differ by 180 degrees from the same parameter of the second body. It’s also necessary to calculate the SemiMajorAxis parameter for each body based on their masses using these simple formulae:
Quote SpaceEngineer:
Distances are in astronomical units, the masses are in solar masses.Body 1: a1 = R * M1 / (M1 + M2)
Body 2: a2 = R * M2 / (M1 + M2)
where R is the distance between the bodies, i.e. sum of their semimajor axes a1 + a2;
M1 and M2 are masses of bodies.
You probably have a graphics card which is not compatible with SpaceEngine.
Post your se.log.
I've posted about this issue too, so you're not alone.Hello, I'd like to ask, I noticed that on some planets ships are not rendered under certain height over the surface. In example, if I build the ship on the planet's surface, it is not visible, however I can take control and fly with it. I start climbing and after reaching certain altitude (or elevation ?), the ship appears. When it gets under that height, it disappears again. This height threshold value varies from case to case and it also seems that in some cases this behaviour appears only over certain regions of the planet. I tried several ship models with the same results. Is there some concrete planet parameter or parameters combination that prevent ships from rendering? Unfortunately, this is also the case of my customized planet, so I'd like to solve it. se.log doesn't contain any errors or warnings, it looks the same as in normal cases.
It happens i.e. on RS 8474-914-8-13293636-80 A8 (Acid planet), over the solid surface, some sea regions seem to be fine.
I aplologize if this problem was already discussed (I couldn't find it), if so, please provide me with link.