I actually managed to get a log file small enough to open by starting the client then killing it with task manager immediatelty.
It just keeps repeating this message block over and over:
{22:15:56} packed a parcel with zero letters!
<no log>
original m_schedulingValue=1.000000, requestSchedulingValue=0.000000 letterSchedulingValue=1.000000 resendUrgency=0.000000 to=54.195.170.117:19364 x 9 WIN-UJO7F3XL804
Don't know if FD development are scanning this thread but I hope the above helps. Stay with it guys - been there myself many a time.
Just use notepad++ or some other capable editor to open large text files.
I don't really feel like posting my log in public.. isn't there a one-way-dropbox? Meh... well..
14-10-01-23:23 W. Europe Daylight Time (21:23 GMT)
{23:23:15} Start Log for this machine: <MY-LAN-IP>:64667 - <MY-HOSTNAME>
{23:23:47} TURN detect NAT type: ErrUnknown
{23:23:53} ConnectToServerActivity: response
<?xml version="1.0" encoding="utf-8"?>
<data><servers><server><ip>35342e37332e3139332e323232</ip><port>19364</port></server></servers><rescueservers/></data>
{23:23:53} New Primary Server: 54.73.193.222:19364
{23:23:53} Now using address <MY-WAN-IP>:64667 for this machine after STUN reply
{23:23:53} packed a parcel with zero letters!
<no log>
original m_schedulingValue=1.000000, requestSchedulingValue=0.000000 letterSchedulingValue=1.000000 resendUrgency=0.000000 to=54.73.193.222:19364 x 9 WIN-UJO7F3XL804
{23:23:53} packed a parcel with zero letters!
<no log>
original m_schedulingValue=1.000000, requestSchedulingValue=0.000000 letterSchedulingValue=1.000000 resendUrgency=0.000000 to=54.73.193.222:19364 x 9 WIN-UJO7F3XL804
{23:23:53} packed a parcel with zero letters!
<no log>
Just seen that the port at "<LAN-IP>:64667" varies each launch. The log file fills up with the segment repeated all over and over:
original m_schedulingValue=1.000000, requestSchedulingValue=0.000000 letterSchedulingValue=1.000000 resendUrgency=0.000000 to=54.73.193.222:19364 x 9 WIN-UJO7F3XL804
{23:23:53} packed a parcel with zero letters!
<no log>
netLog.log grows up to 400mb and more within seconds.