Search results for query: meananomaly

..."OrbitalInclination":21.118831, "Periapsis":201.271868, "OrbitalPeriod":159594273.567200, "AscendingNode":0.000000, "MeanAnomaly":342.599692, "RotationPeriod":285618.408516, "AxialTilt":-0.041915, "Rings":[ { "Name":"Shinrarta Dezhra A A Belt", "RingClass":"eRingClass_Rocky"...

Here you go. managed to find a workaround :sneaky: Search like usually but make a bookmark target something else select bookmark than u can set as target without killing the game. { "timestamp":"2022-03-12T22:44:04Z", "event":"SupercruiseExit", "Taxi":false, "Multicrew":false...

Yes, I see BodyID 68 is missing, and it is likely to be a station since Jameson Memorial is BodyID 69, but are you sure they are numbered consecutively? Because from the Start Menu pic I would have expect a hidden station to be at one of the twin moons of the AB planets. Why does targeting it...

I think i found something in ShinDez BUT i don't want to put too much hope on people. It's a strange thing: i posted ShinDez system bodyIDs some weeks ago, pointed that there were 12 comets in the system but as i only was looking for bodies, i didn't pay much attention to ... stations! Do...

I notice the comets only seem to be associated with event "SupercruiseExit". Perhaps that's why they dont show up on scans. Must check Halley's & Grey's for event type! Edit: mm, also “SupercruiseExit"

Grey's Comet is indeed in Lave (BodyID 9). See below.

Mmm, 12 comets in Shinrarta seems a bit excessive! Not seen the “SmallBody” data type mentioned before, but then not looked in the journal specification for a long time, it’s probably been updated... Edit: have you got a journal specification later than v32? In 3.2 the only body types...

Regarding Shinrarta's logs, i have this: The crash at ID 68 doesn't only happen in this system, but even to others (i still doesn't figure out why, it's not related to station type) Hope it can help ;) Edit: Once you done all stations, the next ID to search crash the galmap, so stations are...

What can we see with Isinor's logs: "Isinor", "BodyID":0 => Single star system It has a belt "Isinor A Belt" (BodyID 1) and 3 clusters (from 2 to 4). It has ringed gas giants It has 23 comets! It has 17 bodies (ONLY stars, gas giants and planets are counted. Belts, clusters, rings and comets...

Comet system (the best one for now is Isinor but don't have full data at the moment, sry): What can we see with Shinrarta Dezhra's logs: "Shinrarta Dezhra", "BodyID":1 => Multiple star system. The first body starts at 1, so there is a barycenter between this star and another star OR another...

If you think understand how they are built, this one will help you: What can we see with 26 Andromedae's logs: "BodyName":"26Andromedae A", "BodyID":2 => Multiple star system. The first body starts at 2, so there is a barycenter between this star and another barycenter of 2 stars It has no...

Here is another system, with 2 stars: What can we see with Sigma Andromedae's logs: "BodyName":"Sigma Andromedae A", "BodyID":1 => Multiple star system. The first body starts at 1, so there is a barycenter between this star and another star OR another barycenter of 2 stars It has no...

What can we see with Sol's logs: BodyName":"Sol", "BodyID":0 => Single star system. If multiple, BodyID would have been 1 (0 beeing not THE, but A barycenter) It has a belt but no clusters It has ringed gas giants: Jupiter (ring name=Jupiter Halo Ring), Saturn (ring name=D Ring), Uranus...

Nice done (y) . "I am not going to tell you how i found it" => Can you just answer this: did you find/target it after a honk or did you use another way? While out in the black i'm still checking logs to understand how BodyIDs are done in-game: Counted as "NonBodyCount": Notable stellar...

..."OrbitalInclination":-32.227753, "Periapsis":78.962212, "OrbitalPeriod":434633028.507233, "AscendingNode":-79.035298, "MeanAnomaly":277.615147, "RotationPeriod":151858.131769, "AxialTilt":0.000000, "WasDiscovered":false, "WasMapped":false } { "timestamp":"2022-01-15T11:54:24Z"...

I was assuming that AscendingNode and Periapsis were in the same direction as MeanAnomaly, but they're actually in the opposite direction. That would have put the moons 25.9 degrees apart at 2021-10-18T13:27:25Z, which would put the conjunction at about 2021-10-28T05:20:46Z (plus or minus a few...

..."OrbitalInclination": 0.146677, "Periapsis": 269.940114, "OrbitalPeriod": 120757.567883, "AscendingNode": -178.757785, "MeanAnomaly": 135.891390, "RotationPeriod": 120772.765114, "AxialTilt": -0.413393, "WasDiscovered": true, "WasMapped": true } 2 c: {...

It seems that I fell for bad data. Measuring the angles (by dropping out with the moon and planet lined up, and looking at the RelPos), gives an angle of about 30.4 degrees between the moons. It seems neither the Orrery nor the scan data can be trusted for moon orbits. Given this, the next...

Excellent, I'll try to be there and check it out. Many thanks.

...Dangerous mixed up the meaning of Mean Anomaly so that it is the sum of the actual Mean Anomaly and Argument of Periapsis - assuming the MeanAnomaly is the Mean Anomaly, and correcting the Longitude of Ascending Node for 2 c to account for the negative inclination, the moons would be about 75...

..."OrbitalInclination": -4.782651, "Periapsis": 125.937692, "OrbitalPeriod": 337679.904699, "AscendingNode": 57.060756, "MeanAnomaly": 67.416656 } New keys AscendingNode and MeanAnomaly (in body scans I think) and some new keys in the Statistics event (some OnFoot_...). That's all I...