Mesh – Troubleshooting Guide

by Katalin Borszéki and Ákos Karóczkai · updated: 11.17.2016

Cannot change Pet Palette function: Elevate Mesh Ridge Height

Affected version: 17 | Severity: workaround applicable | ID: 167778

{i} Note: This issue was fixed in ARCHICAD 17 build 6004


On the Floor Plan display after using the Elevate Mesh Point Height Pet Palette function to change the “z” height of a mesh ridge, switching to another function by clicking on Cancel is not possible: Pet Palette disappears.


The issue is caused by a recent change of this pet palette option. (In previous Hotfixes this Pet Palette option wasn’t retained after use.)


As a workaround switching to another function of the Pet Palette is possible if a node is selected of the Mesh element.

Degenerated Mesh causes “Memory Full” Message on Floor Plan

Affected version: 17 | Severity: workaround applicable | ID: 160829

{i} Note: This issue was fixed in ARCHICAD 18 release version


While zooming or panning on the Floor Plan you might encounter the “Memory Full” message:

memory full

And when switching to the 3D window you get the “Errors occurred during the last operation” message:

errors occurred during the last operation

These two reports most often come together when there is a Mesh element placed on this Floor Plan that has an invalid geometry that can’t be drawn as a 3D element. The Mesh element is visible on the Floor Plan but disappears from the 3D window. This can either be a Mesh that is self intersecting, has too sharp corners or a surface geometry that can’t be calculated.

How to detect the problematic element(s)

Depending on how many times do you get the “Memory Full!” message after one pan or zoom action you can determine how many corrupt Mesh elements you have in the project.

To be able to find the problematic element(s) first the error report needs to be switched off. This can be done in the Work Environment by turning off the “Write Report” option:

turn off error message with the write report checkbox

The Mesh elements producing this error report are visible in the Floor Plan window but they can’t be generated in the 3D window. Therefore this is not a solution to the problem, just a temporary help to be able to detect the problematic Meshes.

To find the problematic element(s) leave only those layers on which have mesh element(s) then try to compare the 2D and 3D window to see which element is not displayed in the 3D window. Sometimes there are very tiny Mesh elements left over in the project by accident that generate this error. It might help to find the problematic element if you select all Meshes by activating the Mesh Tool and pressing Crtl + A or Cmd + A (Win/Mac). Once you found the element causing the error message you can try fixing it based on the three issue categories below.

Mesh with too complex geometry can’t be triangulated


When a Mesh element has nodes very close to each other with drastic height differences these nodes can’t be connected with lines and the surface triangulation can’t be reached:


The Mesh element needs to be simplified in a way so that  Floor Plan triangulation appears. This can either be done by moving nodes on top of other nodes to lower the amount of tiny triangles or by redrawing the Mesh element with a bit simpler shape.

Mesh with too sharp edges can’t be calculated


If the contour of a Mesh element on the Floor Plan appears to be random or it has too sharp corners, it possibly can’t be calculated:

sharp corner


To resolve the issue either the contour of this Mesh element needs to be changed so it won’t have that sharp corners or the element needs to be remodelled with a different element type, for example with a slab element.

Self intersecting Mesh

Affected version: 17 | Severity: workaround applicable | ID: 160829

{i} Note: This issue was fixed in ARCHICAD 18 release version


When moving one point of a mesh polygon onto another (not adjacent) point of the same polygon, the mesh does not fall into two separate pieces as expected and the “Memory Full” error message  appears.

  • mesh poly points


The algorythm governing this code is planned to be fixed in ARCHICAD18.
In the meantime, it is advisable to avoid moving mesh polygon points on top of one another. If the intended result for the mesh is to be cut into two separate entities, please be aware that modelling them separately is advisable with regards to this issue.

  • Was this Helpful ?
  • 0   ​8