Fantasy Adventure Environment Documentation

Fantasy Adventure Environment
Author: jonathan
Version: 1.3.1
Dated: 30 May 2017

Troubleshooting #

Unity 2018+ Substance errors

A separate version of the package was submitted for Unity 2018.1 and newer. Re-download and import the package from the Asset Store to grab this version-specific package.

Console errors and warnings related to Substance materials

Since Unity 2018.1 support for Substance materials has been removed. In Unity 2017.3 and 2017.4, related warnings will be shown in the console.

These warnings are completely harmless, and unfortunately not something I can circumvent.

All tree models are Unity asset files, how can I get the FBX files?

The trees were post-processed in Unity to bake in wind information. You can use the Unity FBX Exporter (also available through the Package Manager in Unity 2018.3+) to export the models.

Trees and vegetation turn white and orange in Unity 2017.1 (and newer)

 

 

 

 

 

 

 

 

 

A separate version of the package was submitted for Unity 2017.1, because the shaders require some modification to work. To elevate this issue, re-download the package from the Asset Store in your new Unity version.

Only re-importing the shaders is sufficient!

Shader console warnings

Automatically setting target of LOD_FADE_CROSSFADE to 3.0

This warning automatically occurs when a shader uses LOD crossfading in Unity 2017.1+. This is unfortunately not a something that can be circumvented, but is completely harmless.

GLSL compilation errors on MacOS using Unity 2018.1

This is a Unity bug regarding the internal LOD crossfading shader code. These errors only occur in this Unity version, and only when using Forward rendering. This has meanwhile been fixed in Unity 2018.2.

Lightmapping

You might experience some issues with lightmaps, such as black spots. Though, this is not directly attributed to the asset. Since LOD1 and up do not support lightmaps, but are rather lit by light probes you may notice visible popping.

All assets have been optimized for lightmaps since version 1.2.1

Grass is grey

This means the grass material wants to use a pigment map, but there is none available.

Adding the PigmentmapGenerator script to your terrain will elevate this.

If you don’t wish to use this functionality, turn down the “PigmentmapInfluence” parameter on the grass material.

Shadow disappear when camera moves around

This is a general issue with Occlusion Culling, you may have moved things around a lot and will have to re-bake Occlusion for your scene. Baking your scene with a lower “Smallest Occluder” value may solve this.

Object appear completely black

This was a shader issue attributed to OSX or DirectX 9, which has been fixed since version 1.0.3

Suggest edit
Last updated on August 14, 2019
1 of 1 users found this section helpful
Suggest Edit