Unknown Artefact (or artifact) Community Thread - The Canonn

Status
Thread Closed: Not open for further replies.
Nice, Very similar to mine. Main difference I use 2 x 6B cells, with a 5A scoop and less cargo.....weapons wise I just go 3G Pulse with a couple of 2GMC's, I find I can fire for ages without putting to much into weapons.
Yeh, I know, Im just lazy. Those 2 turreted beams do 99% of the work for me with no heat issue, if I put usefull weapons in the other slots, I would just use them and overheat. I do keep promising to swap up my SCBs when I next go back for a refit, but forget.
 
On that note: if you find yourself with gaps when the purrs are muted, you can try using the "no more than 2" rule to fill them. So if you see something like:

-''--<muted>

(or 01100<muted> for those that prefer the binary notation)

You can probably assume that the muted purr is a high/fast purr, since there were two low/slow purrs before it. Most likely you won't be able to fill all gaps, but you should be able to fill some of them.

Still, when you do this it'd be good to keep that annotated slightly differently, to indicate that it was done (makes it easier to reinterpret/apply new gap filling rules later if you mark the gaps).


If you are lucky you can get a full 4 minute string of purrs this way, and a couple of "unknowns" are manageable if you plan to decode it. You "only" get 2^n different combinations for n number of unpredictable purrs. Of course this wont really work with recordings near "long"-named bodies.

Dont go crazy with it or you will hear purrs and howl when you try to sleep, i have not managed to make sense of any of it :(
 
Hafnium Convoy Report:
Ceto - Unpopulated System between Azerleach and Timocanu
00:00 Lawless Hafnium Convoy encountered. Normal T9+2 Conda wing, + extra defence wing
00:01 Approach to within 400m, using Power Management for fine speed control
00:08 T9 starts pre-jump wobble, extra defence wing jumps
00:10 Jump to YIN SECTOR ZU-Y B3 (Unpopulated) - Both Condas still in attendance
00:14 T9 and Wing enter normal space - Approach to within 250m
00:19 T9 starts pre-jump wobble. Continues for longer than normal
00:21 Jump to YIN SECTOR WO-A B1 (Unpopulated) - Both Condas still in attendance. T9 begin odd circling flight, almost as if attempting to interdict
00:25 Single Conda enters normal space, lost from Wing
00:31 Circling Flight Pattern continues, so interdicted T9. Destroyed Conda Wing, took down T9 Shields, Hatchet Breakers till empty, deploy Collector Limpets. 3 Charges of my dual A5 SCB used, heat damage taken.

Getting close did not prevent the T9 from jumping. When within 250m, the pre-jump wobble did take longer than previously noticed, but only by a minute, not long enough to make a difference with a UA

Ok, here's my report. Python in Timocani.
00:00 Hafnium convoy contacted, T9, 3 condas, 3 vultures (or may 2 + dropship, I didn't care enough to pay attention).
00:01 After scanning T9 drop back to 3km
00:04 Extra wing peals off and jumps leaving T9 and 3 condas
00:08 T9 charges FSD, condas peel off and start jump, I close to mass lock the T9. Condas jump maybe 10 seconds before T9. I didn't scan the conda wakes, probably should have.
00:09 T9 jumps Jita Ten. No condas to be seen
00:10 I interdict, and strip his shields. Hatchbreakers fail to do the job even when they get through the point defence. Reducing cargo hatch doesn't seem to help until it hits 0% when a single battle weapon falls out. Once the hatchbreakers run out I give up as a conda and an eagle system authority ships have been harassing me. A UA should be easier as it'll be causing it's own damage.

This matches what I was seeing in 1.2, except I think I was able to masslock the T9 for longer. Back then shooting the T9 after the condas jump seemed to make it cancel the jump, didn't test that this time as it completed its jump faster than I was expecting. So it looks to me like hanging back means the extra wing jumps sooner and means the condas might not jump to the same destination as the T9. We need more evidence but I think my tactics make it a little easier to isolate the T9.
 
This matches what I was seeing in 1.2, except I think I was able to masslock the T9 for longer. Back then shooting the T9 after the condas jump seemed to make it cancel the jump, didn't test that this time as it completed its jump faster than I was expecting. So it looks to me like hanging back means the extra wing jumps sooner and means the condas might not jump to the same destination as the T9. We need more evidence but I think my tactics make it a little easier to isolate the T9.

I will try and hang back next time, see if I can get the wing to break up immediately, never seems to happen to me.
Odd that the hatchbreakers didnt do their job, they do seem a little flakey sometimes, but when I launch 3, I expect 1 to attach.

You cannot mass lock a ship jumping to another system at all. Only when going to SC in the same system.
 
I will try and hang back next time, see if I can get the wing to break up immediately, never seems to happen to me.
Odd that the hatchbreakers didnt do their job, they do seem a little flakey sometimes, but when I launch 3, I expect 1 to attach.

You cannot mass lock a ship jumping to another system at all. Only when going to SC in the same system.

Some of the hatchbreakers did attach but I still got the "failure to siphon resources" message eventually. Not sure if it makes a difference, but I am using a rubbish controller (it's all that was available where I was at the time).

It's not mass lock in the same way that happens with jumping to SC, it's probably just that the T9 charges it's drive a little slower than the condas. My previous tactic was to let the condas jump and then shoot the T9 to get it to cancel the jump, though if it jumps to a different location that's nearly as good.
 
Any suggestions as best sytem to hunt in ?

It's... impossible to know.

Granted Timocani has the most hits, but thats likely because more people search there. For all we know the UA convoys may occure any where in human space. One was recently found in an independent system which kind of blows the doors off the "feds only" theory.

That system did have a fed owned station in it though. The convoy itself was an indie faction sys-sec fleet. Not even a Navy fleet.
 
Last edited:
Hi All. Been hunting for 3 days in 109 virginis around 6 hours a day jumping on all signal sources. Nothing.

Any suggestions as best sytem to hunt in ?

We suffer from SSSSS (Statistically Small Sample Size Stupid) to the extent that any advice is purely circumstantial. Mine would be:
Avoid Conflict Zones (Timocani has bee sucky for me since the war broke out)
If you see a Convoy and is has other than UA, Hafnium, HE Suits - Go elsewhere. I have never seen Aniquities, Painite etc in Timocani.

Try the confirmed locations on the Wiki (link on Page 1)
 
Hi All. Been hunting for 3 days in 109 virginis around 6 hours a day jumping on all signal sources. Nothing.

Any suggestions as best sytem to hunt in ?

Timocani is popular as a few UAs have been found there. But 109 virginis is also a confirmed location so it probably doesn't make any difference. No one has confirmed getting a UA from an unknown signal source or a weak signal source so for maximum efficiency only check out strong signal sources. Look for the chat messages from the type-9, if they don't show up then you can ignore that convoy (though I recommend practising on the other convoys).
 
Hi All. Been hunting for 3 days in 109 virginis around 6 hours a day jumping on all signal sources. Nothing.

Any suggestions as best sytem to hunt in ?

LIke others have said, not enough data.

Realistically I think you have to accept that when hunting a UA, 3 days nothing.

You might be lucky, you might not, it was 3 weeks for me. =(
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom