Patch Notes Update Server Side Update 04/11/2014

Status
Thread Closed: Not open for further replies.

J. Calvert (Joshua)

J. Calvert (Joshua)
Made a few test runs and for me, playing Solo, it has improved. Even flying to Chu Hub went a lot smoother, almost no stutter. Don't know if it's caused by the server update or the new Nvidia driver (344.60) for my GTX770 I installed just before I started ED.
 

mono

mono
Will check later after work. Planets like the one at Chu Hub (Styx) would cause stutters for me, along with the frameshift jump stutter of a couple of seconds. The spinning ship when you launch into the game was also quite stuttery for me.

This is on an overlocked (4.3ghz) i5, 780Ti, separate SSDs for game and OS, 16Gb ram.
 

trader4u

T
server connection problems

Thomas Jefferson Jones said:
This sounds correct, likely the 'unable to connect to server' dumps to the menu have been addressed.
Click to expand...

no, not for me unfortunally, i havent been able to start any game since last update(s) 3.02, 3.03 "openplay" or "solo"
had no such problems before update 3.xx
i'm on wired connection(s) only... with no packet loss(in cmd line, ping i checked), or windows firewall issue, avast swithed to 'game mode'
and yes, its all been ticketed, b.t.w.

pc:4Gb ram, msi R7970 lightning BE, ocz vertex 2 ssd´s in raid0 mode
and i sometimes play on my laptop as well, wich has the same connection issues.

its probably a well documented problem, but i wanted to let it be known anyway.
 

Vestinious

Vestinious
Ive been mining in Styx system in Open play for a bout 30 mins now and must say everything is much better :)
I did get a bit of stuttering on approach to planets but it went very quickly and launch and missions all good now.
 

frogfoot

F
Seems a little smoother here, with no disconnects so far, and missions are playable now, (no failed missions and locked cargo so far)
 

Sniger

S
if anything, it is now worse for me: if only I could escape with a simple CTD or hangup, but no - my PC crashes completely and then does a full reset(no bsod). (note: this issue is ONLY present when running ED)
This afternoon I have had 3 crashes, 4 hangs (spinning ship loadscreen, exit from FSD near station in Ross 490, market screen) all in under 1 hour.
The problem started during the update frenzy in the start of B3 then seemed to cool off a bit with 3.03 , but since yesterday the problem has now become so severe that I am forced to put ED on ice pending further updates and/or response to my ticket.
 

stimutacs

S
Still (identically to 3.01 and 3.02) throws me off almost immediately (within one second) of connecting and getting into the 3d game world with

14-11-05-03:14 E. Australia Standard Time (17:14 GMT) - part 1
{03:14:19} Start Log for this machine: 192.168.1.2:62635 - xxxxxxxx
{03:14:36} ConnectToServerActivity: response
<?xml version="1.0" encoding="utf-8"?>
<data><servers><server><ip>35342e37342e37372e313434</ip><port>19364</port></server></servers><rescueservers><server><ip>35342e37382e3134352e313532</ip><port>19364</port></server></rescueservers></data>
{03:14:36} New Primary Server: 54.74.77.144:19364
{03:14:36} New Rescue Server: 54.78.145.152:19364
{03:14:37} Now using address 59.167.220.205:62635 for this machine after STUN reply
{03:14:39} Established MTU=1484
{03:14:45} EnterLocation: response
<?xml version="1.0" encoding="utf-8"?>
<data><servers><server><ip>35342e37382e3134352e313532</ip><port>19364</port></server></servers><rescueservers></rescueservers></data>
{03:14:45} EnterLocation: Using UDP server address 54.78.145.152:19364 from webserver
{03:14:45} New Primary Server: 54.78.145.152:19364
{03:14:45} System:33(Asellus Primus) Body:1 Pos:(-1.18349e+009,-1.12277e+009,-1.19961e+009)
{03:14:46} System:33(Asellus Primus) Body:1 Pos:(-1.18349e+009,-1.12277e+009,-1.19961e+009)
{03:14:54} System:33(Asellus Primus) Body:1 Pos:(-1.18349e+009,-1.12277e+009,-1.19961e+009)
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Someone requested a crash: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:55} Disconnect: MissionUpdateFail
{03:14:56} NeedToSendAck for 54.78.145.152:19364 x 14 r48101 WIN-UJO7F3XL8 increased to 1.00
Click to expand...

in netlog.log as reported in TICKET [ ID: 38005] a week ago.
 
Last edited:

iospace

I
This update was clearly stated to be /server side/. I have seen no indication that the stuttering is a server side problem, so why are people asking if that's fixed/complaining that it's not?
 
Last edited:

Trader Pat

Trader Pat
iospace said:
This update was clearly stated to be /server side/. I have seen no indication that the stuttering is a server side problem, so why are people asking if that's fixed/complaining that it's not?
Click to expand...

Agreed. Go figure...

Besides, lots of empty BBs still. As per FDev support on a ticket of mine, it is a server-side issue. I guess this particular fix is still WIP.
 

Mu77ley

Volunteer Moderator
Mu77ley
stimutacs said:
Still (identically to 3.01 and 3.02) throws me off almost immediately (within one second) of connecting and getting into the 3d game world with



in netlog.log as reported in TICKET [ ID: 38005] a week ago.
Click to expand...

I'm getting exactly the same issue and also have a ticket raised. They are looking into it as I had ticket updates over the weekend.

Can I ask whether you had any missions on the go? Seems to always be the case with me.
 

stimutacs

S
Mu77ley said:
I'm getting exactly the same issue and also have a ticket raised. They are looking into it as I had ticket updates over the weekend.

Can I ask whether you had any missions on the go? Seems to always be the case with me.
Click to expand...

Yep - starting at beta3.0 - no problems playing for hours. Until -

* took a hunt warzone ships mission,

* arrived at low intensity conflict zone,

* couldn't pick a faction from the right panel (old beta 2 bug still there),

* disconnected and relogged in to the game,

* was able to pick a faction,

* fought in the low intensity conflict zone,

* tried to supercruise out, dropped connection

* continue to try and supercruise around, keeps dropping connection either on entering or exiting hyperspace/sc

* eventually relogged in after another dropped connection while jumping and found that now I was being instantly thrown out of the game immediately on entering 3d space, every single time.

That was on the 29th.
 
Last edited:

acegeordie

A
2 attempts to get in, 2 CTD's on the spinning ship screen. attempt 3 coming as soon as the crash report is sent

Attempt 3, CTD on spinning ship again......whens 3.04 coming out? lol

Attempts 4,5,6 CTD on spinning ship screen. Not funny now.

After leaving the game alone for 3 hours since i last posted on this thread (above), I have retried to get in-game and still I get no further that the spinning ship loading screen before CTD.
Thats 10 attempts and 10 CTD's. Yes a Ticket has been raised (ID: 42511). I never had a single CTD before beta 3. I am a sad Panda :(
 

MINDWIPE

MINDWIPE
trader4u said:
no, not for me unfortunally, i havent been able to start any game since last update(s) 3.02, 3.03 "openplay" or "solo"
had no such problems before update 3.xx
i'm on wired connection(s) only... with no packet loss(in cmd line, ping i checked), or windows firewall issue, avast swithed to 'game mode'
and yes, its all been ticketed, b.t.w.

pc:4Gb ram, msi R7970 lightning BE, ocz vertex 2 ssd´s in raid0 mode
and i sometimes play on my laptop as well, wich has the same connection issues.

its probably a well documented problem, but i wanted to let it be known anyway.
Click to expand...

^^^ same connection issues on both pc's... theres your hint right there... have your reset your router lately?! that sound more lilke your ISP connection rather than the game if its struggling on two seperte PC's that are different builds and configurations that can run the game but now suddnely are timing out!

it sounds more likely your connection is being throttled for over use.. try not running anything except the game on your connection. incidentally clean out the excess internet garbage (cookies tmp files etc, run a malware scan and a full defrag. and check your exceptions settings as game mode wont make a beans worth of difference if your router being taxed by background processes..

should all that fail and the game wont run.. THEN ticket it as you've eliminated all other possiblities m8 :)


p.s als validate your game files also (its in the menu)
 
Last edited:
Status
Thread Closed: Not open for further replies.
Back
Top Bottom