This file contains information about Director 7.0 not available in the printed manuals. To get the most out of this release, please read this document.
For the most up to date information about Director 7.0, visit our Web site at https://www.adobe.com/products/director.html
When you install to a drive that is not your main hard disk, you will be asked to enter your serial number twice, once when the installer loads and once when Director loads.
If you encounter an "IMLLib not found" error on launching Director, simply make an alias icon in the Director 7 folder and try again. (You may delete the alias.)
If you are running a localized version of Macintosh System 8.0, we recommend upgrading to a localized Macintosh System 8.1 or later before installing Director 7. A possible conflict with older versions of the localized Appearance extension may result when running Macintosh System 8.0.
Installing Director on a machine running Macintosh System 7.0 or later converts the operating system's appearance to the 3-dimensional look of Macintosh System 8.0. To set the system to its previous appearance, open the Appearance control panel (also installed with Director 7), click the Options button, and deselect System-wide platinum appearance.
If AppleScript is missing from active extension and you are installing Director 7 from the CD-ROM, Peak 2.00 LE fails to launch.
The Director 6 and Director 6.5 uninstallers delete the file association information for .dir and .dcr files, as well as hardware key information on Japanese systems. If you uninstall these previous versions after you install Director 7, you must reinstall Director 7 to regain these attributes.
The Director installer requires that a temp folder exists on your system as defined in your system environment. If you receive an Internal Error when trying to launch the installer, be sure you have a temp folder defined. The name of the folder must match what is set in your temp environment variable. Get Properties on "My Computer" to verify the temp variable setting.
On Japanese systems in Windows NT, the installer does not install an International hardware key as a default. You must select this setting.
There are several mistakes in the printed Director 7 tutorial. However, the tutorial in Director Help is correct. You can print a correct version of the tutorial from Director Help or by downloading and printing the corrected tutorial from the Director 7 Documentation Corrections in the Director Developers Center at https://www.adobe.com/products/director.html.
Director no longer utilizes all available system resources while running. You can lower the amount of CPU usage by increasing the idleHandlerPeriod (at the expense of executing idle handlers less frequently). CPU usage increases as the tempo of the movie increases and when extensive animation occurs on the stage. Older movies do not support this feature, so existing Shockwave content (or older movies not updated to Director 7) function as they have in the past.
When Director 6 files are opened, the Save command is available immediately (even if you don't make any changes). Choosing Save opens a warning dialog explaining that your Director 6 (or previous) file will be updated to Director 7 format if you choose to Save.
The fullColorPermit property is obsolete and should not be used; the documentation incorrectly states that older movies authored with this property still work in Director 7.
The example for recordFont in the Changes in Lingo section of Director Help contains an error. This string is missing an argument. It should look like this:
recordFont(mynewmember, "lunar lander", , [14, 18, 45], "lunar lander game high score board first last name")
References to "the media of window" should be changed to "the picture of window."
Lists with a different number of elements compare based on the number of elements; the list with more elements is considered larger than the list with fewer elements.
SendSprite and sendAllSprites returns a value (null) when no handler is invoked.
Points and rects in Director 7 can now contain floating point coordinates.
The Lingo.ini file is now available for Macintosh. The on startUp handler within the Lingo.ini file now gets executed before the message window is created. This means that put commands don't display within the message window as in previous versions. The handler is executing correctly.
A library of behaviors that facilitate the Multi-user Server and Xtra (available only with the Director 7 Studio) is included in the Director 7 Library palette. The library includes a Connection Manager behavior, which is designed to be placed on a "Connect to Server" button sprite. This behavior creates the connection to a Director Multi-user Server and adds itself to the Lingo actorList allowing calls to be made into it by the other Multi-user behaviors at any time in a movie, regardless of whether or not its sprite persists in the score. The remaining behaviors in the library depend on the use of this Connection Manager. They include behaviors for a chat text input field, a chat output field, a field displaying the current members of a chat group, and a "Disconnect" button sprite. Always use this Disconnect behavior with the Connection Manager. The Disconnect behavior calls the Connection Manager's "destroy" method, which removes it and its instance of the Multi-user Xtra from the actorList.
Using Preview in Browser with linked media (individual members or casts) requires the browser to load local files into Shockwave. To provide for this requirement, place the linked media is within a folder named "dswmedia" when you author your movies. If you like, you can put your entire project into a folder named "dswmedia".
Before using Save as Java on the Macintosh, increase the recommended memory partition by at least 8 MB.
Director 7 introduces a new Lingo movie property: the soundDevice. This property is gettable and settable. At startup, available devices are loaded into a Lingo list called the soundDeviceList. This list is a gettable only. There are currently 2 devices available: Macromix and QT3Mix (RSX is no longer supported). Macromix is the basic Director sound mixer and is the default. It exhibits substantial latency when mixing sounds. QT3Mix is a new soundDevice which is within the QT3 Asset Xtra. It is not available no machines without QuickTime 3 or if the QT3 Asset is not installed. It offers much better mixing and allows the soundtracks of QuickTime sprites to mix with other sounds when QuickTime has been assigned to DirectSound (note that Windows NT does not support DirectSound, so other applications cannot share the output device. NT can use QT3Mix by outputting to Wave out)). For smallest latency (fastest sound performance), set the soundDevice = "QT3Mix" in the prepareMovie or startup movie handler. If QuickTime 3 (the system components) or the QT3 Asset Xtra are not available (or not installed), sound playback uses Macromix or, on the Macintosh, the MacSoundManager.
The device priority for the QT3Mix soundDevice is lower than the priority for the Macromix Xtra, causing Macromix to be used unless specified. This causes many existing Shockwave movies to play back with much greater latency under Shockwave 7; setting the QT3Mix priority higher than Macromix improves latency if QT3 is installed.
(Macintosh) The Modify:Movies:Xtras dialog displays a reference to "Macromix.x32". While not used on the Macintosh itself, this Xtra is necessary for playback in Windows. Do not remove this reference.
Using the Import dialog, SWA can now be fully imported or linked to create traditional sound cast members. These cast members have the standard capabilities of other standard sound members. However, they are quite different from SWA members created through the Insert menu, which creates SWA Asset members such as in previous Director and Shockwave releases. SWA specific Lingo only works on these asset members and causes errors if applied to the new imported SWA members.
The Stage comes to the front only if you select it by clicking on its title bar Clicking in the body of the Stage leaves the Stage in the background, as in previous releases. Choosing Window > Stage currently brings the Stage to the front (from the back) or closes it. Moving the Stage by dragging on its title bar does not change the location settings displayed in Movie Properties. The Center option within the General Preference dialog also does not alter the location settings in Movie Properties or within movies.
If you drag the Stage during authoring, the Stage location is not reflected in Movie Properties. In order to reset the Stage to its position as listed in Movie Properties, change the coordinates of the Stage by a single pixel and then change the coordinates back. Simply opening and clicking OK in Movie Properties does not reset or "snap" the Stage back to these settings.
Director 6 .dir files do not stream in Director 7 (.dcr files do stream as expected).
You must select Save and Compact before movies will stream properly.
Casts whose properties are set to preload "Before Frame One" or "After Frame One" may force the bulk of a movie's media to download before it begins to play (in authoring and projectors, but not Shockwave). To avoid this potential conflict altogether, ensure that the Cast is set to preload "As Needed" (the default).
Compressed fonts are not always identical to the fonts they record. For example, the line height of a recorded font may be slightly greater than the original, and the leading may decrease by one. If a small font doesn't look as expected, use the bitmap option.
We recommend updating movies made in a previous version before working with them.
If you receive an "out of memory: must Save or Quit" dialog, a Save is guaranteed only if the movie is a Director 7 movie. If you are editing an older movie, the Save may run out of memory and fail.
The #digitalVideo member type is now reserved for AVI files only. QuickTime videos use a new type, #quickTimeMedia. In movies made with previous versions of Director, replace uses of the term #digitalVideo that apply to QuickTime videos with the new syntax, #quickTimeMedia.
Due to the new dot syntax, periods can no longer be used in Lingo variable names.
The lingo syntax member(X) of castLib Y will generate an error message. Replace it with member(X,Y).
Global variables must be expressly declared as such; if you encounter odd lingo errors in an updated movie, check that you are not depending on an undeclared global.
Director 4 movies must be updated or opened and saved in Director 5 or 6 before they can be opened in Director 7. If you intend to user Director 4 movies as film loops within Director 7, they too must be updated before they are imported into Director 7.
Director 6 does not show sprite colors for text (you must use lingo to verify colors). Director 7 shows the colors for text sprites.
Text that disappears when a movie is updated may have a blend value of 0. Director 6 ignored blend values for text sprites, but Director 7 operates on these values. Similarly, blend with copy ink has the effect of blending a Flash sprite into its background color; if its bgcolor is white, and the blend is 0%, you see just a white square.
Movies authored under Director 6 that used RSX to synchronize multiple sounds playing at once need to use a different sound device, as RSX is no longer supported.
Certain Xtras, such as the custom cursor Xtra, are not supplied with the default Shockwave download. These Xtras are available through the Xtra downloading feature. To enable these Xtras to work locally, drag them to your Shockwave Xtras folder (in Windows: Windows\System\Macromed\Shockwave\Xtras\; on the Macintosh: System Folder:Extensions:Macromedia:Shockwave:Xtras:). More information on Xtra downloading is available in the Director Developers Center at http://www.macromedia.com/support/director.
URLs contained within text cast members are not being inserted into Aftershock-generated HTML as unanchored links. Workaround: use fields that contain URLs.
Performing Transform Bitmap on 32-bit images with embedded alpha causes the result to include masking effects. Workaround: Turn off Use Embedded Alpha within the cast member properties before applying Transform Bitmap.
Animated GIFs which do not have their own global color tables are not supported.
Rendering of animated GIFs may not always work properly if you have both background transparency and blend set for an animated GIF with inherent transparency. Occasionally, with some files, the GIF renders all gray.
Two-frame animated GIFs may fail to animate.
The Behavior Inspector window may not redraw correctly when expanding the panes and resizing.
If a behavior's getPropertyDescriptionList() handler returns a property list that contains a default value of a string with a list-like syntax (such as "[Next Marker Range]" ), a crash may ensue when the parameter dialog is invoked.
Sound-only QuickTime cast members must be Direct-To-Stage; otherwise the sound cuts off prematurely after setting the movieRate.
Some tempo channels do not export as expected. If you have a "wait for cue" setting in your tempo channel during an export to QuickTime, an error message stating, "An unexpected error occurred. Score database exception" appears. This error should read, "Can't export tempo channel settings".
BMP files exported from Director may not open in some image editing applications. Director exports BMP files at the current monitor bit depth. Photoshop, Debabelizer, and some other image-editing applications do not read 16- or 32-bit BMP files. Be sure to check that your monitor is set to 8 or 24 bits before exporting BMP files from Director that you intend to edit in external image editing applications. Both Fireworks and MSPaint open without problems any BMP file exported from Director.
In Windows using Fireworks as an external media editor: When you launch Fireworks as an external editor for bitmap members, a copy of the image is saved in the Windows temp folder until the final changes are saved. When changes are saved, Director grabs the edited image and brings it back into Director. If you are editing an internal bitmap cast member whose file format is not PNG, you must export the file from Fireworks to the Windows temp folder so the changes are adopted by Director. This folder is typically located in your C:\windows\temp folder on Windows 95/98 and in your C:\temp folder on Windows NT but may also be set to a user-defined location on the latter. If you are using a linked cast member, simply export or save the edited image to the location of the linked file. If you are editing an image whose original file format is PNG, simply save the file when you are done editing the image in Fireworks.
On the Macintosh, we do not advise using Fireworks as an external media editor for internal cast members. Members must be linked in order to use Fireworks as an external editor. To save changes made to the linked file, simply export or save the file to the linked file location.
Exporting GIF transparency from Fireworks to Director: When Director imports a Fireworks GIF with transparency, the transparent areas are designated with a single index color. In order to see the transparency on Stage, you need to set the ink mode of that sprite to background transparent and you must set the background color chip of the sprite to the same index color designated by Director as transparent. Another way to see this transparency is to import your bitmap as an animated GIF with its ink mode set to background transparent.
Photoshop cannot parse 16- or 32-bit BMP files. Using Photoshop as an external editor for 16 or 32 bit BMP files in Director fails.
Director 7 does not support external editing of URL-linked media. If you try to launch an external editor for URL-linked media on the Macintosh, the paint window opens. If you attempt this in Windows, you receive an error saying the external editor is not properly configured.
Images containing alpha information that were imported under the standard import option do not retain their alpha if edited in an external editor. Alpha information does not get written to the external editor from Director unless the image file is imported with the import options set to "include original data for editing".
On the Macintosh using System 8.5, users can select an Appearance Theme setting that causes the system to anti-alias text throughout. Selecting this setting can cause onstage field text to inadvertently become anti-aliased.
In rare cases, file size may double on each save even when only minor changes are made, or on save as with no changes. To repair this situation, choose File > Save and Compact.
Save as Shockwave does not compact the .dir file. For best results, choose File > Save and Compact before choosing File> Save as Shockwave.
Long sounds (and looped sounds) aren't cut off when the sound cast property is disabled via Lingo.
The #autoSize scaleMode doesn't accurately render the sprite when it is rotated about a non-center regPoint.
Flash cast members display a script icon in the cast if you open and close a script without entering or changing its contents.
Sounds of Flash cast members may be clipped when previewed in the cast member properties dialog.
Director 4 movies do not import properly in Director 7. If you have problems importing Director movies, be sure that these movies were updated in either Director 5 or Director 6.
Imported SWA requires MIX Services, SWA Import Export Xtra, and the Sound Import Export Xtra for playback. Using imported SWA members in a Shockwave movie causes a download of 3 Xtra packages before the movie can be played.
Director imports only a single alpha channel. If your image contains multiple alpha channels, only the first channel is imported. Director reads the transparent background as the alpha information for images created in Photoshop with both a transparent background and an alpha channel. Director does not merge the transparent background with the alpha layer before importing. If you wish to import the alpha channel information, you must first flatten the image in Photoshop.
If you are having problems importing files from Photoshop, make sure that the files were saved with the compatibility option ON. In Photoshop 4, this preference is labeled "Options: [option] '2.5 Compatibility.'" In Photoshop 5, this option has been re-labeled "File Compatibility: [option] Include composited image with layered files." In both versions, the default for this option is ON.
Very small SWA files imported into Director (such as button clicks) sometimes don't play. Import the original versions of the sounds and let them get compressed by using Save as Shockwave oruse the Insert:Media:Shockwave Audio command to place them as SWA assets instead.
The Library palette may not be able to find linked cast members.
Movies in subdirectories don't open in the Dropdown List behavior.
The Format Numbers behavior generates a syntax error when it calls the on MoneyFormat handler.
If you issue circular sendSprite calls (sending a sendSprite event to a behavior which calls the same sendSprite) the movie will simply stop with no alert.
Sorting very large lists may occasionally cause the movie to stop without an alert.
Mixing the new dot syntax with old-style syntax may produce unexpected results; such expressions as set a.b to 2 andtheList.getAt(1).a = 0 do not function.
Movies cannot be saved if a lingo score recording session is active.
On Windows in 24-bit display mode, "the picture of stage" will not function.
Editable fields and text are not editable in linked movies.
Clicking the stop and rewind buttons in the control panel executes stopMovie handlers in linked movies when the playhead is already in a stopped state.
Moving a URL-linked cast member from one slot to another in the cast may initiate the download of the media.
If the Macintosh is not connected to the network, clicking "download if needed" for an Xtra freezes the system for some time while the computer searches for a network connection.
The frontWindow property returns the most recently opened window, no matter which window is on top.
Attempting to open a movie in a window whose source file is located at an invalid URL may result in a "There was a disk read error" dialog.
Set the memory allocation for the Director Multi-user Server so that the server has RAM equal to the MaxMessageSize in the Multiuser.cfg file times twice the number of expected client connections. The Xtra's MaxMessageSize should be greater than the size of the largest message you plan to send.
If you configure a user control database with a wildcard record in addition to records with specified user names and passwords, users who attempt to log into the server with usernames that match the specified records will not connect to the server, as their password will not match the one specified in the database. Authors should account for this by testing for successful connections and prompting the user to try a different username if the connection is unsuccessful. You may also lessen the odds of this by using uncommon strings as your specified user names.
In Internet Explorer for the Macintosh, postNetText does not function and generates an error dialog. Workaround: use getNetText.
FTP file access may not work in authoring and projectors.
Executing a "go to movie" command that point to an invalid URL may result in the error, "This is not a Director file."
The paint window doesn't read alpha channel data embedded within 32-bit images. This means that 32-bit images that are set to Use Embedded Alpha in their Cast Member Properties dialog can look differently in the paint window than they do on Stage (or in their cast thumbnail). In Director 6 and earlier, alpha information is applied during import, thereby always matching the paint window display to the Stage.
The paint window sometimes takes longer to open than in previous versions of Director.
Occasionally, palette sprites in the score cannot be selected as a whole; only individual frames can be selected.
Color cycling precaution: Be sure to select the color set for cycling. If no colors are selected and color cycling is set in your movie, Director may hang, forcing you to reboot your system.
Color cycling effects in the palette channel are reset on go marker(0); much unwanted flashing results.
The Director palette becomes confused when running simultaneously with Dreamweaver. Sprites on Stage draw in incorrect colors. Workaround: Quit Dreamweaver before authoring in Director.
Paragraph spacing in lines and Center anchor do not work. Background shapes all start one line later than everything else on the slide. Please note this when using slide transitions.
Shape objects in PowerPoint source files will be imported as Flash assets. You will not be able to edit these shapes after importing into Director.
On Japanese systems, the Preview in Browser command does not work when there is a double-byte character included in the path to the HTML document generated by Director 7. Workaround: open the document directly in the browser.
In low memory situations, the browser may not open without an error being posted.
If the system's Temp folder is missing, projectors on Windows NT will report a "cannot find dirdib.drv" error message upon launching.
In Windows, Control-Q no longer quits a projector. Workaround: use Escape or Alt-F4.
Java Applets show no background transparent ink effects--sprites with this effect appear with copy ink.
Macintosh movies with 89 or more characters in the pathname may not convert properly to Java; some necessary classes may not be created.
Macintosh Java applets that contain 4-bit images may hang Netscape 3.
On the Macintosh, many applets fail with class not found errors in Netscape 4.5; in particular, sound fails to play. The problem is not limited to applets made with Director.
A "go next" command sent when the playback head has passed the last marker sends the playback head to the previous marker.
In Netscape on the Macintosh, you may occasionally encounter a "broken icon" instead of a movie when loading a movie locally. To repair this condition, try going into the browser preferences and examine the mime-type mapping. Examination (without actual editing) is enough to force the browser to refresh its mime-type mapping table.
On the Macintosh, if the MacromediaRuntimeLib extension is turned off in the Extensions Manager, Shockwave generates a "One or more Shockwave files are missing" error message on loading.
Future versions of Shockwave may contain a context menu triggered by right-clicking a movie in Windows or control-clicking a movie on the Macintosh. In Director 7.0, this feature is disabled. More information on using the context menu is included in the online documentation.
In Netscape 3.x on the Macintosh, the logo and progress bar remain painted on the screen while playing a movie "full screen" (not wrapped in html).
On Macintosh, files may appear to load slowly into browsers from local disks. For example, if you use preloadNetThing to cache a .dcr and then use gotoNetPage to load it, the movie will take a few moments to appear, almost as if it were downloading from the net. This behavior does not affect playback on the Internet.
When using transitions and on cuePassed together, prematurely exiting frames with transitions, such as with a mouseUp handler, can cause the cuepoints to appear unsynchronized. This is caused by leaving frames with a mouse click before a cuePoint is reached, rather than allowing the on cuePassed handler to precede the movie.
MPEG 3 files cut off several seconds before the end of the file.
Very small sprites may not generate trails properly.
Using FlipH or FlipV and then scaling a sprite with an uncentered regPoint may appear jumpy on playback.
Moving a bitmap over a previously trailed graphic may erase a few pixels more than it should.
When you select File:New:Movie when the current movie has a text, field or button sprite on stage, your new movie stage will show the background or desktop through a hole where that sprite was last drawn.
When you create a projector without checking the "centered" box in the projector options dialog, the projector tries to display the stage at its original coordinates. This was true in Director 6, except that when the projector was played on a system that did not contain those coordinates, it automatically centered the Stage to the main monitor. Director 7 projectors attempt to display the stage outside the screen boundaries; for example, if the projector was set to play on second monitor, it would not appear on a one-monitor system. Workaround: always select "centered" in the projector options dialog.
Compressed fonts preload their media prior to movie playing, significantly increasing the time it takes for the first frame to appear on playback.
Attempting to preload a movie from an invalid URL does not invoke an error message in the authoring environment.
Changing the netThrottleTicks property has no affect on background streaming.
Editable text always displays with copy ink.
RTF text files do not split into separate members at page breaks when imported.
Triple clicking does not select an entire text on the Stage or in any windows.
Under some circumstances, it is possible to get text to render in an incorrect font (sometimes fully incorrect, sometimes just partially). The text (and font) data is not corrupted. You can safely do a "Save As" and restart Director to clear the problems.
Performing a Find And Replace in the script window for a word in all casts visibly flips through each and every script as it searches.
In Internet Explorer on the Macintosh, it is difficult to type or delete text within a text block in field cast members (text members function correctly) during Shockwave playback.
Moveable text sprites with hyperlinks do not show themselves moving to the new location until you release the mouse. Then they snap to the new location.
On Macintosh, text whose backcolor is black cannot be visiblyhighlighted (in other words, the highlight color is also black).
On the Macintosh, a small percentage of PostScript fonts either fail to compress or render incorrectly.
When creating font Xtra on a Macintosh system, the use of fonts with large file sizes, such as Japanese, may cause the application to slow down or to quit. In this case, specify a subset of characters.
We suggest using only 1 compressed font member per source font. We further suggest to use the default names suggested (sourceFontName *) so that you can tell whether a movie already has a compressed font based on a particular source font.
On the Macintosh, thumbnails for font cast members that only include certain characters may not display correctly until memory is purged.
On the Macintosh, characters outside a limited character set are handled differently between fonts -- some show up as box symbols and others as blank spaces.
In Windows, compressed fonts in a .dcr playing in a browser appear available to Director if Director is running at the same time.
Ordered lists are bulletted instead of numbered.
Nested tables not supported. Trying to import them causes unpredictable results.
Table width is not supported, but cell width is. If no explicit cell widths are specified, you can use the margins to adjust left and right sides. Changing the width of the text member adjusts the width of the table.
HTML import from a (possibly veiled) cgi query may cause the application to freeze.
On German Windows systems with traditional German keyboards, certain Alt-Gr characters (like "" and "@") will not appear when typed into a field or text cast member in projectors.
Anti-aliasing is not supported on Korean and Chinese systems.
Some non-compressible Japanese fonts may appear in the insert font dialog. You cannot use compressed versions of these fonts.
On the Macintosh, recording fonts of huge file sizes, such as Japanese, causes Director to slow down or quit.
Windows Korean and Chinese systems: text displayed using a recorded font may not display properly if it is reset to its original font.
Windows Korean and Chinese systems: Compressed versions of double-byte fonts are not supported.
Japanese systems: Missing fonts do not map correctly. When movies contain fonts that are not available on other platforms, text may become mojibake (garbage). Workaround: select the mojibake text and choose the right font after you open the movie.
On the Macintosh, dissolve bits, dissolve bits fast, and dissolve pixels fast transitions are much slower in Movies in a Window than on Stage. Workaround: set your MIAW to a window type that doesn't have a grow box.
On the Macintosh, while a movie is running under System 8.5, the Stage may get layered over any floating windows. Workaround: close and open the Stage or close and reopen the windows.
Changing from 8- to 24-bit display mode may cause the palette to become distorted.
Occasionally small windows can be set to dimmed; if they get to this state, they can only be closed by using their shortcut keystrokes.
Undoing creating a vector leaves a trace of a vector shape in the window and in the cast.
Scaling in the vector window may not effect vector shape sprites that have been scaled or skewed on the Stage.
Vector shapes may have inaccurate loc properties relative to their regPoints when rotated.
When you pull out the second handle from an originally square point, the first handle does not retain its position but locks to a position that is about 60 degrees away from the second handle.
When you first open the vector shape editor and create a shape, the move-to-the-stage, script, and info icons are grayed out and unusable.
The thickness of vectors may change as the vertexList changes.
After autoscrolling while dragging a selection, a shape can get too far off screen to scroll back with the scroll bars. Workaround: close and reopen the window.
On the Macintosh, you must be connected to the Internet before you can select "Download if Needed" for an Xtra in the Modify:Movie:Xtras dialog.
To use Xtra downloading in authoring, you must open the movie with a gotoNetMovie command. Simply opening a movie does not download the necessary Xtras.
Windows ActiveX Xtra: keypress events may not work correctly when an ActiveX sprite is on Stage.
Windows Web Design Effects: Natural Effect does not function on gradient bitmaps.
If you use the third party utility FinderPop on the Macintosh, you see context menus in the Library palette when you click items (normally you should only get a menu by holding down the control key). You should disable this utility's control free context menus within Director. You can do this by selecting the menu item that this utility places at the bottom of the Help menu.
There are minor incompatibilities when the Macintosh utility Kaleidoscope is installed. Some of Director's custom pop-up menus (the ones with small fonts, such as the inks at the bottom of the Paint window) can display slightly flattened.
Windows Intel Xtras are not supported when running under any emulator, such as Virtual PC 2.1.1.
In Windows 16-bit display, NVidia video cards create distortion when bitmaps are zoomed in the paint window.
1995-1998 Macromedia Inc. All rights reserved.