Frequently Asked Questions - Solving Issues
This page covers questions you may have or issues you may encounter.
Grass Meshes dosen't appear
A few steps to help if grass meshes dosen't appear.
Ensure that your engine's scalability settings aren't set to the lowest for the Foliage section.
Make sure the Instance's NO-GRASS mode isn't enabled or that the faulty Sub-Layer's o grass debug feature isn't enabled.
Building the Landscape data can help.
In case of big World Partition worlds, entering "grass.FlushCache" in the console made the foliage (re)appear. Even if the landscape isn't big or using WP, this command can also solve issues.
My compiled project dosen't start
Before packaging a project using PANORA|make, be sure to have at least one C++ class ! You can create a blank one if you don't have any.
If you don't have one, you project won't start !
I get a long message when opening the project saying that elements dosen't exist anymore in the builder component
Reinstall the plugin.
The Builder takes a very long time to toggle switches/react to changes
There are a lot of causes that can affect the editing speed; toggling switches causes the builder to recompile a big part of the Instance for example.
The size of your terrain, number of layers used, Instance type (a Single instance is much lighter than a Multi Instance), using World Partition or not and of course specs of your computer can all affect the reactivity of editing.
The Builder takes a long time to open
This can be due to the amount of materials and textures the builder has to take into account when opening. Try to tweak the paths of the assets used in the Builder Settings.
Last updated