# Known issues and limitations

There are always cases where things does not work quite as expected, issues or limitations caused by various reasons. We'll try to list common known issues and limitations below to make users aware of the issue and possible workarounds.

# Simplygon and Bump-maps

There are cases of where materials utilize bump maps (grayscale textures) for detail preservation. It is not uncommon that these textures get sent through Simplygon's NormalCaster as if they were normal maps. The baked normal map will in this case not be correct, neither as a normal map or bump map.

The reason for this is that Simplygon simply does not support bump maps. A NormalCaster always expects a normal map where each pixel (in use) is a valid normal, this is not the case for bump maps. When a bump map is sent to a NormalCaster each pixel will be treated as a normal, and incorrectly get transfer to a normal map (incl. correction of the reduced surface).

Bump maps can be baked using a ColorCaster, but with the limitation that the baked texture will not include compensation of reduced geometry (less accurate).

# sgsdk_ExportToFile and sgsdk_ImportFromFile inconsistencies (scripting)

The states (and some mapping data) in the Simplygon Max plug-in are kept until cleared. Some examples are LOD-prefix, texture output directory, shading nodes, material overrides etc. While we are trying to avoid mapping data it is required to preserve things such as original mesh properties, hierarcy, skinning, multi/sub materials and so on. Cleraring mapping data incorrectly may affect the import and the ability to map back original data. To make each export and import consistent, call sgsdk_Reset() and sgsdk_ClearGlobalMappingData() at the beginning of every script (or places that assume default settings).