might be of help to you..
One such failed start attempt. showed the red glowing rotating cobra for 3 sec and then black screen with music:
it repeats the last 3 lines of the log forever. The file was 2 GByte after 1 minute or 2.
(thanks to the one for pointing out the observation of the extremly large growing logfiles)
(and no sorry dont liek your support ticket system.. pls create a proper beta report system)
One such failed start attempt. showed the red glowing rotating cobra for 3 sec and then black screen with music:
Code:
{18:22:15} New Primary Server: 54.73.141.153:19364
{18:22:16} Now using address xxx.xxx.xxx.xxx:61860 for this machine after STUN reply
{18:22:16} The message was too large for the specified buffer and (for unreliable protocols only) any trailing portion of the message that did not fit into the buffer has been discarded.
{18:22:16} The message was too large for the specified buffer and (for unreliable protocols only) any trailing portion of the message that did not fit into the buffer has been discarded.
{18:22:17} The message was too large for the specified buffer and (for unreliable protocols only) any trailing portion of the message that did not fit into the buffer has been discarded.
{18:22:17} The message was too large for the specified buffer and (for unreliable protocols only) any trailing portion of the message that did not fit into the buffer has been discarded.
{18:22:17} Established MTU=1492
{18:22:35} EnterLocation: response
<?xml version="1.0" encoding="utf-8"?>
<data><servers><server><ip>35342e3231362e32322e3930</ip><port>19364</port></server></servers><rescueservers/></data>
{18:22:35} EnterLocation: Using UDP server address 54.216.22.90:19364 from webserver
{18:22:35} New Primary Server: 54.216.22.90:19364
{18:22:35} FailedToConnect: in ServerAdminRegister::CreateMissionAcceptRequest
{18:22:35} 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
{18:22:35} 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
{18:22:35} packed a parcel with zero letters!
<no log>
it repeats the last 3 lines of the log forever. The file was 2 GByte after 1 minute or 2.
(thanks to the one for pointing out the observation of the extremly large growing logfiles)
(and no sorry dont liek your support ticket system.. pls create a proper beta report system)