Can't download the latest update

No surprises here Andrew - but do you have any tricks up your sleeve? Must have tried 20 times now. It shoots from 0% to about 60% in about half a second and then just jams there.

Java Plug-in 10.9.2.05
Using JRE version 1.7.0_09-b05 Java HotSpot(TM) Client VM
User home directory = C:\Users\Jason
----------------------------------------------------
c:   clear console window
f:   finalize objects on finalization queue
g:   garbage collect
h:   display this help message
l:   dump classloader list
m:   print memory usage
o:   trigger logging
q:   hide console
r:   reload policy configuration
s:   dump system and deployment properties
t:   dump thread list
v:   dump thread stack
x:   clear classloader cache
0-5: set trace level to <n>
----------------------------------------------------
    Match: beginTraversal
Match: digest selected JREDesc: JREDesc[version 1.6+, heap=-1--1, args=null, href=http://java.sun.com/products/autodl/j2se, sel=false, null, null], JREInfo: JREInfo for index 0:
    platform is: 1.7
    product is: 1.7.0_09
    location is: http://java.sun.com/products/autodl/j2se
    path is: C:\Program Files (x86)\Java\jre7\bin\javaw.exe
    args is: null
    native platform is: Windows, x86 [ x86, 32bit ]
    JavaFX runtime is: JavaFX 2.2.3 found at C:\Program Files (x86)\Java\jre7\
    enabled is: true
    registered is: true
    system is: true

    Match: ignoring maxHeap: -1
    Match: ignoring InitHeap: -1
    Match: digesting vmargs: null
    Match: digested vmargs: [JVMParameters: isSecure: true, args: ]
    Match: JVM args after accumulation: [JVMParameters: isSecure: true, args: ]
    Match: digest LaunchDesc: null
    Match: digest properties: []
    Match: JVM args: [JVMParameters: isSecure: true, args: ]
    Match: endTraversal ..
    Match: JVM args final:
    Match: Running JREInfo Version    match: 1.7.0.09 == 1.7.0.09
     Match: Running JVM args match: have:<>  satisfy want:<>



^ This is my entire Java console reading. Can leave it there for 5 minutes and it never goes furthur than this.

Might pay to note, much like last time, live timing loads in a matter of seconds with no problems at all.

Ok sorry to panic Andrew. It worked on about the 40th time. No idea why I have so much trouble getting updates on this one computer only. Oh well, for now it's working any way.

I'm getting similar results - OSX 10.8.2 using Safari/Java x64 and Windows 7/Firefox17/Java 7 u10. The applet will start loading and give me a progress bar - as it reaches approximately 75% it switches to the grey screen and then nothing happens.

Looks like the same error in the Java console:

Guys just keep the window open until the 2D loads.

On a unoccasion, you may get unrecognised data, just refresh the page and it will load.

David, I literally tried 40 times to get it to work. Leaving it open just does nothing, even if you let it load for 15 minutes. I had to completely close and re-open the viewer many many times to make it work. If you leave the window open when it "jams" it literally just sits there (I tried this a few times leaving it open for 5+ minutes and nothing progresses at all.)

Kade, in a nutshell they reckon it has something to do with the distance between us (Aussie/NZ in our case vs them in the UK) - Basically the other side of the world. I don't know why it makes a difference, it's not like we have slow internet or anything. Maybe Andrew could explain furthur.

Just do what I did, reload the bloody thing 50 odd times until it actually works. Even when mine did work it looked like it was going to have the same problem. Jumped to about 60%, sat there for a minute, then started doing little 2-3% increases every 5-10 seconds until the end (took about 3-4 minutes)

I'm just glad it worked on the first night this time. Last time they did an update it was a little over 2 weeks before I could get the 2d viewer to work.

This isn't the issue - or if it is, there seems to be an issue with the speed of the update being delivered. Much like Jason I waited 15-20 minutes in different browsers/sessions/VMs - many times - atleast 15-20 times in Safari without a result. This isn't a user issue, it's a server side issue either with the update being delivered incorrectly or the update speed being extremely slow.

It took me a couple tries of reloading the page before it finally updated.   

@Devs: Those of us with slow/troublesome internet connections appreciate notifications of updates to the Java console.  I received the email announcing the holiday special/2D upate as well as I saw the home page advertising the specials as well.  I was able to update my applet hours ahead of my scheduled race.  No question of whether I would be able to use the 2D viewer or not.  Huge thanks!  Well done.

Worked fine for me. Loaded in 3 mins tops. and on the first try. 

Like the new update. Looking forward for the future!!

Still experiencing the same problem in Safari, same java message after clearing all Safari data.

edit: I should note that the Java applet actually dies after sitting where it stops on the log after a while. The console disappears when then applet disappears. Still sitting on grey/black screen. Can send thread dumps if that helps.

Same here.

That doesn't make it not an issue/bug though, it just means you are unaffected.

Exactly what I keep going on about and will go on about it until I am blue in the face..

New updates without fixing the ones that STILL 1 year down the line continue to happen.... and when someone brings issues up.. you get people saying that everything is fine and it's like a shout or put down on the ones with issues..

Jools Hogg and Kay Wilms have been having issues with the 2D for over 6 months now...

I have got the 2D up and running but in the past 3 races I can not zoom in to the car, as iGP has developed a stuttering lag  and it is awful to view up close and gives me a headach

Big whoopie for the ones who have it working. Well done to yourself, but done come on to others post to say "Oh it's working for me" does that solve the orig issue.. no it doesn't. Jeezzz

Although I feel like I'm yelling in to space reporting this problem, it also happens on j7 u10

Kade, your best bet is to PM Andrew regarding the matter. Chances are he's busy working on other things and isn't checking the forums.

http://igpmanager.com/play/?url=manager-profile/7

There probably isn't a lot they can do though. As I said, they reckon the problem is something to do with location because the only people who seem to get this problem are the people living on the other side of the world (eg me, you, a few other australians in the past)

If it is a locational/latency thing, there is a few things that can change - greater time out/keep alive values for one :) Ill PM him this thread

I've been out Christmas shopping and taking a little bit of time to recover from extremely intense work running the recent update.  I'll try to get this issue sorted now.  Kade, I'll PM you directly about this (thanks, I received yours).  If anyone else has similar issues could you also PM me so I can investigate in more detail.

If we find a solution or even just a workaround I'll update this thread.