Hi All,

I’m getting some worrying hardware errors here: screen flicker, hanging, screen garbage and BSOD.  Only when I’m running Away3D though.

I’m using:
Away3D4 (from Git yesterday)
FP11 RC1 + correct playerglobal (from Adobe yesterday)
XP 32bit
FireFox
HP DV9500 with Nvidia GeForce 8600

Anyone else got this, or am I alone here?

Sounds like a rather severe issue, and is far outside the realm of Away3D. Please file a bug with Adobe. They will probably want to look into this.

Thanks RIchard.  I’m not 100% that my laptop is in best of shape - hasn’t had a rebuild in a year and the graphics cards on these machines are notoriously dodgy, although I’ve only ever heard of complete failure, not something that can be fixed with a reboot - which would indicate I have a display driver/FP11 issue.

I’m backing up now and will rebuild with Win7, but I think I’ll file a bug report nonetheless.  After all - it started just after installing FP11.

Ok, so I’m going to blog all this in this thread as it’s as good a place as any.

I’ve reported the bug to Adobe and rebuilt the machine with Win7.  So that’s new OS, latest drivers from Nvidia, fresh install of Flexbuilder, latest SDK, latest Away3d, the works.

All good until I fired up the 3D app again.  Locked up right away, lots of flickering, then a black screen.  Hit the power switch before anything got worse and rebooted.  Got some sort of mangled 8 bit graphics at 640x480.  Was a bit worried that even the BIOS had yellow stripes on it.  However, an uninstall/reinstall of the graphics card has fixed it for now.

Going to proceed a little carefully and try some demos and the like, then start back with my own code.

Same thing with Delta Strike.  Seems to corrupt the display drivers somehow. Didn’t think Flash player had the capacity to touch the drivers, but there you go.