Patch Notes Update Beta 2.02 incoming

Status
Thread Closed: Not open for further replies.
ops..

Started Beta 2.02 and had it waiting in the connecting screen.
Was busy with something else for 15min and it never connected (start stayed red)

when i returned the game exit didn't work so i had to kill the task

checked the netLog.log
and it logged a 17 GByte file in this 15min !!!!!
 
Will give up tonight, keep losing connection. Maybe an offline mode would be a good update? It depends on server connection so please give us an offline option!:D
 
Maybe the devs and community team should consider this part of the testing of what happens when the community they depend on get a really bad patch.

Because thats what this is. Its a gigantic mistake. It might be a honest mistake, but its sort of mindnumbing to think how this could get out to a live build with bugs like this. Doing some quick math the next major patch will be Gamma. The data that will live as long as the game does will be generated in that. This was not a patch that give much confidence in FD ability to pull this off and keep the game stable after Gamma.

I think I read somewhere a dev saying that they wouldn't rule out a short preview test for the Alpha backer group on some builds, which is presumably a smaller number of people than the full Beta player base now.

From the looks of this release, they could use a stress test somewhere in-between their private development network and the full player base. Things like this staggeringly large log file being written shouldn't slip into the outside world. That's going to cause problems for people, over and above just wanting to beta test and/or play a game.
 
flamr

What is it with the !!SERVER'S!! you get on after four or five goes (solo only cannot get into open) then have five mins of play then !!BAAM!! disconnected again. Was hoping 2.02 would give me more on time but same old problem, I know they have a hard job getting beta 2 ready but would like to get on to find out all the new things....

Just another flamer who doesn't know, what he is talking about xD

This is a real beta, not a "we release an unfinished game and call it beta". Things don't work on patch days. Thats normal. Grab your school books and relax.
 
I get disconnected from server a few minutes after starting open play. I'm not sure if it's related to server load or bugs.

The one good thing I found is that creating a private group with just myself works. Played about 1/2 hour with no problems. That will have to do until the problems are sorted out.

And I have to say....What an amazing game! :)
 
Well the guys must have been working late to get some of these bugs out.
I've now managed to get into the game but I entered Supercruise and got a crash to desktop. Bug report sent.
 
worse than previous two iterations for me. Now it cannot connect at all, and the opening menu soft-locks and needs ctl-alt-del kill. Watch out for your logfile dir, folks - because it spams 300mb of
original m_schedulingValue=1.000000, requestSchedulingValue=0.000000 letterSchedulingValue=1.000000 resendUrgency=0.000000 to=54.74.15.224:19364 x 10 WIN-UJO7F3XL804
{14:54:34} packed a parcel with zero letters!
<no log>
into the net log in under a minute.
 
That's what a beta is for. Making these mistakes allowes the developers together with the community to not make these mistakes again and learn from it before the full game is released.

They pushed too much in and did not check the patches after 2.0 .
That is not what I call a beta but really a noobish mistake.
2.0 was more or less stable, patching a broken patch is simply patchwork and the more they patch the more a bug gets sunken into the code.
A lot of things in beta can go wrong, but anything that requires way too many overhours means that some bugs will sink in...the devs should call it a day and get some sleep (and maybe rather retrace what went wrong after 2.0 )
 
{22:25:30} System:6(Styx) Body:6 Pos:(-34.9891,-91.3782,995.201)
{22:25:30} System:6(Styx) Body:6 Pos:(-34.9891,-91.3782,995.201)
{22:25:42} ModularStationAttachComponent: object kinematic Alli_StoragePodA_0x0000000100000016 is not ready
{22:25:42} ModularStationAttachComponent: object kinematic Alli_StoragePodA_0x0000000100000017 is not ready
 
Well mine just loads to the menu screen, shows the menu text and the server ip at the bottom with [unconnected] beside it.
I can move the mouse cursor about the screen but menu items are not selectable. Have to end task to quit it.
 
Well I was able to play for about 20 mins before getting disconnected again... and now once again cannot connect at all. Also, playing at 2560x1440, there are many areas where the graphics are APPALLING! My patience is running out... Beta 2 was stupidly late and the atrocious state it was (and continues to be) in means it has been nothing short of an unmitigated disaster. Requiring 2 updates in less than 24 hours after finally being unleashed upon the unsuspecting testers and still both broken and inferior to Beta 1.06 in almost every way. I used to detest people who endlessly bashed the devs and the game... After today i'm starting to see exactly why they do.

You would be the David Niven of the ED forums that put up that elegant and witty clip on YT ? If so I would like to personally thank you for your fine efforts, and your style.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom