WARNING: WARNING: DONT USE STORAGE AT ALL.

[Titler]

Hey all; you will see on the launch screen of the game there is now a warning that trying to put two "Unique" items on a ship that are taken from Storage, that is, something that you can only have 1 of, will corrupt your commander data.

I've just lost my data by installing a single item.

The cause then is NOT two, but more widespread than that, unless it's counting Engineering modifications as making the item unique; I had stripped the Beluga down to Core Internal items, the Optional were all empty, and moving an Engineered Prismatic Shield from Storage to Optional triggered it and corrupted my commander.

DON'T USE STORAGE UNTIL THE EXACT CAUSE IS KNOWN.

 

[ShadowWolf Kell]

Saw this when I logged in and decided to completely hold off on module storage in general. Really sucks.

Hopefully they fix it soon and don't have to roll-back any CMDRs afflicted with this.

 

[Martian Successor]

Jeezus... Thanks for the heads up man. Are FD able to restore your commander data after this error?

 

[m1dane24]

Woah! This should've been reported right away!

 

[Tikigod]

Jeezus... Thanks for the heads up man.

Are FD able to restore your commander data after this error?

Will be the same solution Frontier already outlined. Contact support, they'll remove the offending module and refund the associated cost of it.

 

[Gunnet]

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.

 

[viper666]

Saw the warning on the start menu, but thanks for the heads up. This could get ugly real fast.

 

[vrseven]

I am not even going to start playing for real real, until after a week goes by...lol

 

[Titler]

Jeezus... Thanks for the heads up man. Are FD able to restore your commander data after this error?

I've seen indications they might, but it's 3:30am UK time, so it'll be a few hours before I'll know for sure. I sent in a bug report as soon as it happened, then came here and to Reddit to warn you all.

You can still transfer items via Buy Back, so I'd recommend you all use that to move modules about for now.

 

[Jenner]

Official forum announcement thread on this issue:

https://forums.frontier.co.uk/showthread.php/300493-PLEASE-READ-Module-storage-and-unique-modules!

 

[Martian Successor]

Hope FD sorts out your Commander data and thanks again for the heads up.

FD are gonna need one of these:

 

[Faded Glory]

Official forum announcement thread on this issue:

https://forums.frontier.co.uk/showthread.php/300493-PLEASE-READ-Module-storage-and-unique-modules!

Yes, but unless I'm misunderstanding the OP, that is not the issue. OP is saying he transferred a module from storage into a ship that did not have another module of the same type already there. If that's the case, then it would seem that just the act of transferring a module (particularly an engineered one) from storage to a ship will corrupt your CMDR data.

Painful if this is the case, and I'm kind of scared to try now...

 

[Titler]

Official forum announcement thread on this issue:

https://forums.frontier.co.uk/showthread.php/300493-PLEASE-READ-Module-storage-and-unique-modules!

Thanks for pointing me towards that; I looked in Bugs and Discussion but couldn't see a sticky. I'll post there too, but just to re-confirm, that information must be wrong. My ship was absolutely empy in Internals when it corrupted my Commander, so the issue must be wider than understood.

 

[Swan Electro]

Wow. That's awful.
Kind-of par-for-the-course,
but awful.

 

[Codger]

Thanks very much for the heads up. It's most appreciated.

 

[Faded Glory]

Just want to update this...

Very nervously, and expecting disaster, I transferred an engineer updated shield generator back to my ship, having previously removed the existing shield generator, and no problem.

I did this three times, so not sure what exactly happened with you.

I removed the existing shield generator from the ship. I transferred one from storage to the ship so I could engineer it. No issues.

So, to anyone wanting to do this, obviously I cannot guarantee anything, but I have just transferred previously engineered shield generators from storage to a ship so I could upgrade their engineering mods, and my save has not been corrupted.

 

[racer1]

Hey all; you will see on the launch screen of the game there is now a warning that trying to put two "Unique" items on a ship that are taken from Storage, that is, something that you can only have 1 of, will corrupt your commander data.

I've just lost my data by installing a single item.

The cause then is NOT two, but more widespread than that, unless it's counting Engineering modifications as making the item unique; I had stripped the Beluga down to Core Internal items, the Optional were all empty, and moving an Engineered Prismatic Shield from Storage to Optional triggered it and corrupted my commander.

DON'T USE STORAGE UNTIL THE EXACT CAUSE IS KNOWN.

Please make sure you have raised a bug report.

 

[AreZee]

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

 

[cptdavep]

I suspect they'll have all hands on deck to get a patch out for this one! Hopefully it won't be too long.

 

[sutex]

I am not even going to start playing for real real, until after a week goes by...lol

Yeah doing the same , letting Third party apps sort their bugs out , while updating VA EDDI scripts, by then Frontier should have removed the watermark , and fixed what other bugs have crawled up