UA Mystery Thread 3: The Canonn

Status
Thread Closed: Not open for further replies.
Shame. Results like that will muddy the waters.

So it seems simple at this point... Everyone with a genuine UA, talk to each other via PM's to arrange a little UA meetup around Earth. [...]

With that tidbit of information, I concurr with mkten.

We'd have to eliminate the results from the dupe bug UA's that would "muddy the waters", and then retest using unique UA's. Just have to continue the testing from this point on, ensuring that the only UA's involved are unique.



Which brings up another point when we do the testing.

Maybe we can start naming the UA's to keep track of them :D lol
 
Last edited:
Well, they (FD) either overlooked the fact, that we experimented with duplicates or there is simply more to it. (See my previous post, that sadly got overlooked in the quest for torches and pitchforks).
I would have hoped they'd have said something. I wonder how often a dev looks at this thread...maybe they have a board on which they stick all these theories around a space for the one true theory, waiting to be filled.

We filed a bug report though, it wasn't just mentioned in these threads. A lack of communication between whoever handled the bug report and the devs involved in the UA stuff wouldn't surprise me as I know what it's like working on a large piece of software but it would still be pretty disappointing given that this situation should have been entirely foreseeable.

If there is a regional marker on the UAs, it wouldn't matter if we had two from 109V or one that was duplicated. The results would be the same (negative).

Yes. I hope there would be some reasonably obvious difference between UAs from different regions in that case though.
 
Last edited:
Purrs theory correct me if im wrong:
5-6 Every cycle (2 in HR1185)
Max 2 high or low purrs in a row. With 5 purrs in cycle it gives 20 combinations... or maybe 20 symbols ? If Yes, all we need is dictionary, a long signal with blocks of 5 impulses , never 3 in a row + human symbol representation.

But even this gives us one symbol per cycle, so about 7 symbols per jetissoned UA. Its not much, but what if every UA is transmitting diffirent part of longer messege?...

Lot of if's ... :)

Never found same purrs sequence (was it tested in one system/location ?).

I don't think the purrs align with a "cycle", they are an independent track.

Purrs occur very close to every 3.6 seconds, with a max deployment time of 6m40 you get 100 purrs (there's a no purr buffer at the start).

Because the "lights off" period (where there is no other sound) is always 18.6s (or thereabouts) you tend to hear 5 purrs but often you catch a 6th due to hearing an extra one at the end of the morse or just inside the howl.

Max 2 high or low purrs in a row - yes.

"Max 2 high or low purrs in a row. With 5 purrs in cycle it gives 20 combinations... or maybe 20 symbols ?"

Aye maybe X combinations given Y purrs per "group", but for me 5 is an arbitrary figure since there aren't 5-6 purrs per "cycle".

But the real issue is that no pattern ever seems to repeat, I've done an imperial (slave) tonne of listening and as far as I can see, every UA deployment has a unique set of purrs. I may be wrong but I've never heard the same twice and I've listen to a lot. =(
 
Last edited:
Correct. I saw it several times while scooping the paladium various commanders kindly contributed. Not sure how long you've been following the threads, just in case it's not long I want to point out that we've always been up front about those first couple of UAs having been duplicated, and we've warned people off using that bug more than once.

So, if you knew for a while that duplicated UAs are an exploit and, I assume, you also knew about FD policy on cheating and exploiting - you should have figured out much earlier that you experimental data is not credible? It like 1+1=2.
I think you should assume "can do" attitude and be in the first to confirm if multiple non-cheat UAs would solve the puzzle or not (I have little doubt after Kerrash tip)
 
So it seems that the 'And here the wheel' hint was the one about the special weapon in the book:
where five of them were needed in five ships, fired all together, to make it work.
I remember, one month ago, after reading the book, was the first thing I was suggesting: five ships with five UA each, but as we had just three of them, and they were so hard to find, it seemed almost impossible to me to achieve... at that time at least... :(
 
Last edited:
So, if you knew for a while that duplicated UAs are an exploit and, I assume, you also knew about FD policy on cheating and exploiting - you should have figured out much earlier that you experimental data is not credible? It like 1+1=2.
I think you should assume "can do" attitude and be in the first to confirm if multiple non-cheat UAs would solve the puzzle or not (I have little doubt after Kerrash tip)

Easy tiger.
 
So, if you knew for a while that duplicated UAs are an exploit and, I assume, you also knew about FD policy on cheating and exploiting - you should have figured out much earlier that you experimental data is not credible? It like 1+1=2.
I think you should assume "can do" attitude and be in the first to confirm if multiple non-cheat UAs would solve the puzzle or not (I have little doubt after Kerrash tip)

Firstly, to echo Bitstorm, let's all have a biscuit and a sip of whisky (or your other favourite/permitted beverage).

I will stick my neck out at this point and say that whatever 'critical mass' of UAs is required, and specific circumstance they need to find themselves in, was not, in fact, triggered when UAs were being duped and that, actually, the community came very close to the solution entirely accidentally due to the bug - but not quite close enough.
 
So, if you knew for a while that duplicated UAs are an exploit and, I assume, you also knew about FD policy on cheating and exploiting - you should have figured out much earlier that you experimental data is not credible? It like 1+1=2.
I think you should assume "can do" attitude and be in the first to confirm if multiple non-cheat UAs would solve the puzzle or not (I have little doubt after Kerrash tip)

Wow, talk about hindsight eh?

Duplicating UAs is an exploit/bug and was not used intentionally. Were we to know that UAs are individually tagged or to know the coding mechanics behind them?
 
So it seems that the 'And here the wheel' hint was the one about the special weapon in the book: where five of them were needed in gove ships, fired all together, to make it work. I remember, one month ago, after reading the book, was the first thing I was suggesting: five ships with five UA each, but as we had just theee of them, and they were so hard find, it seemed almost impossible to me to achieve... at that time at least... :(

Yeah I said this in the last thread, toward the end. Didn't get any airtime, sadly.
Although I put the details in a spoiler in case anyone was reading the book and hadn't got to that point yet! ;) J/K
 
Yeah I said this in the last thread, toward the end. Didn't get any airtime, sadly.
Although I put the details in a spoiler in case anyone was reading the book and hadn't got to that point yet! ;) J/K

Oops! From mobile everything is so hard to achieve! ;)
 
Not sure if it helps but here's the first 5 mins of the HR1185B (20 mins) recording with the howls removed
(to get back to your recognised sounds just double the playback speed)

https://drive.google.com/file/d/0B57cdY0ggG50alF0ZUZFMWJia1k/view?usp=sharing

Also have 3.5 mins of HIP28711 with howls removed however due to the short sample there are extra bits on the result, it is however obvious which they are as their timing is way off

https://drive.google.com/file/d/0B57cdY0ggG50YTZuaDdaclZUTkE/view?usp=sharing
 
Last edited:
or may be he telling us Frontier haven't yet figure out how to fixed the bug but have manage to make sure that it can't be exploited to crack this puzzle. It possible that their back end systems do detect the bug and do make sure commanders acitvely using it are punished.

Fair point, but it misses something: at times some commanders have, in good faith, conducted tests with UAs that were passed to them by others rather than found themselves. This could include Doop UAs. Such a 'blind' punishment in the case of a UA's origins would hardly be just. All still a big If, though fingers crossed for a test.
 
Last edited:
So, if you knew for a while that duplicated UAs are an exploit and, I assume, you also knew about FD policy on cheating and exploiting - you should have figured out much earlier that you experimental data is not credible? It like 1+1=2.
I think you should assume "can do" attitude and be in the first to confirm if multiple non-cheat UAs would solve the puzzle or not (I have little doubt after Kerrash tip)

As I've said repeatedly to you, we filed a bug report. We were not asked to dispose of the UAs, warned against using them, nor were they removed. That's pretty clearly implied permission to continue to use them, IMO. Again, we did everything we were supposed to do. There have been plenty of other cases where cmdrs have benefited from bugs or mechanics that border on exploits and FD have (on the whole) been content to let them keep their (arguably ill-gotten) gains.

Edit: And just to clarify, the palladium scooping was after the UAs duplication, it was the prize Arcanonn organised for the first recovered UA. When the UA was duplicated I had not seen the bug before, and while it was suspicious, it wasn't clearly a bug. It could have been intentional behaviour by this rather unique thing we'd only just encountered for the first time.
 
Last edited:
Oops! From mobile everything is so hard to achieve! ;)

Isn't it just! I wish they'd do a proper mobile build of ED - not exactly sure what it'd do. Even exploring the galaxy map and planning routes (that were actually persistent!) would be nice!

Actually - employing NPCs to trade on your behalf would be good, so you still make profit, only less so because they take their cut... Anyway, that's completely O/T...

Where did I leave that pitchfork...
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom