I understand all the nuances of that, and I really should have said UTC rather than GMT, because while GMT and UTC happen to share the same time, one is a timezone, the other is not, but I digress. The only reason I asked was because the times listed in the various posts were devoid of any qualifiers that I could see, and since players are from all over the world, it is hard to tell exactly what time they may be referring to. Since the time displayed in game is universal to all players, that is why I asked about and referred to in-game time.
Exploration - When worlds colide
- Thread starter Ben Ryder
- Start date
I understand all the nuances of that, and I really should have said UTC rather than GMT, because while GMT and UTC happen to share the same time, one is a timezone, the other is not, but I digress. The only reason I asked was because the times listed in the various posts were devoid of any qualifiers that I could see, and since players are from all over the world, it is hard to tell exactly what time they may be referring to. Since the time displayed in game is universal to all players, that is why I asked about and referred to in-game time.
Game time is not GMT. There's an hour difference due to Daylight Savings Time. I never specified a time zone since the game clock isn't set to a specific time zone.
So yeah, all times are based on the in game clock display in the cockpit. It's too much work to translate to my time zone or any others. I'm GMT -8, but actually because of DST I might actually be GMT -7 right now. Too much room for confusion.
And FYI. The distance display to the B moon just switched from reading in Ls to reading in Mm
It switched over from 0.10Ls to 30.0Mm at 20:11:21 and then to 29.9Mm at 20:14:36, 29.8Mm at 20:25:40 and 29.7Mm at 20:36:40. So it's moving at ~100Km every 11m and speeding up slightly at this time in the orbit.
The speed varies depending on where the moons are in their orbit, so I need to average the speed over 1 full orbit or 1.4 days.
I should have some more accurate numbers tomorrow since I have better resolution now on the distance and it will click over tenths of Mm quicker so I don't have to watch for 5 hours to see the number change.
P.S. Where I'm parked, the moon was dipping down below the horizon and is now staring to rise back up as it gets closer. So at this point in the orbit I think the approach is effectively linear. There's not much of a curve left between them.
Also note that the radius of the B moon is 1,347 km so the moon will be in contact at a distance of 1.347Mm, as measured from the surface of the C moon.
P.P.S. Over the past 67.7 hours the average speed is 0.001391 Ls/hr or 0.416983 Mm/hr
So I make it 68.7151 hours to collision from 12 Oct 20:11:21 (2d 20h 42m) which is October 15 at 16:53:21 pm
The variability of the calculation each time is a bit frustrating but because of the orbital speed and distance variation of the moons and the rounding of the numbers, I don't know how to be more accurate.
Disclaimer: Due to inherent inaccuracies in the measurements, give or take a couple of hours from my prediction. Also, I'm no mathematician, so I could have made a mistake in my calculations or logic that may result in my prediction being completely wrong.
Update: 21.8Mm away at 13:01:20 (13 Oct), 16.8h average speed of 0.487137Mm/hr
Update: 18.3Mm away at 00:25:50 (14 Oct), 28.2h average speed of 0.414286Mm/hr
Update: 15.7Mm away at 05:56:51 (14 Oct), 33.8h average speed of 0.423599Mm/hr
So yeah, all times are based on the in game clock display in the cockpit. It's too much work to translate to my time zone or any others. I'm GMT -8, but actually because of DST I might actually be GMT -7 right now. Too much room for confusion.
And FYI. The distance display to the B moon just switched from reading in Ls to reading in Mm
It switched over from 0.10Ls to 30.0Mm at 20:11:21 and then to 29.9Mm at 20:14:36, 29.8Mm at 20:25:40 and 29.7Mm at 20:36:40. So it's moving at ~100Km every 11m and speeding up slightly at this time in the orbit.
The speed varies depending on where the moons are in their orbit, so I need to average the speed over 1 full orbit or 1.4 days.
I should have some more accurate numbers tomorrow since I have better resolution now on the distance and it will click over tenths of Mm quicker so I don't have to watch for 5 hours to see the number change.
P.S. Where I'm parked, the moon was dipping down below the horizon and is now staring to rise back up as it gets closer. So at this point in the orbit I think the approach is effectively linear. There's not much of a curve left between them.
Also note that the radius of the B moon is 1,347 km so the moon will be in contact at a distance of 1.347Mm, as measured from the surface of the C moon.
P.P.S. Over the past 67.7 hours the average speed is 0.001391 Ls/hr or 0.416983 Mm/hr
So I make it 68.7151 hours to collision from 12 Oct 20:11:21 (2d 20h 42m) which is October 15 at 16:53:21 pm
The variability of the calculation each time is a bit frustrating but because of the orbital speed and distance variation of the moons and the rounding of the numbers, I don't know how to be more accurate.
Disclaimer: Due to inherent inaccuracies in the measurements, give or take a couple of hours from my prediction. Also, I'm no mathematician, so I could have made a mistake in my calculations or logic that may result in my prediction being completely wrong.
Update: 21.8Mm away at 13:01:20 (13 Oct), 16.8h average speed of 0.487137Mm/hr
Update: 18.3Mm away at 00:25:50 (14 Oct), 28.2h average speed of 0.414286Mm/hr
Update: 15.7Mm away at 05:56:51 (14 Oct), 33.8h average speed of 0.423599Mm/hr
Last edited:
You can catch it next time around. It happens every ~133 days
I'm planning to record video from early Sunday morning until the moon has passed. I'll try a 2-4 hr video capture tonight and see what it looks like when I speed it up.
Is there an easy way to take a screenshot automatically at regular intervals?
I've minimized fuel use but I would still worry about staying logged in unattended for 12-24 hours or longer.
Looming large over the horizon now at 27.8Mm away (27.7Mm@00:08:52, 0.581012 Mm/hr average over the past 4 hours. 581Km/hr or 161m/sec)
Update: 18.3Mm away at 00:25:50 (14 Oct), 28.2h average speed of 0.414286Mm/hr
Update: 15.7Mm away at 05:56:51 (14 Oct), 33.8h average speed of 0.423599Mm/hr
Last edited:
Turn off your shields and unnecesary modules to spend less fuel.
Yeah. I had them off but I was moving the ship around and using the SRV last night and forgot to turn them off again. Idle fuel use is down to 0.10/h with temp at 7% and ice on the canopy. I have ~21.2T left in the tank which is ~212 hrs at this rate. I was full when I got here but spent a lot of time looking for geysers and idling on the surface.
Update: 21.8Mm away at 13:01:20 (13 Oct), 16.8h average speed of 0.487137Mm/hr
Update: 18.3Mm away at 00:25:50 (14 Oct), 28.2h average speed of 0.414286Mm/hr
Update: 15.7Mm away at 05:56:51 (14 Oct), 33.8h average speed of 0.423599Mm/hr
Last edited:
Just arrived in-system late last night. I'm at 30,-30 on the C moon and the B moon is 17.8Mm away as I post this.
I've been thinking of opening up my ship to multi-player when the moon gets closer. It looks like 11PM-5AM my time (UTC+8) Sunday night will be the closest distance, depending on the speed estimates. 1AM will be my cut-off time so I get some shut-eye for work on Monday. I'm hoping to at least see the moons 'touch'.
I'm usually in Fleetcomm, but could be in Mobius or Mobius Eurasia.
I've been thinking of opening up my ship to multi-player when the moon gets closer. It looks like 11PM-5AM my time (UTC+8) Sunday night will be the closest distance, depending on the speed estimates. 1AM will be my cut-off time so I get some shut-eye for work on Monday. I'm hoping to at least see the moons 'touch'.
I'm usually in Fleetcomm, but could be in Mobius or Mobius Eurasia.
Update. My new average speed over 33.8 hours, since it started reading in Mm, is ~0.423599 Mm/hr (~117m/s)
With 14.353Mm remaining until impact, that's ~33.88h remaining putting the impact time at ~15:49:51 tomorrow.
So the numbers are still in the ballpark of my past estimates.
I'm in Fleetcomm recording some early video of the approach.
Disclaimer: Due to inherent inaccuracies in the measurements, the impact could be sooner or later. Arrive early and be prepared to stay later.
The moons orbital speed is variable so it could be moving a bit faster or a bit slower nearing the time of the impact which could move up or move back the impact time significantly.
Also, I'm no mathematician, so I could have made a mistake in my calculations or logic that may result in my prediction being completely wrong.
With 14.353Mm remaining until impact, that's ~33.88h remaining putting the impact time at ~15:49:51 tomorrow.
So the numbers are still in the ballpark of my past estimates.
I'm in Fleetcomm recording some early video of the approach.
Disclaimer: Due to inherent inaccuracies in the measurements, the impact could be sooner or later. Arrive early and be prepared to stay later.
The moons orbital speed is variable so it could be moving a bit faster or a bit slower nearing the time of the impact which could move up or move back the impact time significantly.
Also, I'm no mathematician, so I could have made a mistake in my calculations or logic that may result in my prediction being completely wrong.
Last edited:
This is very exciting - it's a shame it is too far away from where I am at the moment otherwise I would have been joining you in a heartbeat. Is anyone parked on the approaching surface watching the imminent collision from the 'other side', as it were?
A little more added to my timelapse:
[video=youtube;7zIgN2_qg_s]https://youtu.be/7zIgN2_qg_s[/video]
[video=youtube;7zIgN2_qg_s]https://youtu.be/7zIgN2_qg_s[/video]
My $0.02 regarding collision time: all today the time per 0.1Mm has been decreasing for me, up until the last few measurements. It started at 12m28s, but the last five measurements have been 10m25s +/- 0m01s. If the moon was heading straight towards me, that would put 0Mm at 9:17 in game time.
I'm parked on 2 c with 2 b on the horizon, so I'm more-or-less over the centre of 2 c. The distance in the UI is to the centre of 2 b, so the distance when they touch could be the shown distance less the two radii (1.348+1.108=2.456Mm). At the current rate of closure that could put 'first contact' about 4h16m ahead of the 0Mm time, or about 5:00 in game time.
As Major Klutz recommends - arrive early!
I'm parked on 2 c with 2 b on the horizon, so I'm more-or-less over the centre of 2 c. The distance in the UI is to the centre of 2 b, so the distance when they touch could be the shown distance less the two radii (1.348+1.108=2.456Mm). At the current rate of closure that could put 'first contact' about 4h16m ahead of the 0Mm time, or about 5:00 in game time.
As Major Klutz recommends - arrive early!
If anyone that's there will stream the event, I would appreciate a link to their stream
Yes, please
( and/or multicrew seat-offers) I've never streamed before, but I *think* I've got one set up. The link right now is:
https://gaming.youtube.com/watch?v=23X3W8-XWXg
I don't know if that's a permalink or not. My internet connection is something that resembles a piece of wet string, so not sure how good it will be.
Edit: I'll probably take the stream down again shortly. No point using up my data quota before the main event. I'll try to be back about 9:00am my time (UTC+8) or about 01:00 game time. I'll open up for multiplayer then too.
https://gaming.youtube.com/watch?v=23X3W8-XWXg
I don't know if that's a permalink or not. My internet connection is something that resembles a piece of wet string, so not sure how good it will be.
Edit: I'll probably take the stream down again shortly. No point using up my data quota before the main event. I'll try to be back about 9:00am my time (UTC+8) or about 01:00 game time. I'll open up for multiplayer then too.
Last edited:
Last edited:
Yeah, that variable speed has been a real pain. Half the time it's much faster than the average and half the time it's much slower.
It's in the fast part of the orbit now. The only question is, will it impact before it get's to the slow part of it's orbit?
There's a wobble too. The B moon will dip down below the horizon and then pop backup up again because the two orbit at slightly different angles.
10.9Mm now at 14:40. At it's average speed, there's ~22 hours to go.
Fingers crossed, the impact doesn't happen when the planets are in shadow. It's pretty dark in a black hole system without the milky way to light things up.
I don't see anyone else here with me in Fleetcomm. But there are bound to be instancing issues unless we're in a wing.
And for added fun, The A moon is now swinging around to do it's close pass now. A, B and the planet are all visible in the same direction.
B is now 10.9Mm. The raidius of B is 1,347 km or 1.347Mm, so there's 9.553Mm to go until contact. (with me, not the planet surface)
Last edited:
So, the moons don't rotate relative to each other?
If so, makes my plan easier to accomplish.
I'm going to land on the b moon (that's the smaller one which is 'ramming' the c moon, right?) , dismiss my ship & try to record the impact in my SRV. On a spot which is bound to be crushed in the collision.
Correct. Both are tidally locked.
Yes. The b moon orbits slightly faster than the c moon. They're about the same size but the b moon is actually slightly bigger.
Good luck. I'm not sure where on the b moon is the optimal place.
I would assume near the equator but I think the longitude would need to be opposite the side facing the planet.
If you time it right, you may be able to jump up in your SRV and land on the other moon.
Last edited: