Unknown Artefact (or artifact) Community Thread - The Canonn

[Derthek]

Ya now that you mention it - especially early on i managed to toast myself while jumping more than a few times .... I was thinking how we have the power settings - can we rig it somehow that during the countdown the FSD gets turned off due to power management settings ?

1. 0 throttle
2. start FSD powerup
3. FSD charge complete
4. increase speed to just under threshold
5. another CMDR lets 3 gimbal beams loose on your FSD
6. As the drive nears malfunction health, increase throtle to jump speed
7. other CMDR keeps the pressure on right up until the point of jump
9. Thargoids

 

[Tallsword]

Could they be trying to tell us that there IS a way to do a misjump?
The final report indicated that it was most likely caused by the unlucky failure of a single component during the start of the jump, causing a small fire in a key part of the drive that resulted in a massive explosion and consequent misjump at the same time.
Funny thing - I was trying randomly to do that yesterday. Maybe the UA helps cause misjumps ..... Which components is it damaging most ????
Edit: also says
The final safety report into the incident found there were insufficient safety precautions within the internal drive systems
Will have to check if this is player submitted or not ...
Edit again ... ha ya this thread goes too fast for me - sorry

Seems like you didn't read my post right on the page before...

The news are starting to fortify one of my ideas... It might be nothing more than a lost UA if made carelessly, thats why I neglected to mention this idea...
The news is speaking about "Drive failure"... What if all we have to do is jump from A to B while the FSD is nearly broken or broken while we have a UA on-board? ofc a broken FSD means that we cannot jump anywhere from the said moment... but what if we can? thanks to the UA! Its a bit of a fuzzy idea, but it could be worth a try if someone acompanies the vessel to make sure the UA stays safe, even if the other person has to self-destruct. It also mentions the fact that these were colossal ships, maybe it'd be worth sacrificing some money to try this in an Orca or Anaconda.

Also, an FSD breaking while there's a count-down would be another test as well...

We should compare the two cases: SS1 and that ship from 3251... Similarities and differences are the key to solving it imo.

Edit: Seems like some1 got my idea while I wrote this :3

 

[Derthek]

or, as the drive is charging i suppose you could just go to your modules tab and shut it off. Ive never actually tried that.

edit:

nvm im pretty sure the side tabs dont pop up while the drive is counting down. nvm.

 

[Zenith]

I'm thinking there might be mileage in rizal72's suggestion.

Have a number of Cmdrs at various distances recording a UA from multiple viewpoints.
Have 1 Cmdr sat facing "down the barrel" while the UA decays down to 0%.
When the UA is at 30s to full decay, have the Cmdr in front of the UA charge up a hyperspace jump with the throttle at zero.
As soon as the UA screams and "explodes", punch full throttle to engage the jump.

The idea is that the UA explodes, sends out the pulse/plasma/distortion exactly where the Cmdr's ship is and the Cmdr in question fires the FSD jump to try and coincide with the pulse.

If it works, whoa!
If it doesn't, we've tried something different.
This is based on the detail of the misjump in the Galnet article today.

 

[bitstorm]

3 of us doing this Biscuit Barrel event, one with a UA, where is everyone?? =(

 

[Zenith]

3 of us doing this Biscuit Barrel event, one with a UA, where is everyone?? =(

I'm still on holiday.

 

[rizal72]

CMDRs!
The Antares accident on Galnet today is an hint without ant doubt, believe me...
And the T9 experiment some of you are proposing is THE TEST!
I agree that the Convoy could be doing that kind of experiment, and the "have you listened to THEM" gets a very new meaning in my mind as well.
And the SS1 was a huge ship indeed, so, if was carrying the UA, that could have triggered the unfamous misjump.
I strongly invite all the bearers to move their minds towards the MASS JUMP MIS-JUMP TEST

@Zenith: thanks for remembering to everyone my test "Expiring UA with a ship close to its mouth with FSD loaded"

PS I'm on the beach, for the next 3 weeks...

 

[Tallsword]

3 of us doing this Biscuit Barrel event, one with a UA, where is everyone?? =(

I'm currently in Ugrivirii... Quite far away and my Python is not well equipped for the task... Gonna miss out on it this time, need to earn some creds to upgrade before heading out to find a UA.

 

[simulacrae]

Seems like you didn't read my post right on the page before...

ya hence the thread comment

 

[bitstorm]

I'm an idiot, biscuit barrel is the 9th, I assumed this Sunday.

Might as well make a brew and do another round of SSSs I suppose.

 

[Derthek]

I suppose I could fire up a T9 if no one else steps up to the plate.

 

[simulacrae]

3 of us doing this Biscuit Barrel event, one with a UA, where is everyone?? =(

can't make it for biscuts ... sorry

 

[Kyp Shard]

I strongly invite all the bearers to move their minds towards the MASS JUMP MIS-JUMP TEST

Make that the BIG-SHIP MASS JUMP MIS-JUMP TEST

 

[Tallsword]

CMDRs!
The Antares accident on Galnet today is an hint without ant doubt, believe me...
And the T9 experiment some of you are proposing is THE TEST!
I agree that the Convoy could be doing that kind of experiment, and the "have you listened to THEM" gets a very new meaning in my mind as well.
And the SS1 was a huge ship indeed, so, if was carrying the UA, that could have triggered the unfamous misjump.
I strongly invite all the bearers to move their minds towards the MASS JUMP MIS-JUMP TEST

@Zenith: thanks for remembering to everyone my test "Expiring UA with a ship close to its mouth with FSD loaded"

PS I'm on the beach, for the next 3 weeks...

Are you sure the SS1 was escorted to A-letter system? The way I understood it went alone and the galnet states nothing about escorting vessels, does it?
We are also able to follow those T9s... I think it's more about the FDS degrading to a point where it misjumps or completely breaks (will need a second player rescue and maybe self destruction... but even if carried in a conda or T9, it might be worth making this few-million credit sacrifice I previously mentioned... FOR SCIENCE!)

 

[Nicholas Powell]

Biscuit Barrel Note

The slated date for the exercise was Sunday 9th August.
Those of you in Timocani and frustrated at a low turn-out, I suspect the original text's mention that it was (while stated as 9th August) 'still before the Gamescon announcement' might be the root of this enthusiastic but week-early turn-out. I was wrong about that, the Gamescon announcement. Still, it's still down for the 9th. I hope this won't stop you doing well, those of you there and perhaps remaining there today. Good Hunting, Commanders! (Hope that 45min spawn rate bumped up for you, Dommarraa.)

Since this was a misfire, Biscuit Barrel is still slated for 9th August.

(Am in-game myself but cannot commit to a shift of any meaningful length so, sorry, probably won't be joining you tonight.)

 

[Ratking15]

I don't understand what you mean by this, there is no "computer core" module?

UA = Computer Core

Look at the last post on Galnet, there was a fire aboard the antares, which could have over heated the engines. I say someone should enter into silent mode, charge the engines, wait until they reach above 150 degrees an then align to your destination and jump.

As far as I know we can't affect anythinng on the ship computer core.

Actucally in the article it says this:

The final report indicated that it was most likely caused by the unlucky failure of a single component

That is because there was no wreckage offically found and the mystery wasn't solved it was all speculation about what was known.

Also the new frameshift drive took the old one and decreased the time by sooo much so the computer cores of that time may not have been able to handle the required power and such, also computer cores often have their own little power source that's unshielded making it easy to cause problems for people in contact with it.

 

[Derthek]

If I sold everything I own, I could make this. I don't think it gets much heavier than that.

edit:

nvm! this is heavier haha

edit 2:

Yup i think thats as heavy as she gets. Even the Anaconda is slightly lighter. Both the Dropship and the Clipper are significantly lighter as well.

 

[rizal72]

Are you sure the SS1 was escorted to A-letter system? The way I understood it went alone and the galnet states nothing about escorting vessels, does it?
We are also able to follow those T9s... I think it's more about the FDS degrading to a point where it misjumps or completely breaks (will need a second player rescue and maybe self destruction... but even if carried in a conda or T9, it might be worth making this few-million credit sacrifice I previously mentioned... FOR SCIENCE!)

I invite you to read carefully the Galnet posts about thr SS1: the escort has slaved their jump to the SS1 an they misjumped as well but went back to normal space with damage as well, while the SS1 disappeared.
BTW I support any kind of FSD RELATED test, in any form.
That's why the brave bitstorm is doing that in the last 3 days, under my insistent requests... And not only mine

 

[Kyp Shard]

Are you sure the SS1 was escorted to A-letter system? The way I understood it went alone and the galnet states nothing about escorting vessels, does it?
We are also able to follow those T9s... I think it's more about the FDS degrading to a point where it misjumps or completely breaks (will need a second player rescue and maybe self destruction... but even if carried in a conda or T9, it might be worth making this few-million credit sacrifice I previously mentioned... FOR SCIENCE!)

I think it's pertinent that the escorting anacondas drop out as you follow the convoy, eventually leaving the T9 alone. Where do they go? Why? And Why Anacondas - to protect the T9 or to be sent by the T9 somewhere on the offensive?

 

[bitstorm]

1. 0 throttle
2. start FSD powerup
3. FSD charge complete
4. increase speed to just under threshold
5. another CMDR lets 3 gimbal beams loose on your FSD
6. As the drive nears malfunction health, increase throtle to jump speed
7. other CMDR keeps the pressure on right up until the point of jump
9. Thargoids

In between errands for people, testing for the last 3-4 days for me has been.

Modules all at <40%.

Get timer.

1. Jump
2. Start 12 second countdown as entering system
3. Point to next waypoint
4. Alarm goes off
5. Start jump - FSD charging
6. Corrosion event happens right during the 5 seconds countdown period
7. Goto 1

Spent a good amount of hours doing this now.