News PLEASE READ: Module storage and unique modules!

Status
Thread Closed: Not open for further replies.

Sans Daring

Sans Daring
Brett C said:
I would err on the safe side and say, don't use it until the client update comes out for it.
Click to expand...

Hi Brett. Is there any broadly roughy indication when you think that update might be? A little grounded right now with a semi-stripped ship, so naturally a little curious. :)
 

Gswine

Gswine
Ok, thanks Brett. Appreciate that this is being worked on.

Sans Daring, I'm in the same situation so you have my sympathies. For some reason it seemed like a good idea to test modded A3 Prismatics on a Python before patch...


Just realised I should ask, is there any eta on a hotfix, Brett?
 
Last edited:

efelstead

E
Hi Cmdr
I am just about to purchase a Python after many months of work accumulating the funds.
I want to upgrade many of the standard modules to abetter class.
Can I continue with my purchase and outfitting without worrying about this problem.
As far as I can remember I don't have any modules in Storage but I will be fitting
more than one module of the same type eg Two shield boosters in the Utility slots
 

The Ellis

T
the silence is killing me. where is the hot fix? where did the warning message go on the log in screen? how come I still can't log in? what's next?
 

Doolittle

D
TheLawful said:
I'm sure FD know how to implement simple condition checks. Plus, I'm sure their code compiles, doesn't mix up class and instance methods, does proper null checks and also ensures thread safety. Apart from that, I'm confident too that the fix will be easy once the exact cause is identified, but that's another matter.

The overall level of quality ED delivers in such a complex scenario has always impressed me, and bugs just happen regardless of whatever QA level you apply, even nasty ones. YMMV [noob]
Click to expand...

Well said. Plus the fact the ED is an ongoing in dev title, bugs will get by and make into the wild, regardless of how bad, or annoying they can be. I'll criticize, throw stupidity to the wind, but EDs quality is nothing to be laughed at. With that kind of quality, when something isn't up to snuff, the rants can get obtuse.
 

Vandaahl

Vandaahl
amadeus1171 said:
Seriously? The programmers 'd this?! It's a simple check, people!

class UniqueShipModuleException : Exception
class ShipModule
class UniqueModule : ShipModule
class Ship {
private:
Ship Module ship.shipModules[]
}
function Ship:InstallModule(ShipModule shipModule)
try {
if shipModule.isUnique() and ship.contains(shipModule.getModuleType())
throw(UniqueShipModuleException())
} catch() {

}
Click to expand...

DocPossible said:
Very good. Have a cookie.
Click to expand...

<takes cookie away from amadeus>

Who on earth learned you to catch an exception and do nothing?
F
Again!
 
Last edited:

Starstrydur

Starstrydur
I have moved a 6A FSD, 4A milticannon, 3C multicannons, all modded, to storage from a Conda. Then equipped them to another Conda. When equipping to another Conda I first moved the guns to storage. For the FSD I did went to the stored section picked the stored modded FSD and mounted it while storing the current one. No problems there. This suggests the bug is related to optional internals and by doing something outside storing, then equipping. This was done about 24 Hours ago.
 

PhantomWolf

PhantomWolf
The Ellis said:
the silence is killing me. where is the hot fix? where did the warning message go on the log in screen? how come I still can't log in? what's next?
Click to expand...

I'm in the same boat, locked out and no reply from support as yet ...hope they can get us up and running today
 
Last edited:

amadeus1171

amadeus1171
DocPossible said:
But I guess an awesome programmer like you never ships code with any bugs in at all. Ever.
Click to expand...

Never, ever, because I employ solid engineering practices.

In my line of work bugs equals someone's life. The bugs are caught in the testing phase using pretty much complete test cases.
 
Last edited:

Eymerich

E
Brett C said:
Takes time to create the code to fix it, get approved by QA, wait for the build to compile. Patience. :)
Click to expand...

Thanks
for the answer.

If I may give a suggestion, I would consider to restore the "warning" message on the main screen: otherwise someone could think the issue is solved.

:)
 

CitizenLee

CitizenLee
Seems to be working as advertised now.

I got back to my home station, sold x4 modded Shield Boosters I had fitted to the Anaconda, swapped into the FdL and bought the Boosters back. I then got back in the Conda and stored a G5 modded Charge Enhanced Power Distributor, got back into the FdL and then retrieved the module from storage. I then shut the game down and logged back in with no issues at all.
 

DocPossible

DocPossible
Status
Thread Closed: Not open for further replies.
Back
Top Bottom