Patch Notes Update Server Side Update 10/10/14

Status
Thread Closed: Not open for further replies.

Arindor

Arindor
Yep, similar stuff for me. Scanning a new system doesn't recognize the body being scanned and stellar cartography option at a starport just hangs. Oh well, at least I can get some flying practice in and some BB missions.
 

Harbinger

Volunteer Moderator
Harbinger
CaptainKremmen said:
My "Basic Discovery Scanner" just went berserk.

I scanned a new system, got 4-5 new bodies announced in blue... but they didn't appear in my nav list.

I then flew near one planet, and got spammed with endless "1 astronomical body discovered" messages... unending. Without it appearing as a labelled body.

A bit wacko right now! :)
Click to expand...

Zhang said:
One related issue, scanning an unknown planet still returns "unknown" after the scanner does it's thingy. Tried it couple of times in different systems. Some planets get discovered and named properly, one or two never gets past "unknown."
Click to expand...

Yeah there are definitely still issues with exploration, some of which were introduced in v2.05 (or when I upgraded my regular scanner).

  • When you jump into an unexplored system you tend to get "Discovered 1 Astronomical Object(s)" appear on screen several times as you automatically detect the star. only after it's finished spamming the same message a few times can you actually select it as an unknown object and commence scanning.
  • When you manually trigger the D-Scanner and get the "Discovered [X] Astronomical Object(s)" message it doesn't always add the object(s) as unknown in your navigation tab and multiple manual scans may be necessary to get the object(s) to appear. This is most likely the same thing as above which is why multiple automatic scans happen in the initial star discovery scenario.
  • Some objects remain as "UNKNOWN" even after completion of scanning.
  • When tracking moving objects against the backdrop they tend to be bright at long distances but get dimmer to the point of disappearing at closer ranges. I don't recall this happening in v2.04, the objects got continually brighter the closer you got to them.
  • As others have mentioned, Universal Cartographics is not able to be accessed currently. It just comes up with "Unable to get cartography listing from the webserver" after 1-2 minutes of the "Stand By" animation.

On the plus side you can now visit WREDGUIA star systems without it crashing so that's a plus. :D
 
Last edited:

Taomyn

Taomyn
hchalkley said:
This might be an MTU issue: in Beta2, when the game connects to the server, we check to see the biggest packet we can successfully send, but it turns out that in some cases the route back from the server to the game has a smaller maximum packet size.

Bulletin board results are the main case where the server has a large chunk of data to send back to the client.

I have already rewritten this MtuDiscovery code to be bidirectional for Beta3, but in the meantime, try inserting a setting such as mtu="1400" in your appconfig.xml file to see if that helps. (This should go in with the other settings in the <Network ... > section)
Click to expand...

Sorry, made no difference. I even took it down to 1200 and 1000. Whatever is the cause it happened with 2.04 because I was happy and working with 2.03 and earlier.

I just hope you can fix this soon.
 

Taomyn

Taomyn
hchalkley said:
This might be an MTU issue: in Beta2, when the game connects to the server, we check to see the biggest packet we can successfully send, but it turns out that in some cases the route back from the server to the game has a smaller maximum packet size.

Bulletin board results are the main case where the server has a large chunk of data to send back to the client.

I have already rewritten this MtuDiscovery code to be bidirectional for Beta3, but in the meantime, try inserting a setting such as mtu="1400" in your appconfig.xml file to see if that helps. (This should go in with the other settings in the <Network ... > section)
Click to expand...

Actually, maybe it would work if the game took notice or I'm entering it into the XML incorrectly. I put it so the section looked like:

Code: 
	<Network
	  Port="0"
	  LogFile="netLog"
	  DatestampLog="0"
	  MTU="1400"
	  >

But I see in the log:

Code: 
14-10-10-20:07 W. Europe Summer Time  (18:07 GMT)
{20:07:54} Start Log for this machine: 192.168.1.14:52279 - F
{20:08:10} ConnectToServerActivity: response
<?xml version="1.0" encoding="utf-8"?>
<data><servers><server><ip>35342e37332e3131322e313833</ip><port>19364</port></server></servers><rescueservers></rescueservers></data>
{20:08:10} New Primary Server: 54.73.112.183:19364
{20:08:10} Now using address 195.2.6.17:52279 for this machine after STUN reply
{20:08:10} Established MTU=1500
{20:08:16} EnterLocation: response
<?xml version="1.0" encoding="utf-8"?>
<data><servers><server><ip>35342e37332e3131322e313833</ip><port>19364</port></server></servers><rescueservers></rescueservers></data>
{20:08:16} EnterLocation: Using UDP server address 54.73.112.183:19364 from webserver
{20:08:16} System:1(LP 71-157) Body:3 Pos:(-479.877,334.52,-811.058) 
{20:08:16} System:1(LP 71-157) Body:3 Pos:(-479.877,334.52,-811.058) 
{20:08:19} ModularStationAttachComponent: object kinematic Alli_Spacer1000m_0x0000000100000018 is not ready
{20:08:19} ModularStationAttachComponent: object kinematic Alli_Spacer1000m_0x0000000100000018 is not ready
{20:08:25} System:1(LP 71-157) Body:3 Pos:(-479.877,334.52,-811.058) 
{20:08:55} Sync mismatch & connected!
{20:08:55} FailedToConnect: in InGame
{20:08:55} Established MTU=1500
{20:08:56} ConnectToServerActivity: response
<?xml version="1.0" encoding="utf-8"?>
<data><servers><server><ip>35342e37332e3131322e313833</ip><port>19364</port></server></servers><rescueservers></rescueservers></data>
 

Tinman

Tinman
Taomyn said:
Actually, maybe it would work if the game took notice or I'm entering it into the XML incorrectly. I put it so the section looked like:

Code: 
	<Network
	  Port="0"
	  LogFile="netLog"
	  DatestampLog="0"
	  MTU="1400"
	  >

But I see in the log:

Code: 
14-10-10-20:07 W. Europe Summer Time  (18:07 GMT)
{20:07:54} Start Log for this machine: 192.168.1.14:52279 - F
{20:08:10} ConnectToServerActivity: response
<?xml version="1.0" encoding="utf-8"?>
<data><servers><server><ip>35342e37332e3131322e313833</ip><port>19364</port></server></servers><rescueservers></rescueservers></data>
{20:08:10} New Primary Server: 54.73.112.183:19364
{20:08:10} Now using address 195.2.6.17:52279 for this machine after STUN reply
{20:08:10} Established MTU=1500
{20:08:16} EnterLocation: response
<?xml version="1.0" encoding="utf-8"?>
<data><servers><server><ip>35342e37332e3131322e313833</ip><port>19364</port></server></servers><rescueservers></rescueservers></data>
{20:08:16} EnterLocation: Using UDP server address 54.73.112.183:19364 from webserver
{20:08:16} System:1(LP 71-157) Body:3 Pos:(-479.877,334.52,-811.058) 
{20:08:16} System:1(LP 71-157) Body:3 Pos:(-479.877,334.52,-811.058) 
{20:08:19} ModularStationAttachComponent: object kinematic Alli_Spacer1000m_0x0000000100000018 is not ready
{20:08:19} ModularStationAttachComponent: object kinematic Alli_Spacer1000m_0x0000000100000018 is not ready
{20:08:25} System:1(LP 71-157) Body:3 Pos:(-479.877,334.52,-811.058) 
{20:08:55} Sync mismatch & connected!
{20:08:55} FailedToConnect: in InGame
{20:08:55} Established MTU=1500
{20:08:56} ConnectToServerActivity: response
<?xml version="1.0" encoding="utf-8"?>
<data><servers><server><ip>35342e37332e3131322e313833</ip><port>19364</port></server></servers><rescueservers></rescueservers></data>
Click to expand...

Doublecheck that you are in the right directory. Due to how older versions of the game was installed you might have two different directories.
 

RickDangerous

R
Will this also fix module updates and trade-ins? Currently if I have a 500k FSD and want a 1.5M FSD I don't seem to get anything for the old one which is... painful.
 

Gromit

Gromit
I'm currently docked at Murray Port in G 180-18, orbiting a gas giant with several moons within 4.5ls, which although previously scanned on a previous night (by pointing the ship towards them at close proximity), were still showing as unknown.

So I have undocked and tried rescanning them whilst under standard drive. One of them has changed to a named moon after scanning fairly quickly, but the second stayed as unknown for several minutes after being scanned before becoming named. A third moon has remained as unknown.

I have entered SC and flown towards this third moon. As soon as I entered SC, it restarted the scan, but at the end, again remained as unknown. Coming out of SC very close to the moon restarts the scan, but again no positive result to report. So I've come back and redocked at Murray Port.

Selecting the station cartographics section, after a period of minute or two of the message 'Stand By', I get the system message saying 'unable to get cartography listing from the webserver'.
 

Gibbonici

Gibbonici
Tinman said:
Doublecheck that you are in the right directory. Due to how older versions of the game was installed you might have two different directories.
Click to expand...

I've just done this on my own install, and it comes up the same. I set MTU to 1400, but the log says it's established at 1500.

I'm on a BT Home Hub 4 that defaults to 1500, so that might be what the log is, er, logging.
 

Athan

Athan
Yeah that MTU setting isn't working here either. The game usually detects it as 1244, I put 1200 in, it still detects 1244. Definitely the correct file as it's picking up on Port and some verbose logging options support gave me for that same section.
 

GolemXIV

GolemXIV
The BB issue is not on our side. Why? Sometimes it works, most of the time not. I changed and tried anything , it doesn´t make any difference.
 

Falkenherz

Falkenherz
Yeah, well. Still crashing on 5 of 6 hyperjump exits. You are receiving plenty of reports from your crash reporter from me this night.
 

Taomyn

Taomyn
Tinman said:
Doublecheck that you are in the right directory. Due to how older versions of the game was installed you might have two different directories.
Click to expand...

There's only one place that file is and that's:

Code: 
C:\Users\Public\Public Games\Frontier\EDLaunch\Products\FORC-FDEV-D-1001

and it's the one I edited
 

Daerdor

Daerdor
First the good news: the commodity market update in starports seems nicely fixed, there are many more ship upgrades and the trading route map is displaying correct data again.

However, I'm now experiencing severe performance/connection issues:
- Longer loading times (rotating sidewinder)
- Stuttering / lag in all systems, supercruise seems OK
- Severe stuttering in hyperspace
- Infinite hyperspace (not exiting from hyperspace)
- Docking clearance timeout
- Landing at a starport and suddenly appearing/teleporting outside of the station
- Launching at a starport and without touching any controls the ship moves sideways (while there is no issue upon landing, the ship stays perfectly still)
- Destroying a wanted player, bounty message appeared but not registered in ship
- Extremely slow loading of Bulletin Board

Overall I had to kill the game in the taskmanager multiple times in order to continue.

I also tried the MTU 1400 setting in AppConfig.xml but the NetLog.log keeps showing 1500.
 

RikonGB

RikonGB
Arindor said:
Yep, similar stuff for me. Scanning a new system doesn't recognize the body being scanned and stellar cartography option at a starport just hangs. Oh well, at least I can get some flying practice in and some BB missions.
Click to expand...

Having exactly same issue, thought it was just me scanning wrong till got error at station cartography.
 

Isocar

I
Unplayable

The game was working just fine for me in 2.0.4. I was seeing 30-60fps in 4K pretty much everywhere. I was getting better performance with Beta 1.

With this latest update, the game will not load at all in Open Play. In Solo, I have 3-15fps...

... not really playable for me ...

Will wait for the next update.
 

Devil

Devil
I don't think these problems are MTU settings. There seems to be issues with this build generally, 2.04 was great for me personally, 2.05 is nearly unplayable.


Just had a station disappear in a cloud of dust.
BB lagging like crazy
Purchased upgrade, and got server error.
 

Zhang

Zhang
Devil said:
I don't think these problems are MTU settings. There seems to be issues with this build generally, 2.04 was great for me personally, 2.05 is nearly unplayable.


Just had a station disappear in a cloud of dust.
BB lagging like crazy
Purchased upgrade, and got server error.
Click to expand...

Ditto. Been trying to upgrade FSD couple of times after a wait get server 401 error.
 

Molly Dog

M
Spent a good hour and a half in game following the server side upgrade...

- First load tonight got stuck on spinning s/w
- Killed it and tried again fine
- Loaded quickly
- Most s/c exits were fine

Commodity market balance is much better now.

One issue opening Uni Cart... long, long, long hang... Then "unable to get cartography data from the webserver"... :-(
 

Edward Lewis

Edward Lewis
Harbinger said:
Yeah there are definitely still issues with exploration, some of which were introduced in v2.05 (or when I upgraded my regular scanner).

  • When you jump into an unexplored system you tend to get "Discovered 1 Astronomical Object(s)" appear on screen several times as you automatically detect the star. only after it's finished spamming the same message a few times can you actually select it as an unknown object and commence scanning.
  • When you manually trigger the D-Scanner and get the "Discovered [X] Astronomical Object(s)" message it doesn't always add the object(s) as unknown in your navigation tab and multiple manual scans may be necessary to get the object(s) to appear. This is most likely the same thing as above which is why multiple automatic scans happen in the initial star discovery scenario.
  • Some objects remain as "UNKNOWN" even after completion of scanning.
  • When tracking moving objects against the backdrop they tend to be bright at long distances but get dimmer to the point of disappearing at closer ranges. I don't recall this happening in v2.04, the objects got continually brighter the closer you got to them.
  • As others have mentioned, Universal Cartographics is not able to be accessed currently. It just comes up with "Unable to get cartography listing from the webserver" after 1-2 minutes of the "Stand By" animation.

On the plus side you can now visit WREDGUIA star systems without it crashing so that's a plus. :D
Click to expand...

Thanks for all the feedback. Much appreciated. Have you logged tickets pertaining to this?
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom