Patch Notes Update Beta 2.02 incoming

Status
Thread Closed: Not open for further replies.
I actually managed to get a log file small enough to open by starting the client then killing it with task manager immediatelty.

It just keeps repeating this message block over and over:

{22:15:56} packed a parcel with zero letters!
<no log>
original m_schedulingValue=1.000000, requestSchedulingValue=0.000000 letterSchedulingValue=1.000000 resendUrgency=0.000000 to=54.195.170.117:19364 x 9 WIN-UJO7F3XL804

Don't know if FD development are scanning this thread but I hope the above helps. Stay with it guys - been there myself many a time.
 
I haven't been able to get on since the first 2.0 patch....still the same with 2.02. Just hangs on the load screen for 30 mins then says it cannot connect. A little gutted now to be honest :(
 
Log possibly interesting not sure...

So I don't get past the menu screen, it just dies and in 20 seconds have produced 2gb of net log with

{22:15:39} packed a parcel with zero letters!
<no log>
original m_schedulingValue=1.000000, requestSchedulingValue=0.000000 letterSchedulingValue=1.000000 resendUrgency=0.000000 to=54.78.160.13:19364 x 9 WIN-UJO7F3XL804
{22:15:39} packed a parcel with zero letters!
<no log>
original m_schedulingValue=1.000000, requestSchedulingValue=0.000000 letterSchedulingValue=1.000000 resendUrgency=0.000000 to=54.78.160.13:19364 x 9 WIN-UJO7F3XL804

Over and over, not sure if this is useful for anyone. P.s I love Elite (DB)!

Arbor
 
Things seem to be calming down a lot with servers now, was just able to play for over an hour without getting disconnected!!BUT then I was disconnected again! MUCH BETTER though now!! FUN!! Keeping fingers crossed good work ladies & gentleman!
 
Okay so maybe you all will hate me then because I've tested this and been able to jump to various systems without crashing. I am playing on Solo Mode though haven't tried Open Online. Also noticed that my FPS rate seems more stable than it did in 1.06 so a definite improvement!
 
The same.... :(

The same, sadly. Log files bloating whilst menu frozen, exactly as others above have described.

Worse than 2.01 for me, that at least let me make it as far as playing the tutorials before the main menu froze.

Now it is as soon as the game load, as others have observed the server in bottom left says unconnected
 
hmm

planets and moons are looking good I cant wait to be able to touch down on one of them - so cool.

the ai pilots seem to veer off now from head on colliisions
 
Sidewinder spinning, spinning, and spinning again ^^ !

{23:33:09} ConnectToServerActivity: response
<?xml version="1.0" encoding="utf-8"?>
<data><servers><server><ip>35342e37382e3136352e3434</ip><port>19364</port></server></servers><rescueservers/></data>

{23:33:09} New Primary Server: 54.78.165.44:19364
{23:33:09} Now using address 109.26.42.225:56035 for this machine after STUN reply
{23:33:09} Established MTU=1500
{23:33:46} Connection from 79.125.72.13:14554 -- now attached to machine 88.171.220.189:30739
{23:33:46} EnterLocation: response
<?xml version="1.0" encoding="utf-8"?>
<data><servers><server><ip>35342e37382e3136352e3434</ip><port>19364</port></server></servers><rescueservers/></data>

{23:33:46} EnterLocation: Using UDP server address 54.78.165.44:19364 from webserver
{23:33:46} System:21(Aulin) Body:4 Pos:(-65.7747,-10.2917,-2999.26)
{23:33:46} System:21(Aulin) Body:4 Pos:(-65.7747,-10.2917,-2999.26)
{23:33:55} ModularStationAttachComponent: object kinematic Alli_ONeillHabitatRing_0x0000000100000018 is not ready
{23:33:55} ModularStationAttachComponent: object kinematic Alli_ONeillHabitatRing_0x0000000100000018 is not ready
{23:33:55} ModularStationAttachComponent: object kinematic Alli_ONeillHabitatRing_0x0000000100000018 is not ready
{23:34:14} FailToJoinSession1: 0x000000024bd09371: at 30.0s : 81.83.165.31:36809 x 2 Name Unknown
{23:34:14} FailToJoinSession1: 0x000000024bd09371: at 30.0s : 82.32.161.39:51177 x 3 # Name Unknown
{23:34:14} FailToJoinSession1: 0x000000024bd09371: at 30.0s : 88.122.88.42:61946 x 5 # Name Unknown
{23:34:14} FailToJoinSession1: 0x000000024bd10a03: at 30.0s : 88.122.88.42:61946 x 3 # Name Unknown
 
Last edited:
Launcher starts - frozen client. Unconnected, ah well, first day of a Beta patch.

I remember Everquest being down for 5 days :).

Time for bed and have another go tomorrow.
 
Beta 2.02 is incredibly nice ! Sadly, I can't quit Azeban Orbital : game crash when entering supercruise... and disconnect me from server when entering hypercruise :) (I tried about eight times)

Will have to wait 2.03 (or .04... ?) to begin playing.

Ticket submitted. Keep up the good work devs, I know you are busy at the moment with all those bugs ! ^^
 
OK heres verdict on Beta 2.02

Crossfire doesnt work. Other than that no issues :\ sorry for those who cant get it working. Works a treat on mine apart from crossfire :D oh and dam controls reset YET again ( you gotta stop doing that! ) :mad:

One minor glitch i noticed, if you select any other monitor from its default then it loads on the default and then moves to the selected one. Abit annoying :\
 
Just got home, updated to 2.02, and sorry, but it's worse than ever. Still got the 10-15 second black screen pause before the first Elite logo appears, then when the menu appears it hangs. I can't even play the tutorials now.

Log file very quickly fills up with thousands of lines exactly like this:

Code:
original m_schedulingValue=1.000000, requestSchedulingValue=0.000000 letterSchedulingValue=1.000000 resendUrgency=0.000000 to=54.74.29.156:19364 x 9 WIN-UJO7F3XL804
{22:25:10} packed a parcel with zero letters!
<no log>
 
No but you can put in tickets for those problems with logs and thus HELPING with the "BETA testing".

You missed the whole point I was making in the first place. Which is it is BETA, its not going to work for everyone right off the bat (and there was some major game breaking bugs as of Beta 2's first release yesterday).

But raging about it and losing "patience" and saying "So DONE with this game" etc etc etc isnt really constructive to BETA testing now is it?

If you cant deal with things breaking when there is a major release change and not helping FD to fault find with full tickets/logs/etc then you failed to understand what BETA testing is..

plain and simple.

Personally I didn't see many people raging(definitely a small minority) and coming on with a holier than thou attitude while smugly proclaiming you aren't suffering the same issues is nothing short of baiting and helps nobody.

The devs are well aware of the issues and the people locked out of the menu are aware this is Beta and they are working hard.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom