Patch Notes Update Gamma 2.03 Changelog

Status
Thread Closed: Not open for further replies.
I'm unhappy to report that I still get "Failed to communicate with server" "Failed to perform mission transaction" when trying to hand-in a Mission. (Of course reported on my ticket, but FD don't seem to bother reading tickets unless it's something which prevents you from playing the game, like a Crash.)

P.S. And I can't screenshot the problem, as the screenshot key (F10) stopped working with Gamma 2.x.

I believe they made reference to this in the changelog? More debugging info :)

"Added some logging for accepting missions failing and updating missions failing"
 
I'm unhappy to report that I still get "Failed to communicate with server" "Failed to perform mission transaction" when trying to hand-in a Mission. (Of course reported on my ticket, but FD don't seem to bother reading tickets unless it's something which prevents you from playing the game, like a Crash.)

P.S. And I can't screenshot the problem, as the screenshot key (F10) stopped working with Gamma 2.x.

It's one that they are well aware of since Ashley posted about it asking for more details. Since FD are working all weekend I would imagine further patches before Monday once they get to the root cause.

G
 
(Of course reported on my ticket, but FD don't seem to bother reading tickets unless it's something which prevents you from playing the game, like a Crash.)

Seems a bit harsh! Just because they don't send you a bunch of flowers to thank you does not mean they are ignoring your ticket. Pretty sure they are aware of this one

From the change Log

"Added some logging for accepting missions failing and updating missions failing"

FYi I have the same problem (not checked in 2.03 as I am at work tho)
 
seperate 'UI Back' into its own bindable input (Note this might affect players with custom bindings!)

I can't select the UI, it still shows as bound to shift for me, I am using custom controls
 
Don't be petty, there are many tickets being submitted. Crashes are A class issues that receive priority in any testing environment. They'll get to it, be patient.
I'm not being petty, I'm just commenting on the situation. (It's perfectly true that FD are ignoring many tickets for months. Even when my latest comment was that the issue was fixed, so that the ticket can be closed, the tickets are still open months later. Proof if any were needed that FD aren't reading some kinds of tickets.)

The result of them ignoring tickets is that I (and many others) don't bother to ticket many things any more (unless it's really major). I assume that FD are happy with this (since they are too busy to handle all the tickets anyway).
 
Last edited:
Still having issues with the UI. Since 2.02 the camera no longer automatically moves to look at the panel you have open, which is really annoying :/
 
Great work guys, everything seems to be working great, no longer having issues playing which is a major win! Thanks for all your efforts and have a good weekend.
 
One thing not on the Change log, there is now a FSD cool down graphic in the bottom right. Nice little extra.

However I can't access any of the panels. My joystick buttons and 1 2 3 4 don't do anything. I've tried changing to the stock Keyboard/Mouse set and that doesn't work either. I can access and navigate the panels if I switch to mouse look, but that's a PITA. Anyone got any idea how to fix that?
 
Ok on W&T repair screen. All modules at 100% and still showing credits to pay but, can't. Not complaining, I don't have to make repairs like this. New thing after patch is. The paint job, will highlight to fix and I change it to any percent I want but won't stay that way.
 
"Allow exploration data worth 0 credits to be sold"

Why not just make the minimum value 1?
I mean come on, it is pointless to even have data for 0 credits. At least Selling for 1 credit is "something".
But if its gonna be at 0 you might as well just auto-delete the data from the players account, saving them the hassle.

check facts before posting.
the exploration data valued at 0 credits is actually previously sold data that had somehow managed to get back into our lists for data to be sold (probably caused by the fix for being unable to sell data/cartographics crash), but as it had previously been sold it was now worth 0. this is the fix for that.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom