Patch Notes Update Beta 2.02 incoming

Status
Thread Closed: Not open for further replies.

Titus Balls

Titus Balls
2.02 in terms of connecting to the servers (UK) are much worse for me.

If I do get in, I get disconnected pretty quickly. Otherwise I don't get in at all when I do try after a crash and I just get a big red Start button (even though it doesn't say unconnected to the server)
 

billeman

billeman
Ok, I'm calling it quits for today, a few minutes or seconds and then disconnect.

This morning I was able to play for quite some time on 2.00.

My sympathy for the devs, I know about these kind of situations even though my experience is not in development. Good luck guys, make sure to get some sleep, after x hours searching the brains don't work anymore, it's better to get some rest, next morning usually the solution pops in fast.

Cheers
 

Gommster

G
WoenK said:
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 )
Click to expand...

This is what expanded community testing is for - there will be a lot of things that work with a small group of testers but not with thousands, it's exactly why they need us for a beta.

We just need to remember, this is pre-production software, it takes time to get it right, from time to time it will go wrong and we need to be patient when that happens.

If you can't be patient or put up with things breaking, you are probably not the right sort of person to be in a beta programme

Personally, I've been waiting for this game for 30 years, I can wait a little longer for it to be finished in the right way. These guys have my full support as they've already proved they are good enough to both fix any hiccups and make this something truly wonderful.
 
Last edited:

Aqualarius

Aqualarius
At the risk if ing everyone off...am I the only person who has been able to get into the game with no problems? The stars are there and there's no crashing. Looking good FD! :cool:
 

pookeyhead

pookeyhead
Peeps at FD....

Get some sleep!!!

I want to play so bad it hurts, but please... it will still be there in the morning :)

As for all the flamers, calling it a disaster, and accusing FD of "noobish mistakes" is just making you look like whiners.

They'll sort it. Obviously they'll sort it... no one seems to be able to test their beta.. don't you think it's mission critical for them? Going into nerd rage will help no one.. not even yourself.

Me? I remain sanguine.. I'm going to pour a single malt, and then go to bed with a Peter F Hamilton novel. Can I advise that you do something similar?
 
Last edited by a moderator:

Kerrash

Kerrash
Finally had chance to play a little.
All seems okay so far, a couple of disconnects; but overall working well.

Thanks for working so hard to get this out FD ;)
 

fishermanpaul

F
2.01 had the freezing after selecting Start (when that was possible - most recently got "your client is too old/new"

2.02 Freeze on menu - can't select anything
 

Korben Dallas

Korben Dallas
Hm,

These guys are working late hours to provide us with continuing enjoyment, so kudos to that. Don't forget that these people also have families that are waiting for them to come home.

It's a beta after all.

Cannot connect to server (red menu option) or disconnects, but cannot seem to find the huge logfiles that everyone seems to talk about neither.

Singleplayer works fine. Only crashed once. Log was sent.

I looked in

C:\Users\[Username]\AppData\Local\Frontier_Developments\Products\FORC-FDEV-D-1002\Logs

there is no folder with this name, only this one:

EDLaunch.exe_Url_uulw3mf3cv1l5yuggwup0k0dv1zkpct2

opening that folder goes toe a user config file.

any ideas, does anyone have the same issue, since I would like to check on the size of the logfile.

PS at least now everyone can practice the blockade running techniques for smuggling goods into a station without losing the ship.
The only thing that would be cool to add would be to have a sort of "skirmish area" around the starport in the take off or cruise training missions, and a choice of weapons.

Good work ED,

Keep it up.
 

Tanith Low

Tanith Low
Lukozer said:
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.
Click to expand...

Wow, I just have no idea where to start with you.

The current build has 4.5 million lines of code in it. Why don't you sit down and try and find the errors in all of that. At the very least it should keep you quiet! :p
 

Benghlo

B
2.02 works better for me, at least I managed to do a mission this time around, but got a massive crash after that. DebugLog still empty, should I start ED with -debug or something to activate it? I want to be able to give as much info as possible.

Still have unconnected servers and disconnects though, and my net log is usually tiny (1-4kB)
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom