1.3 Requirements

This plugin requires at least Hollywood 6.0 since it uses the display and bitmap adapter APIs introduced with Hollywood 6.0. Some features, however, require newer Hollywood versions. Here's an overview of the features only available with newer Hollywood versions:

• – Unicode support: requires Hollywood 7
• – Support for VanillaKey and OnDropFile event handler: requires Hollywood 7
• – Support for OnRawKey event handler: requires Hollywood 7.1
• – Support for menus: requires Hollywood 9
• – Support for Plananarama's special palette mode: requires Hollywood 9
• – Hardware sprite support: requires Hollywood 9

The following optional components might be required as well:

• – guigfx.library and render.library: These two libraries are required when the PaletteMode tag in the @REQUIRE call has been set to False (which is also the default). In that case, Plananarama will remap all graphics to the current screen's palette. This is done using guigfx.library and render.library. If you set PaletteMode to True, however, Plananarama won't require guigfx.library and render.library because graphics won't be remapped to the screen palette but all graphics will be drawn using the screen's pens.

  Note that render.library is available in two flavours: There is a v40 and a v30 branch. It is recommended to use the latest version of the v30 branch because all the v40 versions are C ports of the v30 branch versions which are all written in 68k assembler. The assembler version (= v30 branch) of render.library is much faster than the C version which is why you might want to use the assembler version instead. The latest assembler version of render.library is v32.0. So if you care about performance you should use this one. Also, the v40 branch of render.library requires an FPU which is another reason to use the latest version from the v32 branch instead.

• – FBlit: When the PaletteMode tag in the @REQUIRE call has been set to False (which is also the default), it is highly recommended to use FBlit because otherwise your chip memory will be gone in no time and Hollywood will run out of memory. So make sure you install FBlit first and you add Hollywood to its "Include" list in the "FAllocBitMap" tab. If Hollywood is included in this list, it will be able to place graphics in fast memory which is absolutely needed since 2 MB of chip memory certainly won't be enough for Hollywood. Using FBlit also has the advantage that Hollywood can use the CPU for blitting which is much faster than the blitter on higher 68k CPUs or WinUAE anyway. If PaletteMode is set to True, FBlit isn't necessary because Hollywood can store its graphics data in fast memory. In that case, however, you might want to use BlazeWCP (see below).

• – BlazeWCP: When the PaletteMode tag in the @REQUIRE call has been set to True, Hollywood will store all graphics in fast memory and draw them using the WriteChunkyPixels() command from graphics.library. WriteChunkyPixels(), however, is very slow on OS3.1-3.9 so you might want to use BlazeWCP from Aminet to speed up things. Rumour has it that the implementation of WriteChunkyPixels() in the new classic AmigaOS releases by Hyperion (3.1.4 and up) has seen some optimizations so BlazeWCP might not be necessary on 3.1.4 and up any longer but I haven't done any benchmarks so I can't tell whether BlazeWCP is still necessary with the classic AmigaOS releases by Hyperion. It's definitely recommended with classic AmigaOS 3.1, 3.5 and 3.9.