Patch Notes Update Beta 2.01 available now

Neo-ST · Oct 1, 2014

Getting the black screen thing here too, as well as the huge log file growth. In less than 2 minutes of launching the game the network logfile was 601MB in size.

It starts off like this:

Code:

14-10-01-19:16 GMT Daylight Time  (18:16 GMT)
{19:16:55} Start Log for this machine: 192.168.1.1:59066 - dr01d
{19:17:12} ConnectToServerActivity: response
<?xml version="1.0" encoding="utf-8"?>
<data><servers><server><ip>35342e3231372e3137302e323436</ip><port>19364</port></server></servers><rescueservers/></data>

{19:17:12} New Primary Server: 54.217.170.246:19364
{19:17:13} Now using address 217.155.46.58:56807 for this machine after STUN reply
{19:17:13} 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.
{19:17:13} 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.
{19:17:13} 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.
{19:17:13} 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.
{19:17:13} Established MTU=1492
{19:17:22} EnterLocation: response
<?xml version="1.0" encoding="utf-8"?>
<data><servers><server><ip>35342e37332e3131322e313833</ip><port>19364</port></server></servers><rescueservers/></data>

{19:17:22} EnterLocation: Using UDP server address 54.73.112.183:19364 from webserver
{19:17:22} New Primary Server: 54.73.112.183:19364
{19:17:22} FailedToConnect: in ServerAdminRegister::CreateMissionAcceptRequest

Then the following is repeated many times a second:

Code:

{19:17:22} packed a parcel with zero letters!
<no log>
original m_schedulingValue=1.000000, requestSchedulingValue=0.000000 letterSchedulingValue=1.000000 resendUrgency=0.000000 to=54.73.112.183:19364 x 10 WIN-UJO7F3XL804
{19:17:22} packed a parcel with zero letters!
<no log>
original m_schedulingValue=1.000000, requestSchedulingValue=0.000000 letterSchedulingValue=1.000000 resendUrgency=0.000000 to=54.73.112.183:19364 x 10 WIN-UJO7F3XL804

By the time I killed the process there were almost 8.5 millions lines in the log file and it was up to 601MB in size.

Thankfully it compresses pretty well (310KB), so if you guys will find it in any way useful you can grab it here: https://dl.dropboxusercontent.com/u/3585260/netLog.1410011916.rar

I think it would be wiser to raise a ticket with this data.

scarysean · Oct 1, 2014

I cant get past the launcher it keeps asking me to uninstall lol looks like I wont be doing any combat practice tonight

Dinbar · Oct 1, 2014

Tutorials are now showing wrong version for me too. However they did let me play?

Grodit · Oct 1, 2014

I'm a sad panda. Getting the black screen on load as well

Sippi · Oct 1, 2014

I hope that they release another statement to explain what's going on because I'm freaking anxious to play this. Also, EVERYONE please wait until the next update before you start screwing with things like port forwarding and buying a new graphics card. The black screen and not being able to play is not graphics related so just chill fellas.

rootsrat · Oct 1, 2014

elewis said:
Update - the team is still plugging away. A new thread will be posted in just a moment detailing the next update. It's on its way! Should fix the majority of problems with B2.01.

You guys are absolutely amazing. Chapeau bas and big ups to the team, compliments to the pizza takeway

Thanks, Frontier!

Dialoco · Oct 1, 2014

Have been getting in ok since 2.01, but now getting client version too old.
Guess not long until 2.02?

Steve8066 · Oct 1, 2014

right ive had a bit of a play and.....initially my ED was installed on an external network drive. This worked fine prior to 2.0, but since 2.0 i just get a black screen direct from the launcher play button.

What i have just done is to completely uninstall ED from the drive, then reinstalled it onto the C drive via the store d/l button. Now i can get into the game and access the menu okay, although i do have the too old msg at the bottom. However, im further forward now than i was an hour ago.

So not sure if its a network drive issue, or if its the new d/l that has solved my initial problem.

Mucka · Oct 1, 2014

Tony H. said:
Hi Mucka, what's the path of those log files? Thanks.

In windows 7 they are here for me.
C:\Users\myname\Local Settings\Frontier_Developments\Products\FORC-FDEV-D-1002

Going to try and delete some latest ones again and see if I can get back in and grab a screeny for people to see who haven't got in yet while they wait for 2.02

Tamaya Ravenwood · Oct 1, 2014

You will make it - I'm with all of you at Frontier - my Heroes

Don't forget to eat and drink - I'm sure, you are very busy at the moment.

As far I could see - it's worth waiting for Beta2 - it looks real great

Lukozer · Oct 1, 2014

I was able to connect to the game... for precisely 17 seconds.

FredTA · Oct 1, 2014

When are we going to be hearing about 2.02 do you think?

macedk · Oct 1, 2014

in C:\Users\myname\AppData\Local I see two folders called "Frontier_Developments". contents are not the same ...an issue ?

FredTA · Oct 1, 2014

macedk said:
in C:\Users\myname\AppData\Local I see two folders called "Frontier_Developments". contents are not the same ...an issue ?

Frontier_Developments is the relevant one.

Henri · Oct 1, 2014

the issue there is that the uninstaller does not work

I was able to connect only to disconnect on warp

PIXEL · Oct 1, 2014

Not had this issue with large log fies.. the most recent one was less than a mb - tho there was one from a while back that was more but nothing wild like those reported.

I just deleted all but the most recent, verified files, checked that there wasn't a large file after verification and got on with the game - sadly only got a few tutorials done until game crashed in a FTL(faster than light) travel jump, same as yesterday after the Beta 2 launch - must be something odd as tutorials are offline arent they?

Graphics/detail are very bright, non atmospheric - played around with bloom with no effect.

Cant get on network as my something is tooo new

Happy to get on with life (feed cats, make dinner, watch a movie, sleep, wake up) till the devs work some issues out over a pizza or two - keep up the good work

S.H.A.D.O · Oct 1, 2014

FredTA said:
When are we going to be hearing about 2.02 do you think?

When they have done it, I'm sure they are busting a gut to get it out.

Whippet · Oct 1, 2014

Sigh ...

I'll try again tomorrow.
Hope you can get it fixed by then FD, thanks for trying.

uksub · Oct 1, 2014

Updated to 2.01 and telling me that my client is too old for the server????

Mucka · Oct 1, 2014

macedk said:
in C:\Users\myname\AppData\Local I see two folders called "Frontier_Developments". contents are not the same ...an issue ?

No there should be two folders, you want the second one for the log files.

Anyway the first time must have been a fluke because deleted them all and just got server unconnected message.
Tried checking game files and then was back to client too old.
Ahh well, it was 30 seconds of bliss.