Unknown Artefact (or artifact) Community Thread - The Canonn

Status
Thread Closed: Not open for further replies.
I have an audio question.

I'm trying to record audio from elite with audacity and I keep getting noise in my recordings. Even when recording silence there is noise in the playback. What am I doing wrong?

could be a range of things

Perhaps try to isolate the problem......record without elite running and see if the noise is still there.

Could be a faulty ground/earth

Could be a bad connector

Try to cut out various things and see if you can determine where the noise is coming from
 
Apologies for "Yet Another Summary/Recap post", but looking at the avenues open to us, as opposed to specific theories:

- Analyse the UA sound: I think this has been done to death, if there's more in there beyond the location Morse I think it's beyond us to find it.

- Do something with the UA: we've poked and prodded it* (*not yet mated with it!), honked, spat and chatted it up. Again, I think we've reached a dead end.

- Do something with the UA in a specific location: possible, but with 400 billion systems we're going to need a clue, and if we've had one (or more), we've missed it.

- Ignore the UA itself, and focus on the convoys, and/or the systems they were found in. My favourite, at the moment.

I'm currently tested a theory that - if I'm right, fingers crossed - confirms with 100% certainty that I haven't a clue what I'm doing or how to solve this.. My latest searches have been:

- Heracles (Cerberus link) : nothing.
- Shibboleth (near the UA drop systems, which means a word which identifies you as part of a class/race ...species? Seems appropriate as a key to unlock an artifact) Nada.
- Next up: all the confirmed UAs seem to have been captured in exploited systems. Don't even know where to start.. (Edit - not 109 Virginis, that seems to be the exception).
 
Last edited:
- Ignore the UA itself, and focus on the convoys, and/or the systems they were found in. My favourite, at the moment.


Perhaps look at where the convoys are from? I believe some people have followed the convoy for 2 or 3 jumps - if we draw a rough line through those systems and extend it backwards we should get an expanding cone of probabilities for the origin - I tried to do this but my mind doesn't like 3d visualization - it goes all wobbly....

I'd suspect that it can't be very far, given that t9s have a lousy jump range and the UA is eating it the whole time. Maybe 120Lys? I know the cone still has a lot of systems in it - but its less than 400 billion....

I have no idea what to look for - anything different I guess - in space or at stations....

Just out of interest - current research shows sirius as 70Lys from Timocani

Timocani is 77Lys from Sol
Sirius is 8 Lys from Sol

Therefore Sirius is damn near on a direct route to Sol - maybe the convoy is going to Sirius. I might go to Sirius tonight and hang around the drop in point to see if anything/anyone turns up....
 
Last edited:
Theory to add to the pile: Have someone get a ship and park it as close as they can to a dropped UA and point the nose of the ship in the same direction the head of the UA points at and begin charging their FSD. Keep the throttle at 0 and have a second person (probably someone who dropped the UA) record everything in good quality and tell the other pilot right when the UA is going to die and basically time it so that your FSD finishes its countdown and begins jumping just a moment after the UA explodes into spores. This both checks if jumping out of UA spores does anything and also checks if jumping at (around) the same time as a UA dies does anything. I would think it dying during the countdown lockdown would be close enough.

Having a second person recording it can also check the sounds and warp effects. One guy thought the latest recording of one dying sounded different than usual, like a crunch, and supposed it could have been due to someone having their ship somewhat close to it when it died. That will be checked as well as a theory of the thing making a weird broken warp effect when it dies, which hasn't been recorded properly since the first time it was noticed. Plus we can test one more "kill it in x area" theory.

All we'll need is a ship with good enough cooling to stay in a "throttle up to jump" state for a long time, plus someone in another ship in debug camera to record the UA close up in high detail+audio quality, then maybe a third person recording everything - the jumping ship, the UA dying, etc. Wouldn't be a bad idea for the jumping ship to record things too, but not necessarily in super high quality.

The last question would be do you high-wake or just supercruise jump? I guess if you point the same way as the UA and flick through your nav screen to see if its pointing at any system in particular you could make the decision to perhaps have a second person jump to that system while the first just goes supercruise.

Finally, you need to be moving at max speed to actually begin the countdown. That would require a short run-up, which could be made shorter by setting max pips to engines, boosting, then setting no pips to engines - dropping your top speed below your actual speed after the boost. A bit difficult, but does anyone know what ship could do that the best? One with high acceleration but low top speed.
 
I am getting bored of this thing really. There wasnt enough info to go on.

The test i wanted to do as for letting one finish its cycle. No one wanted to do that with the rare UA's.

I am done for now. I will help look for one on the 9th. I will be back in town for that.

As till then peace out brothers and sisters.

May the midi-chlorians find you well on the tests to come for not.
 
Theory to add to the pile: Have someone get a ship and park it as close as they can to a dropped UA and point the nose of the ship in the same direction the head of t...

Just so you don't feel like you're being ignored by a closed club or anything, there is a tacit agreement among us that if you want to try a destructive test, you go and find your own UA.

There is a meet up in Timocani in Möbius this Sunday if you want to help find one.
 
well. for me FD links the UA symptoms (failure of internal devices) to the loss of SS1 and then also Antares. i don't think FD is actively misleading people, and they claimed that there is something to be found out about the UA. Timing of those incidents, the articles and the hints fell together with the UA discovery. I doubt somehow that FD has those story lines separated.

I think that's pretty tenuous. Yes, the the UA causes internal damage. But so does toxic waste, so why are you assuming the UA has something to do with SS1 rather than toxic waste?
And how does the parallel drawn between SS1 and the Antares help your argument given that Antares happened years before the UAs appeared? People have tried extensively to get a FSD misjump when carrying a UA and it hasn't happened; carrying a UA does not cause the sort of incident that happened to SS1. As for timing, it wasn't particularly close. The UAs appeared with 1.2 on March 10th (though this group didn't acquire one until May 4th) and SS1 didn't vanish until May 26th. The timing is not obviously significant IMO.

I think we are prone to trying to make every about the UA even when there is little evidence. To me it looks like there are three mysteries in ED: the UA, Raxxla, and the disappearance of SS1. I don't think there is good reason to believe that any of them are linked, in fact if I were the devs I'd much rather run multiple separate mysteries than a single large one. It's more likely to engage more players.
 
Just so you don't feel like you're being ignored by a closed club or anything, there is a tacit agreement among us that if you want to try a destructive test, you go and find your own UA.

There is a meet up in Timocani in Möbius this Sunday if you want to help find one.


I'm working on it, but I thought I would put my idea here to see what everyone else thinks, or to see if similar tests have been done before.
 
Last edited:
in regards to the shuttle:

this sounds like an assassination attempt. Sean Richards clearly knew something that linked the Antares and SS1 and had to be taken care of. The software was likely made to fail in order to make it look like an accident.

conspiracy 101

in regards to the UA connection to SS1 & antares

it's... really hard to say. From what we know, mixed with a bit of imagination, the UA may be an artefact of a past era (imagine that, an artefact being an artefact) from the thargoid war some 300 years ago.

The thargoids could be entirely responsible for Antares & SS1 but that doesnt nessicarily imply Antares or SS1 had a UA on board.

The UA and the misjumps could be two separate things that both point to Thargoids.
 
I just posted a witty and massive theory post and although the auto save kept popping up as I posted it it's gone! UA interference! Actually this seems funny but it is actually TRUE!
 
What follows is a shortened version of my speculations and is in no way the truth....maybe.

The UA disrupts navigational controls and works well in conjunction with the frame shift drive. Mr Rodgers knew this so he travelled in a shuttle which didn't have a FSD but the UAs master still pancaked him into Patterson in normal space (by controlling navigation and maybe thrusters too). Experiments have been going on in one form or another for over fifty years, without many leaks save the elephants graveyard of ships one. As for SS1 there was no fire, no misjump the UA specifically targeted it and it went wherever if was instructed to go by the UAs fat controller. Got to keep the shareholders happy.

So to test this, well it's counter intuitive but firstly get the precious UA to target just when it's active (it does this through its scanner), then jump away from it normally with your FSD.

Ok maybe leave a guardian with it to prevent loss on test failure, but if the test succeeds may I be the first to congratulate you, as we wont be seeing you again, er probably. Maybe you'll get lucky and it'll only exhaust your fuel and the Rats will come and save you?

So the UA is a multiuse device that specifically targets and sends ships where it's master wants them to go....into a star, black hole, space station or the nearest public library, by misguiding the navigational systems.

Believe me this post is far shorter, makes less sense, is in no way witty, is less well constructed than the missing one and less well constructed, with more errors but is shorter for you the victim.
 
What follows is a shortened version of my speculations and is in no way the truth....maybe.

The UA disrupts navigational controls and works well in conjunction with the frame shift drive. Mr Rodgers knew this so he travelled in a shuttle which didn't have a FSD but the UAs master still pancaked him into Patterson in normal space (by controlling navigation and maybe thrusters too). Experiments have been going on in one form or another for over fifty years, without many leaks save the elephants graveyard of ships one. As for SS1 there was no fire, no misjump the UA specifically targeted it and it went wherever if was instructed to go by the UAs fat controller. Got to keep the shareholders happy.

So to test this, well it's counter intuitive but firstly get the precious UA to target just when it's active (it does this through its scanner), then jump away from it normally with your FSD.

Ok maybe leave a guardian with it to prevent loss on test failure, but if the test succeeds may I be the first to congratulate you, as we wont be seeing you again, er probably. Maybe you'll get lucky and it'll only exhaust your fuel and the Rats will come and save you?

So the UA is a multiuse device that specifically targets and sends ships where it's master wants them to go....into a star, black hole, space station or the nearest public library, by misguiding the navigational systems.

Believe me this post is far shorter, makes less sense, is in no way witty, is less well constructed than the missing one and less well constructed, with more errors but is shorter for you the victim.

Good theory :)

You should read the short story 'A Business Proposal': http://www.dream-ware.co.uk/first-e...s-of-life-on-the-frontier/a-business-proposal
 
The UA disrupts navigational controls and works well in conjunction with the frame shift drive. Mr Rodgers knew this so he travelled in a shuttle which didn't have a FSD but the UAs master still pancaked him into Patterson in normal space (by controlling navigation and maybe thrusters too). Experiments have been going on in one form or another for over fifty years, without many leaks save the elephants graveyard of ships one. As for SS1 there was no fire, no misjump the UA specifically targeted it and it went wherever if was instructed to go by the UAs fat controller. Got to keep the shareholders happy.

So to test this, well it's counter intuitive but firstly get the precious UA to target just when it's active (it does this through its scanner), then jump away from it normally with your FSD.

People have been observing UAs for months without any sign of disruption to navigation controls. I'm sure there have been cases of people jumping out of instances with UAs in them. There have definitely been plenty of cases of the people jumping to SC while a UA was dropped.

Anyway, if the UA disrupted the shuttle and/or SS1 it did it from inside the ship. No one in possession of a UA has reported any problems with navigation or FSD operation (other than the toxic cargo damage).
 
Update in game 30 minutes.....

- - - Updated - - -

People have been observing UAs for months without any sign of disruption to navigation controls. I'm sure there have been cases of people jumping out of instances with UAs in them. There have definitely been plenty of cases of the people jumping to SC while a UA was dropped.

Anyway, if the UA disrupted the shuttle and/or SS1 it did it from inside the ship. No one in possession of a UA has reported any problems with navigation or FSD operation (other than the toxic cargo damage).

Ah still letting facts get in the way of meaningful facts......dross....., Ryes point taken Sir and I suspected this...... Maybe the UA hadn't targeted them? I mean no you're right.
 
Unless I missed something, that testing mostly focused around doing reboots while jumping.

Someone did test a jump with heat damage ongoing, but I don't recall it being above the second tier mark of. 150%, was more like 130 at the time of jump (unfortunately my flaky Internet means I can't double check the video easily). That's why I was suggesting above 200% to guarantee thereshould no dripoff on jump interfering.

Granted this is likely to be another moot point, as I've got nothing more than anyone else to back it up.

I spent quite a bit of time testing heat induced misjumps right near a star, jump cancelling over and over, I certainly had it above 200, even 300. But generally I found the sweet spot in the 150-200 zone for "extended" testing without having your ship die really quickly and having to leave testing and "waste time" repairing.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom