This content has been marked as final. Show 3 replies
from the article:
"Whenever the content earlier to Director 11 is played, Adobe Shockwave
Player needs to understand the version of the content to enable smooth
playback of that content. For this purpose a new and efficient approach is
They either mean it's efficient for them or there is a different definition
for the word efficient than I'm used to.
not only that but I have some Dir 8.5 sw3d content content that when run under shockwave 11 (playerVersion=11) it uses a different coordinate system than the one specified by the w3d used in the scene thereby throwing off all the camera position calculations. Im not sure that the ScriptExecutionStyle declaration functions any longer. I dont think its in anyones interest to have to retool old content for a new player, it is a sign of lassitude on the part of Adobe for this complicated and incompatible solution. I would have preferred they waited another 6 months instead of releasing a bug filled player. The fact is. not everyone has moved on to Vista and Intel Macs,
Microsoft Confirms Vista Adoption at 2%
SO far I have not even found a system (MAC or PC) where the compatibility operation actually succeeds. The plugin simply goes to a screen where it says the compatibility components are downloading and then just hangs. THis is historically the first release of shockwave that I recall where an update actually breaks so much prior contentcompletely. Setting the playerVersion=10 pretty much guarantees a hanging request for compatibility components that dont appear to exist/never download and playing the content as sw11 introduces so many bugs that 3d content is unplayable.
This of course makes it impossible to adopt the new sw11 platform for authoring. However content authored in Dir MX (version 10) is compatible with plugin version 9.0.0.034
Macromedia left quite a high standard on compatibilty issues that Adobe seems to fall severely short of the mark on. I guess we know what to expect from here on out.