WARNING: WARNING: DONT USE STORAGE AT ALL.

Thanks for the warning. One of the first items on my list of things to do once the update downloads was store some engineered modules to make way for experimentation. So this might have saved me.

Good luck getting your save back, but I'm sure it will be fine. I'd be astonished if Frontier doesn't have a good backup system that lets them fix this kind of thing.

you can still store them it's just transferring them back to your ship from storage that causes an issue, i stored a 6d shiled with a class 3 mod on it and i'm still bale to access the game, wont be putting it back on a ship until i find out its fixed
 
Oops I've just moved 50 modules to storage, I guess I won't be putting them back to ships before this is resolved.
 
Well, lucky me; only one hour before that warning I happily transfered every module from my mining Python to my new Anaconda.
Nothing happened so far...
 
i think unique applies to modules you can only equip once, like shield-gens, fuel scoops....; and the transfer to ship option doesn't check if it's already installed. -> 2 shield gens -> corrupted commanderData, does that make sense?

at least that's what i think, worked for me so far
 
Please make sure you have raised a bug report.

Did that before I came here and to Reddit. As of yet, the ticket hasn't been addressed and the account is still broken. But one assumes they're busy desperately bug tracing.

what was the rating of the shield gen? I'd guess that your shield gen operating mass did not support the Beluga and the game glitched out. You can't install a shield gen when ship's hull mass exceeds max mass attribute

The Shield was Rating 6, moving it into the first 6 slot. I spent a while checking all my other ships for bits to cannibalise and I'd taken it from the Cutter, so I've still got all my notes here with me. The Core Internals were a R7 FSD, 6 Power, 7 Thrusters, 6 Distributer, all taken from elsewhere and engineered.

I can't tell you the mass because I can't look into my account, but it may have been the power instead, as the Beluga has a Class 6 power which I've got down here as I needed to purchase from elsewhere, none of my other big boys having that small a size. Thinking about it, I should add this to my ticket...

You do also have modules marked as red, which can cause crash to main menu, if the price of the module is greater than your current balance, because the game for some reason thinks you're "Buying" it from Storage, even though the transfer cost is free. They're still usable however, it's just another bit of wobbly programming. However the shields were under that cost.
 
I have never seen a game so bugged on a patch launch that they have to put a warning in the main menu, telling you not to use the features. Only FD could achieve this...
 

Deleted member 110222

D
I have never seen a game so bugged on a patch launch that they have to put a warning in the main menu, telling you not to use the features. Only FD could achieve this...

At least they gave a warning...

But by rights this should never have happened.

I won't be playing until it is fixed.
 
I have never seen a game so bugged on a patch launch that they have to put a warning in the main menu, telling you not to use the features. Only FD could achieve this...
You must not play many games then. I have seen game updates wipe out entire boot sectors.
 
Did that before I came here and to Reddit. As of yet, the ticket hasn't been addressed and the account is still broken. But one assumes they're busy desperately bug tracing.



The Shield was Rating 6, moving it into the first 6 slot. I spent a while checking all my other ships for bits to cannibalise and I'd taken it from the Cutter, so I've still got all my notes here with me. The Core Internals were a R7 FSD, 6 Power, 7 Thrusters, 6 Distributer, all taken from elsewhere and engineered.

I can't tell you the mass because I can't look into my account, but it may have been the power instead, as the Beluga has a Class 6 power which I've got down here as I needed to purchase from elsewhere, none of my other big boys having that small a size. Thinking about it, I should add this to my ticket...

You do also have modules marked as red, which can cause crash to main menu, if the price of the module is greater than your current balance, because the game for some reason thinks you're "Buying" it from Storage, even though the transfer cost is free. They're still usable however, it's just another bit of wobbly programming. However the shields were under that cost.

okay, so my guess is wrong then. I thought you were able to put a rating 4 shield gen in, which should not have the required attributes.
 
okay, so my guess is wrong then. I thought you were able to put a rating 4 shield gen in, which should not have the required attributes.

You may not be, it's hard for me to know now what the game was doing, as it locked up and booted me mid transfer. It might have been trying to move it from storage to a different location it wouldn't fit, or... My memory is that the ship was clear, but memory is a tricky thing. My commander is in the hands of the database bods now...
 
The record for that goes to batman arkham Knight
And it is still the undisputed King of PC game failures considering people still can't get that hot mess to work without manually configuring config files and messing around with grapgics drivers and etc.

At least FD are truly committed to the continued improvement and fixing of their game unlike a drop and run developer like Rocksteady.
 
Strangely I used storage to store a shield generator, and the fit a cargo bay. then without taking off, I took the cargo bay out (I needed it to hand in a mission) and fit the shield generator back on.

The shield generator is one of the items Frontier were talking about with the storage bug.

So the only thing I can conclude is, if you use it correctly, there is nothing wrong with storage.
 
i have the same problem i done it before the message went up and have tried the fix i still cant get on i am now sitting here in tears lol
 
Back
Top Bottom