Threat 9?
Did you mistype? Or is that an actual thing?
What he/she said
Threat 9?
Did you mistype? Or is that an actual thing?
Also, after about a half hour of checking the ammonia world, unable to confirm any probe spawns. Only seen UAs and Degraded Emissions Threat 9 (Scarcely).
EDIT: Threat 0... lol
Okay... I've just read the last 9 pages since waking up this morning, and I can't tell why people are talking about a Mel Sector system? What's the connection here?
That's a Gas Giant, not an ammonia world.
That's a Gas Giant, not an ammonia world.
Yes, is it common for UA's to spawn around a planetary body? (I thought that was a UP thing?)
I have only ever found them in deep space (cruising out several hundred LY from the main star)
I was surprised to find them in low orbit around a Gas Giant.
I flew around it for a little while a couple nights ago. I'm probably gonna return and try and do a circle around the planet every 10 degrees of latitude. Though if there is a large wreckage site there, that brings the old question back: WHY Merope 5c [blah]
Why are you assuming the high frequency segments are binary '1's and the low frequency ones are binary '0's?
Flipping the '1's and '0's around gives the following ratios:
Code:157 : 1000 = 0.157 31 : 1000 = 0.031 24 : 25 = 0.960 18 : 125 = 0.144 31 : 1000 = 0.031 189 : 200 = 0.945 151 : 1000 = 0.151 1 : 25 = 0.040 937 : 1000 = 0.937
Back when I was working with the unknown probe distances, I remember the aliens liking 'clean' ratios of 1000.
Who decoded that one.. can we ask them to look at this one also
Remember the original UA morse? And how difficult it was to persuade most of us it was actually morse? After that we referred to it as stylized morse. It took a certain kind of mind to decode it. Certainly not mine.
Wow... I've been trying to decode the "morse" from the angry reaction and I honestly can't even see what's going on to transcribe it. I can tell some of the things are obviously dashes and obviously dots, but not everything is the same length. There's bits where I can't tell if it's a dash or a dot-dash because even slowing the video down it pulses too quickly.
When I got through it transcribing what I could, I then realised I don't actually know morse well enough (at all) to be able to visually pick out letters. I tried, but I ended up with a random jumble of letters that made no sense.
And honestly each time I go back through it, I get something different!
/disgruntled
I'm no expert but this certainly looks like Morse code to me:
This would also explain why the Ancient Relic event goes on for ~5 minutes. I think we need to get a full recording of the event and get it transcribed.
(The speed of the video has been slowed down a bit as I was messing around with the footage in Premiere Pro).
EDIT: If it's not Morse code, then it might be some other type of pattern. Doesn't look random though...
It somewhat works with the last one as well. The problem is the middle one as I was searching the galaxy map (or whatever exists in edsm) for suitable planets, HIP 14909 kept popping up as a candidate for both the first and last bits of coordinates. However I couldn't find a system that would fit the middle bits of coordinates. The best I could come up with is:
(The percentage is the error as a percentage of the Col70-Merope distance)
Code:First group: Mel 22 Sector ZU-P c5-1 ------------------------------------ Merope: 136.580083 (-0.02%) HIP 14909: 26.941161 (-0.007%) Col 70: 836.592905 (+0.05%) Second group: Mel 22 Sector NX-U d2-33 -------------------------------------- Merope: 127.697097 (+0.2%) HIP 14909: 28.109822 (+0.1%) Col70: 825.827712 (+0.3%) Third group: Mel 22 Sector NX-U d2-27 ------------------------------------- Merope: 131.181898 (-0.04%) HIP 14909: 34.739277 (-0.01%) Col70: 816.147941 (+0.0004%)
The 0.1-0.3 % error doesn't seem that high until you consider the fact that the Link is able to specify coordinates within 1/1000th (0.1%) of Col70-Merope distance - thus the error should never be larger than +/- 0.05%.
If the probe was measuring distances from Mel 22 d2-33, this would result in the following fractions:
Code:Merope: 127.697097 / 871.018424 = 0.1466 = 147 / 1000, actual 144 / 1000 (represented as 18 / 125) HIP 14909: 28.109822 / 871.018424 = 0.0323 = 32 / 1000, actual 31 / 1000 Col70: 825.827713 / 871.018424 = 0.9481 = 948 / 1000, actual 945 / 1000 (represented as 189 / 200)
Don't suppose there exists an unmapped system within couple of light years from d2-33?
Would just like to add, if it wasn't already known, that it's more than just the Ancient Relic you can add to the Thargon Device.
http://imgur.com/a/VxtUr
You can add the Ancient:
-Totem
-Tablet
-Casket
Adding these 3 will result in the device glowing orange. It does nothing more until you scan it with your SRV. Doing so produces the same orange beam of doom you get from the relic. Here's a 20s clip of me showing exactly this.
https://www.youtube.com/watch?v=UaR8fajm-88&feature=youtu.be
Only guardian tech here, and a human scan. It seems the thargoids don't like ANYTHING to do with the guardians...
We are getting to the point where there is sufficient supporting evidence to say this hypothesis is now proven, but let's not jump to conclusions. More specifically the Thargoid UD does not accept Guardian technology has been proven; which might suggest some antipathy between the races, but it might just indicate one uses Metric threads and the other Imperial![]()
We are getting to the point where there is sufficient supporting evidence to say this hypothesis is now proven, but let's not jump to conclusions. More specifically the Thargoid UD does not accept Guardian technology has been proven; which might suggest some antipathy between the races, but it might just indicate one uses Metric threads and the other Imperial![]()
We are getting to the point where there is sufficient supporting evidence to say this hypothesis is now proven, but let's not jump to conclusions. More specifically the Thargoid UD does not accept Guardian technology has been proven; which might suggest some antipathy between the races, but it might just indicate one uses Metric threads and the other Imperial![]()
That looks better.
If it follows the 'old' system from the UP, we are looking for something relatively close to Merope.
If 1 is still the distance between Merope and Col 70 Sector FY-N c21-3 Then the first number gives the distance to Merope and the third to Col 70 Sector FY-N c21-3.
Second number is tricky though.
Maybe breakfast coffee is beginning to wake up the grey cells but I've had a thought. Possibly the UD spectogram is an invitation to a diplomatic meeting between Thargoids and Humans, the representation of a system from each (Merope and Sol) coming to a common point? Just a thought!
Maybe breakfast coffee is beginning to wake up the grey cells but I've had a thought. Possibly the UD spectogram is an invitation to a diplomatic meeting between Thargoids and Humans, the representation of a system from each (Merope and Sol) coming to a common point? Just a thought!
It somewhat works with the last one as well. The problem is the middle one as I was searching the galaxy map (or whatever exists in edsm) for suitable planets, HIP 14909 kept popping up as a candidate for both the first and last bits of coordinates. However I couldn't find a system that would fit the middle bits of coordinates. The best I could come up with is:
(The percentage is the error as a percentage of the Col70-Merope distance)
Code:First group: Mel 22 Sector ZU-P c5-1 ------------------------------------ Merope: 136.580083 (-0.02%) HIP 14909: 26.941161 (-0.007%) Col 70: 836.592905 (+0.05%) Second group: Mel 22 Sector NX-U d2-33 -------------------------------------- Merope: 127.697097 (+0.2%) HIP 14909: 28.109822 (+0.1%) Col70: 825.827712 (+0.3%) Third group: Mel 22 Sector NX-U d2-27 ------------------------------------- Merope: 131.181898 (-0.04%) HIP 14909: 34.739277 (-0.01%) Col70: 816.147941 (+0.0004%)
The 0.1-0.3 % error doesn't seem that high until you consider the fact that the Link is able to specify coordinates within 1/1000th (0.1%) of Col70-Merope distance - thus the error should never be larger than +/- 0.05%.
If the probe was measuring distances from Mel 22 d2-33, this would result in the following fractions:
Code:Merope: 127.697097 / 871.018424 = 0.1466 = 147 / 1000, actual 144 / 1000 (represented as 18 / 125) HIP 14909: 28.109822 / 871.018424 = 0.0323 = 32 / 1000, actual 31 / 1000 Col70: 825.827713 / 871.018424 = 0.9481 = 948 / 1000, actual 945 / 1000 (represented as 189 / 200)
Don't suppose there exists an unmapped system within couple of light years from d2-33?