Patch Notes Update Beta 2.02 incoming

Status
Thread Closed: Not open for further replies.
Locks Up on Main Menu

2.02 issue. As soon as I log in now I get past the Frontier logo's and to the main menu. I can see about two seconds after getting to the main the game freezes. I can move the mouse, i can hear the sound, but the game does not respond.
bummer...
:S

Edit: I did find a rather large (1gb) netLog.log file in my install /Logs folder for whatever that's worth.
 
Last edited:
Will FD be able to remove big log files

Will FD be able to remove big log files or is it up to the user to delete them??
If the game will auto delete them its not a problem however if it does not then many of us will have wasted HDD space on large log files largest reported so far ive seen a massive 17gb
 
Last edited:
Yeah but I'm not getting these hug log files in the appdata sub-directories, which is odd :S

I'm not getting huge netlogs either. I am getting some weird notifications in them though...


14-10-01-23:04 GMT Summer Time (22:04 GMT)
{23:04:46} Start Log for this machine: <REDACTED>:63449 - <REDACTED>
{23:05:00} ConnectToServerActivity: response
<?xml version="1.0" encoding="utf-8"?>
<data><servers><server><ip>35342e37332e3131322e313833</ip><port>19364</port></server></servers><rescueservers/></data>

{23:05:00} New Primary Server: <REDACTED>:19364
{23:05:00} Now using address <REDACTED>:63449 for this machine after STUN reply
{23:05:00} Established MTU=1500
{23:05:05} EnterLocation: response
<?xml version="1.0" encoding="utf-8"?>
<data><servers><server><ip>35342e37332e3131322e313833</ip><port>19364</port></server></servers><rescueservers/></data>

{23:05:05} EnterLocation: Using UDP server address <REDACTED>:19364 from webserver
{23:05:05} System:37(i Bootis) Body:3 Pos:(42.312,999.011,-13.6671)
{23:05:06} System:37(i Bootis) Body:3 Pos:(42.312,999.011,-13.6671)
{23:05:06} soft sync after hard sync - are params ok?
{23:05:21} FailToJoinSession1: 0x000004cbb4e0032e: at 15.3s : 213.81.105.164:53216 x 5 Name Unknown
{23:05:21} FailToJoinSession1: 0x000004cbb4e0032d: at 15.3s : 213.81.105.164:53216 x 4 Name Unknown
{23:05:58} Cloning dying object #000004cbbcf1e022
{23:06:12} FailToJoinSession1: 0x000000024bd06f8b: at 30.0s : 86.2.18.186:56682 x 4 # Name Unknown
{23:06:57} FailToJoinSession1: 0x000000024bd06f8b: at 30.0s : 86.2.18.186:56682 x 4 # USERX-GC02QVFSL
{23:07:10} Skipped +OBJ 0x000004cbbcf1e022 because sessions do not intersect(?)
{23:07:10} Skipped +OBJ 0x000004cbbc41d30f because sessions do not intersect(?)
{23:07:10} Skipped +OBJ 0x000004cbbcf1e022 because sessions do not intersect(?)
{23:07:10} Skipped +OBJ 0x000004cbbc41d30f because sessions do not intersect(?)


<REDACTED> Been added by myself. No idea if the info is sensitive or not.
 
Took the day off to play Beta 2, not managed to play for more than 20-25 seconds in the entire day. Pretty cheesed off at wasting a day sitting here but I guess they are trying to fix it so can't complain too much.

No, you can't complain.
To be honest, i thought this would happen this way.
No offence, but taking a day off right at the launch of an new beta is very naive. ;)
This is still a very active developed Beta, and so much can happen on our customer PCs.
For me i thought 3 days later 2.03 would be out scince FD are great Developers,
and then it would be playable for the most.

This effort to fix the Game and keeping us informed has me not given a single second
to regret that i bought skins for 18€ just to support FD a little more. :cool:
 
Better, much better. But still 3 crashes/drops in 20 minutes.
1. CTD on exiting HS
2. Server Error on exiting HS
3. CTD on exiting HS - this time with crash dump to send - hopefully help out the investigation.

I found some data - sold it for 1,600cr. That was nice.
Made a profit finally, as I could get into SC to land and dock to sell my stuff
Slammed into a sun doing 25c - the sun was not my target, so SC ignore gravity wells now?? :eek:

Feels better than 2.00, that's for sure. :D

Slim
 
It generated a 87GB netlog file !!! :eek:

It seems to repeat these lines:

{08:23:13} packed a parcel with zero letters!
<no log>
original m_schedulingValue=1.000000, requestSchedulingValue=0.000000 letterSchedulingValue=1.000000 resendUrgency=0.000000 to=54.216.22.90:19364 x 10 WIN-UJO7F3XL804
{08:23:13} packed a parcel with zero letters!
<no log>
original m_schedulingValue=1.000000, requestSchedulingValue=0.000000 letterSchedulingValue=1.000000 resendUrgency=0.000000 to=54.216.22.90:19364 x 10 WIN-UJO7F3XL804
{08:23:13} packed a parcel with zero letters!
<no log>
original m_schedulingValue=1.000000, requestSchedulingValue=0.000000 letterSchedulingValue=1.000000 resendUrgency=0.000000 to=54.216.22.90:19364 x 10 WIN-UJO7F3XL804
{08:23:13} packed a parcel with zero letters!
<no log>
original m_schedulingValue=1.000000, requestSchedulingValue=0.000000 letterSchedulingValue=1.000000 resendUrgency=0.000000 to=54.216.22.90:19364 x 10 WIN-UJO7F3XL804
{08:23:13} packed a parcel with zero letters!
<no log>
original m_schedulingValue=1.000000, requestSchedulingValue=0.000000 letterSchedulingValue=1.000000 resendUrgency=0.000000 to=54.216.22.90:19364 x 10 WIN-UJO7F3XL804
{08:23:13} packed a parcel with zero letters!
<no log>
original m_schedulingValue=1.000000, requestSchedulingValue=0.000000 letterSchedulingValue=1.000000 resendUrgency=0.000000 to=54.216.22.90:19364 x 10 WIN-UJO7F3XL804
 
Last edited:
just popped onto beta 2.02 for 40 mins.

i tried all but no joy connecting, however no problems with solo, once i got on - it took 2 tries.

managed to do a few deliveries from aulin to iboots and then to styx.

a cool 7k or so.

all worked well, looking forward to everyone having such an experience and in all. Well pleased that the space issues and the OTT space dust as well as canopy dirt has been fixed, and the performance is still fantastic for me (on low).

just need to get the galaxy map working in the rift now..... but i think the devs have earned a few hrs shut eye today :)
 
I only crash when Jumping to Dahan. Full client crash.
When I jump to the LP 98-132 I do not crash, but I do disconnect if I set the destination with the galactic map, if I set it with the location scroll menu I make the jump just fine.
 
After clearing logs and after one more menu freeze, i open the netLog.log . ... ..

:eek: :eek: :eek: !?!?!?!?

2856554 lines of the same message!!!! :


Code:
original m_schedulingValue=1.000000, requestSchedulingValue=0.000000 letterSchedulingValue=1.000000 resendUrgency=0.000000 to=54.73.193.222:19364 x 9 WIN-UJO7F3XL804
{02:14:02} packed a parcel with zero letters!
<no log>
 
Had more luck since the last message regarding server issues. Still crashing a fair bit coming out of hyperspace. Solo mode seems to solve that but in general things have improved for me.

Good work FD and good night!
 
Okay, after completely cleaning my PC of everything Frontier related and doing a fresh install, it's still freezing on the menu screen.

Just wondering, I'm using Windows 8.1. Is this happening to people with OS other than 8.1?

i thought about doing this glad i didnt
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom