Should I re-engineer my FSD under the new system?

On my anaconda, my current FSD stats are, optimize Mass 2825t, Max Fuel per jump 8 tons, Mass 50.74 tons. If I remember right, I was near the top with a four or five percent bonus on the optimize mass under the old system. Would I benefit at all re doing it?
 
On my anaconda, my current FSD stats are, optimize Mass 2825t, Max Fuel per jump 8 tons, Mass 50.74 tons. If I remember right, I was near the top with a four or five percent bonus on the optimize mass under the old system. Would I benefit at all re doing it?

The maxed G5 range upgrade will grant you a +61.2% overspec with the Mass Manager Exp added. The original system was unable to achieve anything above +60% even in the rarest of God Roll situations. Sounds like your current overspec is in the mid 50s.
 
Last edited:
As you loose 1 grade when re-engineering a module, it is better to start over with a new one and save your current module for an other build.

Unfortunatly current system doesn't favor conversion from old system.
 
I was going to add, that if the OP is reluctant to loose the legacy module, he could just buy a stock FSD and take that up through the ranks and then compare.

I am 100% certain that once he compares the new G5 maxed version to his legacy module, he will then convert the legacy module and G5 max it to equal the new module, which will be a superior upgrade to his legacy version.
 
Last edited:
I buy another module, transfer to engineer station and then make changes to the new module.

Then change the old module and compare the results in outfiting.

All those glittering numbers appear and is easy to compare two modules. Takes work but is guaranteed to keep the best results .
 
I buy another module, transfer to engineer station and then make changes to the new module.

Then change the old module and compare the results in outfiting.

All those glittering numbers appear and is easy to compare two modules. Takes work but is guaranteed to keep the best results .

Good advice and what I always did back in 2.4 since it was always a crap shoot.

Under the new system two identical modules will have identical specs. when fully upgraded so no longer the need to bother with this unless you are trying to compare a legacy upgrade to a 3.0 upgrade. You're only likely to do this once, since the new system is always better with FSDs. ;)
 
Last edited:
On my anaconda, my current FSD stats are, optimize Mass 2825t, Max Fuel per jump 8 tons, Mass 50.74 tons. If I remember right, I was near the top with a four or five percent bonus on the optimize mass under the old system. Would I benefit at all re doing it?

The max increase in the new system is 62%. Compare yours with that.
 
On my anaconda, my current FSD stats are, optimize Mass 2825t, Max Fuel per jump 8 tons, Mass 50.74 tons. If I remember right, I was near the top with a four or five percent bonus on the optimize mass under the old system. Would I benefit at all re doing it?


This is what a max values G5 mass manager 6A fsd will have:

DXI-WeUU8AABv7O.jpg:large


I'd say the slight mass advantage of your legacy mod is negligible compared to the optimized mass increase you'd get with a 3.0 version.
 
Last edited:
I purchased new FSDs last week, engineered them up to G5 (Increased range), then compared them with my pre-3.0 engineered ones (also done up to G5.)
In all cases, the new engineer upgrades give a significant upgrade over the old system; e.g. my AspX gets an additional 4 or 5 light years with the new drive.

Potentially stupid question though: I've been choosing the "Deep Charge" experimental effect but I've seen a few mentions of the "Mass Manager". Is that a better option to go for, assuming that increased FSD range is the primary goal?
 
I purchased new FSDs last week, engineered them up to G5 (Increased range), then compared them with my pre-3.0 engineered ones (also done up to G5.)
In all cases, the new engineer upgrades give a significant upgrade over the old system; e.g. my AspX gets an additional 4 or 5 light years with the new drive.

Potentially stupid question though: I've been choosing the "Deep Charge" experimental effect but I've seen a few mentions of the "Mass Manager". Is that a better option to go for, assuming that increased FSD range is the primary goal?


For class 5 and above(ie your Asp), mass manager wins out.
It's also better in any case where using more fuel per jump is a problem.

https://forums.frontier.co.uk/showthread.php/403010-Mass-Manager-vs-Deep-Charge
 
Go for it. Lazily collecting Engineer stuff myself to max out all my ships' FSDs in the new system. Will kind of hurt a little on my Vulture which has a tier 5 FSD that uses less power than stock and I'll have to mess around with priorities a bit, but I plan on taking it on DW2, so I'll take the good with the bad.

Cheers.
 
My method has been to go into a station with Outfitting and then select your module and check your current modifications. Now open up a web browser and use Inara (inara.cz) to took at what the new system will do for you.

For the FSD for example go to (https://inara.cz/galaxy-blueprint/2/) and scroll down to the G5 and you will see the max 100% completion of G5 you will get, then look under for your Mass Manager or Deep Charge, depending on your FSD size and then you can compare yours with that and see which is better.

I have been doing this now with all my ships and modules and it makes it so much easier to determine what is worth it or not. I do have a spreadsheet with screen shots of all my pre 3.0 engineered modules though by ship, so it's easier to look at that for me, but most people didn't do that so Outfitting will be the best way, unless you added all your ships details into Coriolis or something...
 
I upgraded my AspX's FSD the other day. It was originally at 49.91Ly. Now it is almost 52Ly. The only thing I didn't like about changing to the new is that it downgraded me to lvl4 and then I had to go get mats to engineer it back up to lvl5. I needed the data material. I hate farming. Not just in this game but in any game.
 
I upgraded my AspX's FSD the other day. It was originally at 49.91Ly. Now it is almost 52Ly. The only thing I didn't like about changing to the new is that it downgraded me to lvl4 and then I had to go get mats to engineer it back up to lvl5. I needed the data material. I hate farming. Not just in this game but in any game.

I had a 52LY Asp with the pre-3.0 engineered FSD. I did what quite a few people here have suggested. I bought a new 5A FSD then upgraded it in the new system.

I tried a couple of different experimental affects and found the “Mass Manager” to work the best for my FSD and my ship.
My Asp now has a 59.x LY range.

I’ll go dig out a screen shot and maybe post my build if people are interested, tho’ I’m sure some people have better ranges than I.

Clicker

P.s. this build is my “bubble taxi”...has a few slots empty, lower rated core where needed, light weight pretty much everything.
No weopons and basically the weakest shield I think I could fit...but NOTE: I’m yet to engineer everything else to 3.0 specs!
 
I had a pretty high end G5 FSD on the anaconda (62 LY fueled). Converting it to max G4 on the new system brought it down to 58 LY. I have not yet upgraded it to G5 as I don't haz the stuffs (curse you engineers) but I am pretty sure a top G5 would exceed the legacy module range.
 
Guess I would advise be careful.
I am unsure how (think it may be a bug) but I lost my G3 FSD upgrade upon converting a Legacy module to the new format.
Could have clicked wrong but it’s hard to imagine being so dumb.
 
The G5 upgrade to my legacy FSD in the Corvette resulted in a 2ly increase, which in a Corvette is found gold. It takes about 12 rolls to max out the G5 and you need to COMPLETELY max it out to get the top experimental effect numbers.

The other upgrade I have found to be worthwhile is the Palin DD5. It gave a higher top end and a bit better agility to the Corvette as well.

On the other hand, when updating Rails, one of my legacy Rails had better effects than a converted legacy at G5.

Unfortunately, FD chose to drape a veil of secrecy over the conversion process (forces you to do a complete upgrade to a plain module if you want to make a comparison to a legacy, can you spell G.R.I.N.D.?)
 
Last edited:
Back
Top Bottom