Patch Notes Update Update 3.3.03

Winterwalker

Winterwalker
Juniper said:
If it was (b), they've had almost 24 hours to release the "tested" version. :rolleyes:
Click to expand...

Nah. I've also seen it said in forums the blue alert is coming up but the discovery is not happening in left panel (so it alerts you again as undiscovered). Planet discovery links to the server - otherwise client-side accounts would hackable to discover *.* right? But networking is THE ONE thing FD can't test in house.
 

CMDR MAIN SEQUENCE

CMDR MAIN SEQUENCE
Winterwalker said:
But networking is THE ONE thing FD can't test in house.
Click to expand...

Why ever not? It might be true for P2P stuff (because Internet) but it's not the case for regular client/server stuff. They can replicate a player at home by having PCs with a dedicated broadband connection and they can replicate the live servers by having an exact replica for test purposes in the AWS data centre in Dublin.

Abnaxos said:
On a more general note, I'd love to see that "discovered XY" message completely gone (banished to the ticker in the top-right). As a full time explorer, I can safely say that when I'm not constantly seeing this message, I'm not playing the game. It's mostly useless and far too prominent. To me, it feels like "good dog", "good dog", "good dog", "good dog". Very annoying, even without the bug. In addition, in FSS, it unnecessarily hides actually relevant information: the planet's name and type.
Click to expand...

100% agreed. And do the messages still conflict with the fuel-scooping banner?
 

Winterwalker

Winterwalker
CMDR MAIN SEQUENCE said:
Why ever not?
Click to expand...

Not saying I know exactly why the bug occurred only that there are explanations other than, 'didn't test before release'. You could have a perfect build then a packet gets lost in upload, in transit to Dublin and now you don't have a perfect build any more is all I'm saying.

CMDR MAIN SEQUENCE said:
100% agreed. And do the messages still conflict with the fuel-scooping banner?
Click to expand...

I'm also not keen on seeing the blue alerts too often. I don't find them too bad in 3.3 myself but they are I agree on the edge of becoming too much and little wonder this bug tipped them over.
 
Last edited:

Ozric

Volunteer Moderator
Ozric
QA have announced that they have fixed the issue for Asteroid Clusters.

QA-Jack said:
Hey Cmdrs,

We have just applied a server-side fix for this (asteroids only) - It is currently propagating across the servers so you should receive this very shortly, if not already!

You will be required to restart your launcher for this to take full effect.

Stay safe out there Cmdrs!
o7
Click to expand...
 

Abnaxos

Abnaxos
Juniper said:
If it was (b), they've had almost 24 hours to release the "tested" version. :rolleyes:
Click to expand...

This is IT. IT from the maker's side is often not as simple as it looks from the user's side. I, personally, would first want to investigate what exactly went wrong and why, before trying to fix it overnight (possibly making things even worse).

Also, for consoles, there's a review process, so it's not possible to quickly upload a patch overnight. Sony/Microsoft first want to review the patch, that takes time. And you should make sure you get it right this time, before submitting the patch. OK, for PC it may theoretically be possible to do it more quickly, but that in turn would break processes that are in place to make sure things like that don't happen.

Trying to fix it helter-skelter would be a bad idea.
 

schmicknick

schmicknick
ruger_shooter said:
I have done so. The problem has NOT been fixed.
Click to expand...

Last I had tested on it...
If you just have the text box active and type it will work.. tying directly into the text box.
If you select the text box, then the virtual keyboard pops up.
Also still now though, if you select a particular Cmdr. and select direct message... you are still faced with the virtual keyboard.
The shortcuts /r, /l, /w, etc... still work, but the squadron chat was disabled last I knew...

So I think that's the current state of affairs... and it is better than having the virtual keyboard pop up with every text entry.
o7
 

fallout2077

F
Ahh, okay then, I kinda had a feeling when it was mentioned that a launcher restart was required. Okay then, thanks for clearing that up for me!
 

ALEX CAOS

ALEX CAOS
- squadron chat not existing great feature

- loosing full keyboard control not fixed

- secenario mission false faction and can´t target enemys

- installations flying away (exiting since impelented)

-numeros cz bugs (existin over 1 year)

all well known since minimum 1 month others more than far

you dont like to fix we dont like to play soon, didnt by something from store since months cause no effort in develop or bug fix
 
Last edited:

ossus74

O
And whats about the bugs after the update? Landing on any station not possible. Since chapter 4 the game is not functional.
 
You must log in or register to reply here.
Back
Top Bottom