Compatibility Issues

Revision as of 03:05, 21 October 2019 by MattKC (talk | contribs)

LEGO Island was written in 1997 for Microsoft Windows 95. Since then, Windows has gone through several changes, many of which have broken the dated LEGO Island code. This is a list of known compatibility issues running LEGO Island on modern versions of Windows.

Save files don't actually save

Affects: Windows Vista+

Description: LEGO Island saves files into its install directory, which is C:\Program Files\LEGO Island by default. While it was not uncommon at the time to use the install directory for application data, it quickly became bad practice due to security risks. As of Windows Vista, administrator privileges are required to write files anywhere in C:\Program Files, which breaks LEGO Island's saving function.

Solutions:

  • Run LEGO Island as administrator (right click > Run as Administrator)
  • Use LEGO Island Rebuilder, which has an option to redirect save data to `%APPDATA%` (the modern day standard location for application data)
  • Re-install LEGO Island somewhere with full write access (i.e. not C:\Program Files)
  • Manually redirect saves to a writable location in the registry (September build only):
    • 32-bit: HKLM\Software\Mindscape\LEGO Island\savepath
    • 64-bit: HKLM\Software\WOW6432Node\Mindscape\LEGO Island\savepath

General instability, graphical glitches, driving scenes unplayable, etc.

Affects: Most versions of Windows 10

Description: LEGO Island was written around a very old version of DirectDraw, including a retained mode API (D3DRM) that is not only unsupported now, it's also been dropped from Windows/DirectX entirely. Many of its DirectDraw function calls are obsolete, deprecated and/or completely abandoned now.

Solutions:

  • Change to a software mode in the LEGO Island configuration (Ramp Emulation, RGB Emulation, MMX Emulation, Direct3D HEL). These use CPU/software rather than GPU/hardware (theoretically slower, but imperceptible on modern PCs), so hardware/DirectX API differences aren't so impactful.
  • Use dgVoodoo. This wraps several old DirectX API calls to modern DirectX 11 calls, fixing a huge amount of compatibility issues with modern software and hardware.

Textures are heavily glitched

Affects: Windows 10 1809+ (October 2018 aka "October Update")

Description: When using "Ramp Emulation" mode, all 3D textures are heavily glitched. Bitmaps remain normal:

 

This is a DirectX incompatibility introduced in Windows 10 1809. The exact cause is unclear.

Solutions:

  • Use "RGB Emulation". This mode is unaffected.
  • Use "Direct3D HAL" with dgVoodoo (full screen only). Direct3D HAL is unaffected in general, but has its own compatibility issues on Windows 10 without using dgVoodoo.
  • Use a version of Windows earlier than Windows 10 1809.