Elite Dangerous Launcher crashing all the time.

also "american ordering" is not YYMMDD... that would be reverse... if they actually used "american ordering" it would be way less confusing, i.e. 0420... oh maybe thats why they didnt haha
 
also "american ordering" is not YYMMDD... that would be reverse... if they actually used "american ordering" it would be way less confusing, i.e. 0420... oh maybe thats why they didnt haha

To be fair, in military speak that is what we use to date emails.

Except YYYYMMDD
 
it should be reflected in the system specs and purchase windows that this game does currently not support all versions of windows
not an acceptable state of affairs atm for players to have to rewind to previous versions imo
waiting to update my pc FD
(official secrets good factual film about a eng\american typo)
 
Last edited:
last big windows 10 update fubared my 7.1 surround setup which I resolved easily enough but as for windows keeping your current settings after updating is doo doo
 
Last edited:
I have my updates deferred in W10 - I keep changing the number of days so as to stop this 2004 compatability issue. It is about time they sorted this, it has been known for long enough but F D seem to just not give a monkey's.
 
last big windows 10 update fubared my 7.1 surround setup which I resolved easily enough but as for windows keeping your current settings after updating is doo doo
Sound problems are quite common, mine developed lets say "safe" hearing experience on headphones after version upgrade. Extremely low volume. Problem solved by removing and reinstalling sound drivers....
 
to be clear, I believe I have the windows 2004 update installed... it took a clean install to fix the issue.. so it must be in the update process? I didn't have to update to 2004 as the image used for the clean install was pulled from MS servers by windows... maybe I am mistaken, but I have not had any updates available since the clean install...

To be fair, in military speak that is what we use to date emails.

Except YYYYMMDD

I don't think thats only american... ISO date/time strings follow a similar format and those are based on an international standard... but even THAT would be an improvement as the resultant version would be 200004, which is ugly but makes some sense
 
Wanted to add to this as of the April 21 update I had the same issue arise. Rollong back Windows to the previous version fixed it. So I'm thinking the bug is back in the .Net update :(
 
Back
Top Bottom