Does Director 11.5 include compatibility fixes?
CC Chamberlin
Has anyone else had problems recently with legacy Director-based projects suddenly failing for clients? I'm starting to see multiple reports of crashes of Director-based products rolling in from multiple sources. These apps don't check in with servers or anything; they're standalone apps that just play back the embedded content. Nothing has changed on our end of things for literally years, and the only interaction with the system outside the app itself is the use of setPref()/getPref().
I've had two people claim that our apps worked fine under OS X 10.6, but now crash in 10.7. I haven't been able to reproduce it, but I tried another one of our apps on an almost-out-of-the-box Air, and it crashed. And I got two emails today from people having trouble with that same app. Not sure the OS - I've got an email out to them asking - but it sounds like they were Windows-based, since they were asking about video driver and acceleration settings they're supposed to be using, which you generally don't have to fiddle with on Macs.
My boss asked me if fixing this is just a function of upgrading to the new version of Director and republishing. (We're on Director 11.)
So I went and looked at the 11.5 upgrade version comparison, and I'm seeing these interesting features:
* Mac OS X Leopard support (that's two versions back)
* Microsoft Windows Vista support (soon to be two versions back, when Windows 8 drops)
This does not fill me with confidence that the $300 to upgrade would be well-spent, since the only thing we'd use it for is to publish legacy content so it continues to work under new OS environments. If it doesn't fix the problem, it's money down the hole.
Anyone have any insight and suggestions? Similar issues? After over 2 years of no problem reports, it's pretty odd to be suddenly getting all these show-stopping crash reports on apps that we published back in April 2009 and September 2008!
CC