Patch Notes Update Beta 2.01 available now

Status
Thread Closed: Not open for further replies.
might be of help to you..
One such failed start attempt. showed the red glowing rotating cobra for 3 sec and then black screen with music:

Code:
{18:22:15} New Primary Server: 54.73.141.153:19364
{18:22:16} Now using address xxx.xxx.xxx.xxx:61860 for this machine after STUN reply
{18:22:16} The message was too large for the specified buffer and (for unreliable protocols only) any trailing portion of the message that did not fit into the buffer has been discarded.
{18:22:16} The message was too large for the specified buffer and (for unreliable protocols only) any trailing portion of the message that did not fit into the buffer has been discarded.
{18:22:17} The message was too large for the specified buffer and (for unreliable protocols only) any trailing portion of the message that did not fit into the buffer has been discarded.
{18:22:17} The message was too large for the specified buffer and (for unreliable protocols only) any trailing portion of the message that did not fit into the buffer has been discarded.
{18:22:17} Established MTU=1492
{18:22:35} EnterLocation: response
<?xml version="1.0" encoding="utf-8"?>
<data><servers><server><ip>35342e3231362e32322e3930</ip><port>19364</port></server></servers><rescueservers/></data>

{18:22:35} EnterLocation: Using UDP server address 54.216.22.90:19364 from webserver
{18:22:35} New Primary Server: 54.216.22.90:19364
{18:22:35} FailedToConnect: in ServerAdminRegister::CreateMissionAcceptRequest
{18:22:35} packed a parcel with zero letters!
<no log>
original m_schedulingValue=1.000000, requestSchedulingValue=0.000000 letterSchedulingValue=1.000000 resendUrgency=0.000000 to=54.216.22.90:19364 x 10 WIN-UJO7F3XL804
{18:22:35} packed a parcel with zero letters!
<no log>
original m_schedulingValue=1.000000, requestSchedulingValue=0.000000 letterSchedulingValue=1.000000 resendUrgency=0.000000 to=54.216.22.90:19364 x 10 WIN-UJO7F3XL804
{18:22:35} packed a parcel with zero letters!
<no log>

it repeats the last 3 lines of the log forever. The file was 2 GByte after 1 minute or 2.

(thanks to the one for pointing out the observation of the extremly large growing logfiles)

(and no sorry dont liek your support ticket system.. pls create a proper beta report system)
 
They've broke the Beta WAAAAHHHHHH! I want to play!

anyone know whats happening?
It's probably simply that something went wrong on their servers, presumably in deploying the update to all of them. The patch itself, for the short amount of time I was playing it, seemed to be perfectly fine.
Perhaps they're messing about with hotfixes that have yet to find their way to us.
Perhaps space unicorns are chewing through their network cables and farting glitter into the hard drives.
 
Occasionally I get in and try to dock with a station, I get a tantalising brilliant blue notification that I discovered a new stellar phenomenon which I visited earlier and then I try to drop off at the station and I get the little grey box telling me little grey things about servers and kicking me out.
 
Beta 2.00 loaded up fine earlier and there I was docked on the platform as I had left it. Didn't have time to test but I got in.
Installed 2.01 and it said couldn't connect to server as my client or something was too NEW.
Kept trying for about 30 mins and it then said couldn't connect as my client/game was too OLD and to upgrade? :rolleyes:
Finally got connected to a server and tried to load in and the game just freezes until I ctrl alt del and end task.
 
Error Message: Can't connect to edserver: Client is too old.

Happens with the latest version 0.3.1395.0.

Tried downloading again and re-installing, but still the same.

Tried validating from installer options, but still the same.

START option in main menu in RED, with the following servers giving [unconnected] message:

Ditto.

Can't even get connected to beta test. FD screwed something up bad.
 
I don't think so, otherwise the message would read "Your client is too new"

Yeh I don't know, looks like we will be getting another big update, or they will be fixing server side problems, I'm guessing they tested it out though so maybe the update had some corrupt data or code errors, your guess is as good as mine.
 
mouse controls

What have you done to the mouse controls???....bring back the control i had before the patch, game is almost un-playable with the new controls.( I don't have a joystick just yet).
Even adjusting the controls in the options doesn't do any good, the ship wallows like a pig in mud...cant do the tutorials with controls like that.....
and i'm saying ,,please.
 
Nope, file validation doesn't work for me.
Sometimes im able to load game and fly/play for few minutes, then im getting server error. Up until 30 min ago i was able to flawlessly play in single system (Aselius Prime).

Schrödinger's client

Im dead :D
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom