Skip to content
English - United States
  • There are no suggestions because the search field is empty.

[TR] 3.5 How to resolve common crashes in Lumion

[TR] 3.5 How to resolve common crashes in Lumion

1. What is a crash?

A crash refers to Lumion crashing to the Desktop (with or without errors).

Make sure to ask the customer to confirm that it’s a ‘proper’ crash and not the two other situations below.

A crash does not refer to the PC becoming slow/unresponsive while rendering.

This issue is discussed in the following article:

A crash also does not mean that the PC restarts while rendering.

This issue is discussed in the following Knowledge Base article:

2. Common causes of crashes

2.1: Crash while importing a model.

  • Cause: Lack of memory / imported model is too detailed for the available hardware.

Diagnosis: Ask the customer to upload the model file and the original CAD file if applicable, so you can check if it also causes a crash on your PC. If it takes ages to import the file or if it makes Lumion crash, it almost always means that the model is too detailed for the available hardware.

Solution: Advise the customer to follow the instructions in the following article:

2.2: Crash while assigning a 3D Grass Material to a surface.

  • Cause 1: A 3D Grass Material was assigned to too big a surface.

Diagnosis: Ask the customer about the grass and/or get them to upload the .LS Project file.

Solution: Advise the customer to follow the instructions in the following article:

  • Cause 2: Some AMD Radeon 6800 graphics cards have an issue with 3D Grass and cause Lumion to crash when the Material is assigned or rendered.

Diagnosis: Ask the user to provide a Diagnostics Report and their Project file. Check if they are using 3D Grass and have one of those graphics cards.

Solution: Advise the customer to install the latest AMD graphics card driver. If the problem persists, the only other option is to follow the instructions in the following article:

2.3: Crash while editing a Project, placing Objects, etc.

  • Cause: The graphics card or other components might be overheating or overclocked.

Diagnosis: Ask the customer to follow the instructions in the following article:

Solution: If the HWInfo report shows that some readings exceed nominal temperature/clock frequency values for the CPU, graphics card and RAM just before the crash, tell the customer to check the cooling system or disable overclocking for the relevant components depending on the cause of the problem.

2.4: Crash while rendering:

  • Cause 1: The graphics card does not meet the minimum requirements.

Diagnosis: Ask the customer to provide a Diagnostics Report:

Solution: Check if the graphics card meets the system requirements.

  • Cause 2: The latest graphics card driver and all available Windows updates have not been installed.

Diagnosis: Ask the customer to provide a Diagnostics Report:

Solution: Check if Windows is up to date and that the latest graphics card driver is installed:

  • Cause 3: 3D Grass Materials are assigned to too big surfaces.

Diagnosis: Ask the customer about the grass and/or get them to upload the .LS Scene file.

Solution: Advise the customer to follow the instructions in the following article:

  • Cause 4: The graphics card or other components might be overheating or overclocked.

Diagnosis: Ask the customer to follow the instructions in the following article:

Solution: If the HWInfo report shows that some readings exceed nominal temperature/clock frequency values for the CPU, graphics card and RAM just before the crash, tell the customer to check the cooling system or disable overclocking for the relevant components depending on the cause of the problem.

  • Cause 5: The Project is too complex for the user's hardware

Diagnosis: Ask the customer to provide a Diagnostics Report and their Project file.

Solution: If you see in the report that the graphics card is not suitable for the level of complexity of their Project, advise them to follow the instructions in the following article:

2.5: Crash while saving or loading an .LS Project file.

  • Causes: Lack of memory, insufficient disk space or other factors.

Diagnosis: Ask the customer to let you know which of the factors in section 1 and 2 that apply to their situation:

Solution: If the customer confirms that one or more of the factors in the article apply, the instructions in section 2 in the article should prevent crashes from occurring again in the future.

 

==========================================

ARTICLE SUPPORT (from transfer to HubSpot):

1. Tables:

Tables were not able to be imported via HubSpot Importer. Any Tables in this article are now based on a DIV Conversion. Same is also the case for the transfer of articles with tables in the EKB.

You can add new (basic) Tables in the HubSpot Editor directly.

If the layout does not work, then you can copy/paste or recreate the old Table from ZD. Where possible the Table has also been copy/pasted from the source page (see link below in 3.). Instructions, see this article: Copying an old Zendesk Table over to HubSpot

2. Finding the reference to the old Zendesk Ticket in HubSpot:

Use this Support article:  Finding the reference to the old Zendesk Ticket in HubSpot

and for ZD ticket Search in HubSpot following step 1 in above article:

3. Source Zendesk article:

A source and backup copy was made of all articles 9 June 2025.

The saved HTML files and images are in subfolders of: HTML files and images subfolders.

See also Support article in 2 above.

Backup/copy article: [TR] 3.5 How to resolv... (360018671080).html

4: Quick Link to Zendesk IKB article:

(not available when Zendesk closed)

[TR] 3.5 How to resolve common crashes in Lumion