Erm just brought a UA back from hip14478 and the timer no damage exploit no longer works, i got damage twice as i jumped, was not sure if it had been noted
On a more upbeat note me and Cmdr Ironguts have just recorded the Imp Eagle links soon
Erm just brought a UA back from hip14478 and the timer no damage exploit no longer works, i got damage twice as i jumped, was not sure if it had been noted
On a more upbeat note me and Cmdr Ironguts have just recorded the Imp Eagle links soon
I was able to perform the "Two CMDRs in the same instance listening to an UA" test, thanks to my second account. Very tricky to control two ships, from two PCs (PC and MAC), and recording at the same time, with only one hotas to swap for both!!!!
The two ships were a DBX and a Cobra.
First I kept the DBX, carrying the UA, 2Km away from the Cobra, then jettisoned the UA. Only the DBX was scanned, and it listened to its Drawing.
Then I approached the Cobra, and it was scanned as usual. The news are that the Cobra listened to the Cobra Drawing.
So, each ship triggered its specific drawing, in the same UA, at the same time.
In my next test I'll deploy the UA while both ship are inside scanning range, to see if something changes, but I doubt it.
Next I will try the test with a T6 and a Cobra, just to see if the Cobra will listen to the Station's name triggered by the T6.
Just one last thing, I noticed that in the sequences I've posted, the DBS and DBX sequences are inverted.
I've already updated the list.
If RedWizzard wants to update its Drawing Tool as well.
I was able to perform the "Two CMDRs in the same instance listening to an UA" test, thanks to my second account. Very tricky to control two ships, from two PC, and recording at the same time, with only one hotas to swap for both!!!!
The two ships were a DBX and a Cobra.
First I kept the DBX, carrying the UA, 2Km away from the Cobra, then jettisoned the UA. Only the DBX was scanned, and it listened to its Drawing.
Then I approached the Cobra, and it was scanned as usual. The news are that the Cobra listened to the Cobra Drawing.
So, each ship triggered its specific drawing, in the same UA, at the same time.
In my next test I'll deploy the UA while both ship are inside scanning range, to see if something changes, but I doubt it.
Next I will try the test with a T6 and a Cobra, just to see if the Cobra will listen to the Station's name triggered by the T6.
Just one last thing, I noticed that in the sequences I've posted the DBS and DBX are inverted. I've already updated the list.
If RedWizzard wants to update its Drawing Tool as well.
I mean that, in my list, the sequences I've marked as DBX are the DBS's, and vice versa. So the two drawings in RedWizzard's application, are inverted. In fact, if you watch carefully, One ship is longer than the other. The longer is the DBX, but it is wrongly listed as the DBS.
I've noticed few moments ago, while decoding the MORSE of my DBX: they were the sequences of what I've listed as the DBS's.
As I said the ImpEagle triggers the Drawing of the common Eagle (MYQNXR QNXRXM the first sequences)
I mean that, in my list, the sequences I've marked as DBX are the DBS's, and vice versa. So the two drawings in RedWizzard's application, are inverted. In fact, if you watch carefully, One ship is longer than the other. The longer is the DBX, but it is wrongly listed as the DBS.
I've noticed few moments ago, while decoding the MORSE of my DBX: they were the sequences of what I've listed as the DBS's.
i know you told me so but i had to try it.
well back on the pictures in the morrow concentrating on the missing and extra characters.
At least the test provided a Cmdr with his first chance to see one so its all good
i know you told me so but i had to try it.
well back on the pictures in the morrow concentrating on the missing and extra characters.
At least the test provided a Cmdr with his first chance to see one so its all good
A few more free floaters for RedWizzard or who ever plots them out
COL 285 SECTOR GX-V C21A 67LS FORM STAR 138.42LY FROM mEROPE
COL 285 SECTOR FB-X D1-89 401LS FROM STAR 135.2 FROM mEROPE
COL 285 SECTOR UT-M A9-0 55LS FROM STAR 140.5 FROM MEROPE
COL 285 SECTOR GW-V C2-11 7.45LS FROIM STAR 137.88 LY FROM MEROPE
COL 285 SECTOR PN-R B5-5 2.4LS FROM STAR 135.52LY FROM MEROPE
HYADES SEC XZ-Y C8 26 LS FROM STAR 136.41LY FROM MEROPE
HYADES SEC XU-X B1-2 25.4 LS FROM STAR 141.48 FROM MEROPE
HIP 14479 15 LS FROM STAR 135.78LY FROM MEROPE
Went to Wolf 221 in an Orca (sh*t range and doesn't like scooping) got UA. Morse freefloating before scoop was too short for drawing ship, took it back to Varati (really you are going to hit cargo hatch EVERY time) got to Bond Hub again short Morse about 30 secs. Have vids but no sound (thanks Shadowplay). Killed UA by accidentally boosting into it. Have now updated Nvidia drivers and experience. Will try to record again tomorrow.
o7
Off to Thompson first to repair the damage and reload AMFU
If you need a UA delivered you can have mine. Jumping with an orca sounds horrible and if any 1.4 UA will do I can give you the one I have at Thompson dock
Allen Stroud, keeper of Elite lore and consistency for FD, confirmed it some time ago in a podcast. See link on wiki if it has not been edited out of existence.
I'd be grateful if you could narrow down where Alan made that statement because if it is as old as you and Han Zen seem to be saying then the context is very important. How did he get on to talking about something that no-one had seen in game?
Are you saying that the change of "Discovery of first non-human relic in space. Origin still unknown in 3200. " (http://wiki.alioth.net/index.php/Timeline) to "Discovery of first non-human relic in space. Origin still unknown in 3300. " (https://www.frontier.co.uk/games/older/frontier_elite_ii/) is evidence that the entry refers to the UAs we see in game now? That seems a tenuous conclusion vs the much more obvious interpretation that they've simply updated it based on the fact that ED is set in 3300. I don't think it's surprising that FD would update the FFE timeline to account for the later game. I do find it surprising that you would reach that conclusion given how reluctant you are to accept that DB bringing up the UA in the context of a question about Thargoids indicates a link between the two.
I've been doing a little independent research on the signal these things produce because well.. I'm curious. I also come at this largely ignorant of any in-depth analysis that's been done. That's OK, a fresh perspective can be helpful. At the moment I'm more interested in the signal structure itself.
I'm just sharing my thoughts and observations.
Looking at these cycle timings for the first object -
The graph shows cycle times (in seconds) for each subsequent cycle. I understand the cycle times are dependant on the morse characters sent, but even allowing a +/- second error I wasn't seeing any repeated pattern. So I wondered how long the message actually was. I set about to find out from the horses mouth so to speak.
Incidentally I was parked next to one when I logged out, when I logged in it wasn't there (confirmed twice). It didn't take long to find another one though (I suspect they eventually spawn in every system in the'shell').
I started timing the second one I found and listening to the sounds it was making, Something in my brain shifted gears and where previously I was hearing the digestive rumblings of someone who had eaten too many baked beans for breakfast the sound suddenly resolved itself into distinguishable morse code. Morse code mind you sounding like it's coming from underwater, slowly drifting up and down in pitch, with 'dits' a high tone and 'dahs' a low tone, and varying in it's timing, but definitely morse code at about 8-10 wpm.
(Although each individual morse character is identical, there is a slight difference between each character. As if someone had tapped out “the quick brown fox jumps over the lazy dog” by hand and that sample was chopped up to generate each character. ).
I start picking out individual characters. Goodness my morse code is rusty, and not helped by the other noises happening at the same time.
I started writing down the morse decoding it by ear over about a half hour period. I found-
A message composed of 29 groups of six-character 'words'.
This message is repeated every ten cycles.
As best I could make out (with a low degree of certainty) the morse message in my case was-
(Question marks indicate non-resolved characters)
This supposedly translates to a 2D coordinate map of my ship (courier). Any ideas how ? Has anyone actually plotted one out ?
In my mind was the question, Does the cycle time depend solely on the length of the morse character sequence ?
Looking at the timings for the sequence I decoded by ear (the last five 'frames' of the signal ) -
I'd tentatively suggest there's some other factor involved in the cycle times. To draw a firmer conclusion I'll need to time both 'on' and 'off' times for each cycle. Anyway that's for another day. What I'm looking at is to prove to myself as much as possible that there isn't another layer of information in the signal. Like I say, I'm curious.
One question – can anyone point me to small simple PC audio recorder ? I don't need video recording and don't have the SSD room anyway.
Thanks
Audacity is a good free audio recorder for PC (nat actually sure how big it is) - I have been using Spek for spectograms - Rizal uses another program ... not remembering it atm
makes it easier than trying pick the morse out by ear
the process goes something like this:
I like Spek because you can hit cntrl-up cntrl-down to change the range of the dBFS - makes it a little easier to "see" the morse.
Also - front of UA thread 3 has links to the morse fun and MJKs Awesome mapping of the Morse to ship images ... Some nifty software (made by more computer savvy people than I ) that will draw your ship for you when you supply the translated morse is in those links as well.
(Although each individual morse character is identical, there is a slight difference between each character. As if someone had tapped out “the quick brown fox jumps over the lazy dog” by hand and that sample was chopped up to generate each character. ).
I believe that's exactly how it's implemented. Rather than a sample for a dot and a sample for a dash, the game uses samples for each letter and digit as a whole.
Make a coordinate plane with the letters A-Z on each axis. A pair of letters defines a point on the plane. Each set of six letters defines three points that can be interpreted as a triangle. You can use this page to do the drawing: https://dl.dropboxusercontent.com/u/1402878/UA_draw.html. Unfortunately your transcription doesn't produce a recognisable image, but checking Rizal's version for Imperial Courier it's obvious that there is significant similarities (he's decoding the Morse using spectrograms of the filtered audio which I believe is a lot easier than listening to it). You've done an impressive job getting as much as you have on your first attempt. For reference I've included Rizal's transcription below and reformatted yours to match.
Oh that's all very cool. Thank you very much for the info !
EDIT: Cycle times. Just using a stopwatch lap timer triggered when the lights first come on (when it makes that groaning noise - which sounds like a massive surge of power). Done by hand so prone to error.
I was able to perform the "Two CMDRs in the same instance listening to an UA" test, thanks to my second account. Very tricky to control two ships, from two PCs (PC and MAC), and recording at the same time, with only one hotas to swap for both!!!!
The two ships were a DBX and a Cobra.
First I kept the DBX, carrying the UA, 2Km away from the Cobra, then jettisoned the UA. Only the DBX was scanned, and it listened to its Drawing.
Then I approached the Cobra, and it was scanned as usual. The news are that the Cobra listened to the Cobra Drawing.
So, each ship triggered its specific drawing, in the same UA, at the same time.
In my next test I'll deploy the UA while both ship are inside scanning range, to see if something changes, but I doubt it.
Next I will try the test with a T6 and a Cobra, just to see if the Cobra will listen to the Station's name triggered by the T6.
Just one last thing, I noticed that in the sequences I've posted, the DBS and DBX sequences are inverted.
I've already updated the list.
If RedWizzard wants to update its Drawing Tool as well.
Let's assume that A) The UA are made by an alien force. And B) They are exploration objects.
If I happened to be an alien force that had a huge military confrontation with another race (IE Thargoids vs Humans), and I had vanished for centuries, I would probably want to know what has happened during this time. So, I'd start sending out probes to gather information.
BUT I would not want any potentially dangerous species to know where my home is.
A good system to do that is to send probes to random systems to check what they find, and contrast it with my database. For many trials, nothing was found... until the humans found and UA. There the UA sent a signal saying "Hey, I've found I ship I think I have in my database in this system".
I'm a Thargoid and I think I've found the humans. What do?
Well, an option would be to keep sending random probes to the zone... but what information would you get? Nothing useful: Probably a hundred, maybe a thousand of random informaion of human presence in different systems. That information is really incomplete: You don't get any clear information if you don't do millions of trials. The way to reduce the needed probes is by triangulatingthe position of the species colonies. How to do that:
1) Select a system far away from your findings (IE: MEROPE) 2) Send your probes to the adjacent systems and search. 3) Note findings. Spread to the next adjacent systems. 4) Repeat 2 and 3.
EVENTUALLY the shell will reach inhabited human space. From there they will have a really good idea of how big the human empires are, and where to send their probes to gather more specific information.
I would add drawing to ilustrate my idea, but I'm at work actually.
In my opinion, when the shell reaches the first inhabited human system, we will start seeing more UA inside the habitable bubble.
