Black screen after champ select

Comment below rating threshold, click here to show it.

GLoop

Member

03-09-2014

Everytime i go through champ select everything is fine, and then as soon as it is suppose to go to loading screen it just goes black and never loads. how do i fix this please? and these are my netlogs.

Sun Mar 09 22:59:40 2014: LogOut_File: : logfile started
Sun Mar 09 22:59:40 2014: Net Status: low-level initialize success.
Sun Mar 09 22:59:40 2014: Note that this new version (12/19/2011) has reduced the frequency of updates so the numbers will be larger
Sun Mar 09 22:59:40 2014: time = time of logging
Sun Mar 09 22:59:40 2014: address = address of IP address
Sun Mar 09 22:59:40 2014: incoming = total size of messages set to me in bytes. Spikes can indicate lag.
Sun Mar 09 22:59:40 2014: outgoing = total size of messages set from me in bytes. Spikes can indicate lag.
Sun Mar 09 22:59:40 2014: app_ctos = client to server bytes delta excluding overheads (app data only)
Sun Mar 09 22:59:40 2014: app_stoc = server to client bytes delta excluding overheads (app data only)
Sun Mar 09 22:59:40 2014: loss = number of packets lost. Can indicate lags. Some node on the network is dropping packets or taking to long and we have to resend them.
Sun Mar 09 22:59:40 2014: sent = number of packets sent. Spikes can indicate lag.
Sun Mar 09 22:59:40 2014: ping = how long it takes for a packet to get back and forth. Spikes can indicate lag.
Sun Mar 09 22:59:40 2014: variance = how much the ping is changing from avg ping. Spikes can indicate lag.
Sun Mar 09 22:59:40 2014: reliable delayed = This occurs when we drop reliable packets from sending this frame because we are sending to much data. Unreliable are more likely to be dropped than reliable.
Sun Mar 09 22:59:40 2014: unreliable delayed = This occurs when we drop unreliable packets from sending this frame because we are sending to much data.
Sun Mar 09 22:59:40 2014: app update delayed = This occurs when the app is taking to long to run code caused by network packets (ie CPU) and packets are delayed until the next frame
Sun Mar 09 22:59:40 2014: Time spent in critical section (frame) = This is the time the network thread is blocking the main thread from doing anything.
Sun Mar 09 22:59:40 2014: [time], [address], [incoming], [outgoing], [app_ctos], [app_stoc], [loss], [sent], [ping], [variance], [reliable delayed], [unreliable delayed], [app update delayed], [Time spent in critical section (frame)]

Sun Mar 09 18:11:06 2014: LogOut_File: : logfile started
Sun Mar 09 18:11:06 2014: Net Status: low-level initialize success.
Sun Mar 09 18:11:06 2014: Note that this new version (12/19/2011) has reduced the frequency of updates so the numbers will be larger
Sun Mar 09 18:11:06 2014: time = time of logging
Sun Mar 09 18:11:06 2014: address = address of IP address
Sun Mar 09 18:11:06 2014: incoming = total size of messages set to me in bytes. Spikes can indicate lag.
Sun Mar 09 18:11:06 2014: outgoing = total size of messages set from me in bytes. Spikes can indicate lag.
Sun Mar 09 18:11:06 2014: app_ctos = client to server bytes delta excluding overheads (app data only)
Sun Mar 09 18:11:06 2014: app_stoc = server to client bytes delta excluding overheads (app data only)
Sun Mar 09 18:11:06 2014: loss = number of packets lost. Can indicate lags. Some node on the network is dropping packets or taking to long and we have to resend them.
Sun Mar 09 18:11:06 2014: sent = number of packets sent. Spikes can indicate lag.
Sun Mar 09 18:11:06 2014: ping = how long it takes for a packet to get back and forth. Spikes can indicate lag.
Sun Mar 09 18:11:06 2014: variance = how much the ping is changing from avg ping. Spikes can indicate lag.
Sun Mar 09 18:11:06 2014: reliable delayed = This occurs when we drop reliable packets from sending this frame because we are sending to much data. Unreliable are more likely to be dropped than reliable.
Sun Mar 09 18:11:06 2014: unreliable delayed = This occurs when we drop unreliable packets from sending this frame because we are sending to much data.
Sun Mar 09 18:11:06 2014: app update delayed = This occurs when the app is taking to long to run code caused by network packets (ie CPU) and packets are delayed until the next frame
Sun Mar 09 18:11:06 2014: Time spent in critical section (frame) = This is the time the network thread is blocking the main thread from doing anything.
Sun Mar 09 18:11:06 2014: [time], [address], [incoming], [outgoing], [app_ctos], [app_stoc], [loss], [sent], [ping], [variance], [reliable delayed], [unreliable delayed], [app update delayed], [Time spent in critical section (frame)]


Comment below rating threshold, click here to show it.

GLoop

Member

03-09-2014

bump


Comment below rating threshold, click here to show it.

GLoop

Member

03-10-2014

bumpper cars