Can you install Lumion on Mac?


Can I install Lumion on my Mac?


1. Can you install Lumion on OSX?

No, Lumion can’t be installed on OSX, and there are no plans to make Lumion available on OSX.

 2. Can you run Lumion in Parallels or VMWare Fusion for OSX?

Parallels and WMWare Fusion for OSX are not supported and will cause crashes, glitches and License Key lock-ups.

3. Can I run Lumion on Mac using Boot Camp?

IMPORTANT: Using Lumion on Macs is not officially supported. Act-3D B.V. provides no warranties on any of the functionality in Lumion and do not accept any liability claims arising from the use of Lumion on Macs. Act-3D B.V. recommends running Lumion on Windows PCs as they can be configured with more powerful hardware than Macs which will make editing and rendering significantly faster.

1.1: To find out if it will work, please double-check that you have got the following:     

  • A relatively new Mac computer with a fast graphics card.
  • The Mac should have an Intel CPU. Apple’s M1 CPU is not compatible.
  • A Windows 10 license.
  • At least 100 GB free hard drive space for Windows 10 & Lumion.
  • Apple’s Bootcamp software for installing Windows 10.
  • The latest driver software for the graphics card (see 1.3 below).

1.2: Please also note that older Macs often do not have very powerful graphics cards and will struggle when running Lumion. Please click here to check if your Macs graphics card is suitable for Lumion.

1.3: In addition, Apple’s Bootcamp drivers for AMD and NVIDIA graphics cards are often outdated, and Lumion 6.5 and newer might not be able to start on a Mac with those drivers. Please verify that you can install the latest official NVIDIA or AMD driver from the AMD or NVIDIA websites before running Lumion on your Mac.

Here is a link to the latest AMD Bootcamp driver

Here is a link to the latest NVIDIA driver:

IMPORTANT: The Bootcamp driver for the iMac Pro (Late 2017) causes performance issues in Lumion and other 3D games/applications. Some iMac Pro owners recommend installing a modified AMD driver from the following website to resolve the problem but we are unable to confirm if that helps or not: