Australian Players ONLY 11-23-2012 Diagnostic Testing

Discussion in 'Player Support' started by Veratu, Nov 22, 2012.

  1. Tullerion

    I still get the hit play nothing happens every now and then, but not as bad, i do actually get in but it takes about 10 -15 seconds. My ISP is Internode.

    Haven't had much chance to play the past day and a bit due to unrelated connection issues -.-'
  2. Veratu SOE

    Kaizan, I've been following your posts and PMs for a couple days. Are you just disconnecting and unable to log back in? What happens after 20 minutes?
  3. Astromaniac

    The game keeps crashing for me after about 2 minutes.
  4. Veratu SOE

    Are you crashing? Or are you disconnecting?

    If you are disconnecting, are you by chance using one of these as your router/firewall? : http://www.netcommwireless.com/product/3g/3g21wb
  5. Forky-05

    In straight away! Happy camper.
  6. Astromaniac

    Weird, doesn't seem to be happening anymore. But it was crashing to desktop with the just the planetside2.exe stopped working message.
  7. Kaizan

    Well the game first stops working (freezes for a few seconds) then it drops to the planetside2.exe has stopped responding/working msg and it automatically closes everything down.

    From there I have to relaunch everything again from steam. Logging in and everything has no issues. just after abit of playing it dies =[
  8. Darkening Kaos

    I logged on at 2212 Adelaide local and had the situation Diablo suffers from, lasted for two minutes before everything froze and I crashed the client. I noticed I had a really bad internet connection - I have a graphic monitoring program that displays up/download through put - there is a marked difference in the characteristics between my first access to Briggs and the second a minute or so later. Wish I knew how to add that picture to this post so you could see it. Worked it out.
    [IMG]
  9. MrMchale

    Have noticed a couple of times tonight my client starts to bug out with what appears to be tearing and white out after a couple of hours of play.. have heard the same from a few others..not sure of what further info I could supply
  10. Darkening Kaos

    Started off so well and then most of my post was wiped for some reason.
    [IMG]
    This is from my recent visit to Briggs where I experienced Diablo's problem, started at approx 1415 Adelaide +9,5 GMT. At point A is where I executed the tracert procedure and closure was by means closing the window when unloading assets stalled at 68%. tracert showed the following:

    Tracing route to 69.174.220.26 over a maximum of 30 hops

    1 * * * Request timed out.
    2 224 ms 270 ms 318 ms [Censored]
    3 187 ms 239 ms 189 ms 119.225.12.101
    4 * * * Request timed out.
    5 * 862 ms 779 ms bundle-ether15.ken39.sydney.telstra.net [165.228.132.205]
    6 218 ms 199 ms 279 ms bundle-ether2.chw48.sydney.telstra.net [203.50.6.181]
    7 299 ms 258 ms 279 ms bundle-ether6.chw-core2.sydney.telstra.net [203.50.6.153]
    8 341 ms 226 ms 239 ms 10gigabitethernet7-1.chw45.sydney.telstra.net [203.50.20.183]
    9 * 781 ms * equini3.lnk.telstra.net [139.130.117.214]
    10 * * 810 ms 27.111.240.140

    I do have a tracert from my earlier session but it didn't complete, possibly because a lot was going on and tracert did not have any bandwidth to complete the task - also possibly explaining the huge times recorded for each hop.

    Code:
    Tracing route to 69.174.220.26 over a maximum of 30 hops
     
      1    *        *        *    Request timed out.
      2  146 ms  128 ms    99 ms  [Censored]
      3  198 ms  129 ms  139 ms  119.225.12.101
      4    *        *        *    Request timed out.
      5    *      813 ms  820 ms  bundle-ether15.ken39.sydney.telstra.net [165.228.132.205]
      6  179 ms  160 ms  229 ms  bundle-ether2.chw48.sydney.telstra.net [203.50.6.181]
      7  468 ms  368 ms  289 ms  bundle-ether6.chw-core2.sydney.telstra.net [203.50.6.153]
      8  128 ms  119 ms  119 ms  10gigabitethernet7-1.chw45.sydney.telstra.net [203.50.20.183]
      9  618 ms  
    I hope this helps you narrow down the problem.