NETWORK STATUS: [Error] at startup

[Weissrolf]

Hello.

I often (likely always) get NETWORK STATUS: [Error] when I try to startup FGU. This seems to lead to FGU varying between 1 to 30 seconds just to launch, often accompanied by the dreaded "not responding" message and blue circle pointer when it takes too long. FGU still is perfectly usable once the launcher finally finishes.

Log with error (17 s):

[11/22/2020 11:41:22 AM] FGU: v4.0.1 ULTIMATE (2020-11-11)
[11/22/2020 11:41:22 AM] OS: Windows 10 (10.0.0) 64bit
[11/22/2020 11:41:22 AM] GRAPHICS: NVIDIA GeForce RTX 2070 SUPER : 8011
[11/22/2020 11:41:22 AM] UI SCALE: 1
[11/22/2020 11:41:22 AM] USER: Weissrolf
[11/22/2020 11:41:22 AM] Launcher scene starting.
[11/22/2020 11:41:39 AM] NETWORK STATUS: [Error]
[11/22/2020 11:41:39 AM] Launcher scene exiting.

Log with error (5 s):

[11/22/2020 11:46:25 AM] FGU: v4.0.1 ULTIMATE (2020-11-11)
[11/22/2020 11:46:25 AM] OS: Windows 10 (10.0.0) 64bit
[11/22/2020 11:46:25 AM] GRAPHICS: NVIDIA GeForce RTX 2070 SUPER : 8011
[11/22/2020 11:46:25 AM] UI SCALE: 1
[11/22/2020 11:46:25 AM] USER: Weissrolf
[11/22/2020 11:46:25 AM] Launcher scene starting.
[11/22/2020 11:46:30 AM] NETWORK STATUS: [Error]
[11/22/2020 11:46:30 AM] Launcher scene exiting.

[Weissrolf]

Log with error (1 s):

[11/22/2020 11:49:20 AM] FGU: v4.0.1 ULTIMATE (2020-11-11)
[11/22/2020 11:49:20 AM] OS: Windows 10 (10.0.0) 64bit
[11/22/2020 11:49:20 AM] GRAPHICS: NVIDIA GeForce RTX 2070 SUPER : 8011
[11/22/2020 11:49:20 AM] UI SCALE: 1
[11/22/2020 11:49:20 AM] USER: Weissrolf
[11/22/2020 11:49:20 AM] Launcher scene starting.
[11/22/2020 11:49:21 AM] NETWORK STATUS: [Error]
[11/22/2020 11:49:21 AM] Launcher scene exiting.

[Weissrolf]

It's noteworthy that FGU is not busy during this time, CPU, network and disc load is hardly measurable.

[Weissrolf]

Log with error (30s):

[11/22/2020 11:53:08 AM] FGU: v4.0.1 ULTIMATE (2020-11-11)
[11/22/2020 11:53:08 AM] OS: Windows 10 (10.0.0) 64bit
[11/22/2020 11:53:08 AM] GRAPHICS: NVIDIA GeForce RTX 2070 SUPER : 8011
[11/22/2020 11:53:08 AM] UI SCALE: 1
[11/22/2020 11:53:08 AM] USER: Weissrolf
[11/22/2020 11:53:08 AM] Launcher scene starting.
[11/22/2020 11:53:38 AM] NETWORK STATUS: [Error]
[11/22/2020 11:53:38 AM] Launcher scene exiting.

[Moon Wizard]

The current FGU client does some initial external IP resolution in order to provide external IP information in a synchronous manner. The issue had previously been identified by @smelton; and the next build already has been modified to make the external IP resolution asynchronous and moved to our own servers. (We have been using public servers for IP resolution.)

Regards,
JPG

[Weissrolf]

I tried the DEV channel and the error remains. But at least it now only takes 1-2 seconds to timeout and finish launching. Why does that error appear anyway?

[11/22/2020 8:58:27 PM] FGU: [DEV] v4.0.2 ULTIMATE (2020-11-19)
[11/22/2020 8:58:27 PM] OS: Windows 10 (10.0.0) 64bit
[11/22/2020 8:58:27 PM] GRAPHICS: NVIDIA GeForce RTX 2070 SUPER : 8011
[11/22/2020 8:58:27 PM] UI SCALE: 1
[11/22/2020 8:58:27 PM] USER: Weissrolf
[11/22/2020 8:58:27 PM] Launcher scene starting.
[11/22/2020 8:58:27 PM] NETWORK STATUS: [Error]
[11/22/2020 8:58:28 PM] Launcher scene exiting.

[Weissrolf]

And to clarify: This thread and issue here has nothing to do with my comparison of load-times between FGU and FGC. That other thread (locked now) compared load times after the launcher was running, this thread here is about load times and NETWORK STATUS: [Error] before the launcher is accessible.

[Moon Wizard]

Please do not use the Dev channel unless asked to. There is absolutely no guarantee what is in that channel or what version it is running; which means it's worthless to report anything from there since any of the developers could be using it.

Once the next version is official released and announced in the Live channel, then check it.

Regards,
JPG

[Weissrolf]

Was the update for this rolled out today? The error does not show up in the console log anymore and launcher starts without long delay. But FGU's version number still displays as 4.0.1 (2020-11-11)?!

[LordEntrails]

Was the update for this rolled out today? The error does not show up in the console log anymore and launcher starts without long delay. But FGU's version number still displays as 4.0.1 (2020-11-11)?!
Only content/DLC was updated today.

[Moon Wizard]

You are probably still on Dev channel....

JPG

[Weissrolf]

Not on Dev channel, I specifically checked. I even deleted the channel sub-directory to make sure nothing is loaded from there. The network error does not happen anymore, thus the timeout-delay does not happen either.

https://i.imgur.com/BEocLhp.png

[LordEntrails]

Only content/DLC was updated today.
Of course, now that I say this, a short bit later 4.0.2 is now available!

[Weissrolf]

The current behavior is different from what I experienced on the Dev channel before. On the Dev channel I still got the network error, but the timeout was only 1 second short. Now there is no error, so maybe something on the SW server end was fixed that lead to the network error to begin with?

[LordEntrails]

The current behavior is different from what I experienced on the Dev channel before. On the Dev channel I still got the network error, but the timeout was only 1 second short. Now there is no error, so maybe something on the SW server end was fixed that lead to the network error to begin with?
As you have been told, the Dev channel is not for user use unless explicitly directed to do so by a developer to help them resolve a specific development issue. Errors on the dev channel should not be reported to support or the forums unless specifically told to do so by a developer. Errors on the Dev channel are to be expected.

If you insist on using the Dev channel, please don't confuse and waste people's time reporting or commenting on issues with development builds (unless you are asked to do so by a developer).

[Weissrolf]

And I did not use the Dev channel after you telling me not to. I explicitly reported about my v4.0.1 Live channel version not producing network errors anymore and put that in comparison to my original report and that one time where I checked the behavior on the Dev channel.

Here is the chronology:

1) Network error happened on v4.0.1 Live, synchronous IP resolution caused long timeout delays.

2) Network error happened on Dev channel (which I tried before you told me not to), but without long timeout delays. Asynchronous IP resolution fix was likely already implemented and working as expected (yay).

3) Network error happened on v4.0.1 Live, synchronous IP resolution caused long timeout delays again.

4) Network error did not happen on v4.0.1 Live anymore, synchronous IP resolution did not cause long timeout delay anymore. No error = no timeout.

5) Network error does not happen on v4.0.2 Live, asynchronous IP resolution does not cause long timeout delay. No error = no timeout, so I cannot give feedback about asynchronous IP resolution fix working or not.

PS: Currently the update process gets stuck at "general-addons", so testing for bug fixes seems like a bad idea until this works properly again.

[Moon Wizard]

Going to close the thread for now. If you're still seeing the issue with v4.0.2, please start a new thread with new logs and details.

Regards,
JPG

[LordEntrails]

Thank you for clarifying.