Patch Notes Update Update 2.3.01

Status
Thread Closed: Not open for further replies.
I docked at Alcazars Hope before patch landed. After patch 2.3.01 was installed I tried to log into open but game crashed every time.

Not going to help you much, but
- playing on PC
- using the direct launcher
- dl'ed the patch, fired up ED, went into a private group, no problems. Currently waiting for my Dolphin to be transferred to where I'm sitting at.

Did this guy say whether or not he was on Steam?

This could be a Local File Validation issue.

This can happen if the update was downloaded from the stand alone ED launcher instead of from the Steam Client.

To check... Go into Steam Client... Right Click on Elite Dangerous game and choose Validate Local Files. This will go out and scan your ED directories and make sure that everything is synced and identical to what Steam expects the game folders to contain. Any issues will be fixed and file questions repaired by Steam downloading a fresh copy of whatever it doesn't like back down to your local ED folder.
 
ok still no charging sound with disco just the beeps and boing, and now the FSD is just a red circular blur and i cant see the numbers. i have bloom and blur off in graphics options so the effect is applied directly and separately to the numbers for no reason. im downloading latest nvidia driver but im 100% sure it wont make any difference to the fsd countdown number blurring. i dont see the point of blurring them all the time - if they are changing too fast to read (supposedly in game world) then they would not be visible since its no use. so im thinking this is a bug.

to clarify : the fsd numbers EACH have a red blur and bloom, type effect around them preventing them being legible on my laptop screen. if this is deliberate effect for some reason then please can i have either an alternate large CLEAR unblurred single number instead of 00x.xxx (dont understand why it needs ANY decimal places) in options instead or an option to turn off the visible countdown (my least preferred option)
 
Last edited:
A massive thanks to Everyone at Fdev, just logged in, did a few jumps, Stars look good, galmap is usable... FPS is good again

I'm a happy chappie

:)
 
iwish the disco sound was fixed. thats one of two things killing my desire to play now. this is the other one the random blurring of the fsd countdown numbers regardless of graphics settings. the numbers visible in the screenshot are not clear long enough for my naked eye to register them - to me they all look like the blurred red circle ones.
f96477a98c.jpg
 

Brett C

Frontier
iwish the disco sound was fixed. thats one of two things killing my desire to play now. this is the other one the random blurring of the fsd countdown numbers regardless of graphics settings. the numbers visible in the screenshot are not clear long enough for my naked eye to register them - to me they all look like the blurred red circle ones.

Hrm, looks like there's a fair amount of a blur effect going on. Might be worth while reporting that as a bug.
 
Thanks to the Dev team for all their hard work and addressing all these issues.

Not entirely sure what "farming salt from the community" means exactly..............
 
Hello cmdrs,
After 2.3.01 landed I have a problem to log into open or private. Game just crash every time :(. Only solo mode works. Anybody else have the same problem?

Same problem here !
Tried many time in open, got game crashes every time exept once... and it crashed few seconds later.
Seems to work in solo or private mode.
 
So that's why they released a buggy as fudge 2.3, someone wanted some salt, thing is if the job was done properly in the first place there wouldn't have been an out pouring of salt, but hey here's a little more from me to top things off.

I guess I should be thankful at least their trying to fix what they broke.
 
And in the mean time, FD breaks their own rules about releasing patches on all platforms at the same time with blatant disregard for the xbox players that can't get in on this event because of FD breaking the game.

So you're either saying that Frontier should have delayed the PC fixes and put them on the shelf until the Xbox equivalent fixes were done also or you're saying that the XBox fixes could have been fixed and released today also (which I presume you know as a fact).

Which is it ? Seems to me that the XBox soft lock can't be fixed by today but they are working on it, so no 'disregard' there.
If Frontier hadn't released the PC stuff (or delayed it's release for no good reason) then even less people would be taking part in the 29th event.
The bugs happened, it was unfortunate, but regardless of that and despite the issue for the XBox owners, it was not Frontier who decided to continue with the event as planned on the 29th. That could have been postponed given the circumstances so you cannot apportion 100% of the blame to anyone for that situation.

Also as regards the 'two weeks' timeline that I mentioned, where you replied that Frontier said 'early May' (essentially the same now), I draw your attention to this from Frontier (4 days ago)...
"There are some separate issues that apply to Xbox Commanders only. We will put this update out as soon as we can too - we understand the frustration caused but rest assured that the developers are working extremely hard to bring these fixes in as soon as possible. We’ll keep you informed on an exact ETA as soon as we know more, but for the moment it looks like it will be a couple of weeks"
 
Last edited:

Tiny_Rick

Banned
Dear FDev,

Please make next week's CG a mining one, where we have to deliver tonnes and tonnes of sodium chloride. If you do, I will personally send cookies, or biscuits, or whatever the hell you blokes nosh on.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom