[mazex]

Originally Posted by AndyJWest

I've decided that another project needs more work first. I'm going to write an application that randomly disconnects me from Rise of Flight multiplayer servers every few hours. It won't help me stay connected, it won't help me find out what else is doing it, but at least I'll have the satisfaction of knowing what might be causing it some of the time...

Yup. CloD isn't alone in having problems. There I was in a D.F.W., feeling smug as I'd just dropped a sample of the Kaiser's best bombs on the enemy from the astonishing height of 2,500m (RoF bombers tend to be somewhat realistic in the rate-of-climb department, in that they don't seem to have one), and heading back over the mud below. Glanced back to see what the AI gunner was doing (a crack shot, but stupid - some things never change), and he disappeared before my eyes. Along with the gun, and everything else, except a hole where his cockpit had been. And no, it wasn't some bounder in a Camel or a Spad, just a bug - that promptly lead to a message that I'd been disconnected. Yup. A statement of the obvious, with no clue whatsoever as to why. Actually, that gives me an idea. I'll write an error-message interceptor, that replaces useless generalisations ("parameter error") with ultra-specific randomly-generated ones ("Negative dividend in procedure wingFoldGammaCorrectionParseURL - preemptive stack-underflow"). Again, no use for actually fixing anything, but at least it gives the illusion that it is fixable...

Lol, RoF sure have their problems too (even though it's a truly great game at heart). The first months where almost as painful as for CloD, but they did catch up to make it rather robust after a year or so... But just like you describe, the pain of dying in an unhandled exception is the worst one

/mazex