I've been working on automatically generating binary stars and I've developed a bit of a problem. A couple systems -- 11 Com and DP Leo (and probably numerous others) cause Celestia to crash whenever you get some distance away (a bit over 120 light years in the case of 11 Com). This problem occurred when I modified my programme to add the HIP prefix to the first star rather than the barycenter (otherwise the "OrbitBarycenter" item would produce incorrect system architectures).
I can't tell if this is an encoding problem in the text file or what it is. If I copy the definitions for 11 Com or DP Leo out into a separate .stc, then they work.
If anyone could take a look at the .stc definitions for 11 Com and/or DP Leo and explain to me why it's crashing, I would really appreciate that.
Celestia crashes ~120 Light Years away from binary star
Forum rules
Please help to make this forum more useful by checking the FAQs before posting! Keep it clean, keep it civil, keep it truthful, stay on topic, be responsible, share your knowledge.
Please help to make this forum more useful by checking the FAQs before posting! Keep it clean, keep it civil, keep it truthful, stay on topic, be responsible, share your knowledge.
-
Topic authorSirius_Alpha
- Posts: 223
- Joined: 21.03.2019
- With us: 5 years 8 months
Celestia crashes ~120 Light Years away from binary star
- Attachments
-
- stars_bad.rar
- (307.66 KiB) Downloaded 168 times
Exoplanet nerd. I maintain a monthly-updated exoplanet catalogue here:
https://celestiaproject.space/forum/viewtopic.php?f=23&t=18705
https://celestiaproject.space/forum/viewtopic.php?f=23&t=18705
- Anthony_B_Russo10
- Moderator
- Posts: 672
- Joined: 03.07.2018
- Age: 21
- With us: 6 years 4 months
- Location: Tallahassee, Florida, US
When I tested it, neither of the systems caused my Celestia to crash.
Anthony B. Russo, I like Pluto. Mod of the Celestia subreddit: https://www.reddit.com/r/Celestiasoftware/
I have over 40 computers, trying to list them here would be a pain.
Responsible for the NEO catalog: https://celestiaproject.space/forum/viewtopic.php?f=23&t=22203
And mod of the Discord server.
I have over 40 computers, trying to list them here would be a pain.
Responsible for the NEO catalog: https://celestiaproject.space/forum/viewtopic.php?f=23&t=22203
And mod of the Discord server.
-
Topic authorSirius_Alpha
- Posts: 223
- Joined: 21.03.2019
- With us: 5 years 8 months
- Anthony_B_Russo10
- Moderator
- Posts: 672
- Joined: 03.07.2018
- Age: 21
- With us: 6 years 4 months
- Location: Tallahassee, Florida, US
I did it in 1.6.1 on my Latitude D820.
Anthony B. Russo, I like Pluto. Mod of the Celestia subreddit: https://www.reddit.com/r/Celestiasoftware/
I have over 40 computers, trying to list them here would be a pain.
Responsible for the NEO catalog: https://celestiaproject.space/forum/viewtopic.php?f=23&t=22203
And mod of the Discord server.
I have over 40 computers, trying to list them here would be a pain.
Responsible for the NEO catalog: https://celestiaproject.space/forum/viewtopic.php?f=23&t=22203
And mod of the Discord server.
-
Topic authorSirius_Alpha
- Posts: 223
- Joined: 21.03.2019
- With us: 5 years 8 months
-
- Site Admin
- Posts: 706
- Joined: 22.09.2018
- With us: 6 years 1 month
I confirm the issue. Line https://github.com/CelestiaProject/Celestia/blob/master/src/celengine/star.cpp#L1019, here getOrbitBarycenter() returns the star itself instead of the barycentre. Even if you did something wrong Celestia creates incorrect barycentre.
-
Topic authorSirius_Alpha
- Posts: 223
- Joined: 21.03.2019
- With us: 5 years 8 months
I think the crashing issue was something else. I had some barycenters missing any IDs. They crashed the programme whenever you got too close to them. 11 Com and DP Leo were just along the line of sight to systems that were incorrectly declared, so they were themselves not at all the problem.
As I expected, this was an error on my end. As for Celestia incorrectly drawing the barycenter, I've simply moved the HIP prefix to the primary star rather than the barycenter. Overall I consider the issue resolved.
Code: Select all
Barycenter
{
# lines
}
As I expected, this was an error on my end. As for Celestia incorrectly drawing the barycenter, I've simply moved the HIP prefix to the primary star rather than the barycenter. Overall I consider the issue resolved.
Exoplanet nerd. I maintain a monthly-updated exoplanet catalogue here:
https://celestiaproject.space/forum/viewtopic.php?f=23&t=18705
https://celestiaproject.space/forum/viewtopic.php?f=23&t=18705