Frequently Asked Questions
Getting layer-related errors when playing the game
Examples of the errors you might be seeing:
To fix these errors, all you have to do go to the top menu bar in the editor and select RTS Engine -> Configure Demo Layers to import the demo layers.
Getting object null reference errors on start or after I do a certain action in runtime
When getting these errors, there are two possibilities:
- Option 1: The RTS Engine found an issue with your entity prefabs or your configurations in the components. In this case, before any object reference is null error is printed on the console, the RTS Engine prints a RTS Engine error which is always prefixed with RTS Engine then followed with the component that caused the error with the error message usually containing how to fix the error. Go ahead and stop the game, fix the error as per the given instructions and the error should be fixed the next time you launch the game or do the action that triggered it during time.
- Option 2: If the errors you are getting are not preceded with RTS Engine specific errors then please report the error with the full error trace!
The particle effects used in the showcase demo game are missing
The RTS Engine demo uses particle effects from a FREE asset on the store. It is not allowed to include the source files for these particle effects since it is not allowed to redistribute them under a different asset in the store but here is a LINK to download them. Import the asset and all particle effects prefabs will be fixed.
Problems with the cameras using the Universal Rendering Pipeline
Please check the Setup Universal RP guide to see how to properly setup this rendering pipeline in your RTS Engine project with details on how setup the camera stack.
Issues moving units and engaging them with their targets on top of hills with Unity Navmesh
Open the Unity Navmesh Navigation window and in the Bake tab, enable Manual Voxel Size and decrease the value of Voxel Size, rebake the navigation mesh and keep re-iterating until there are no movement and engagement issues for units on top of hills. The lower the voxel size the more accurate the navigation mesh (more accuracy is required when having different heights and hills on your terrain) but make sure that the voxel size is not so low that it affects build time so much.
Unable to extract .UnityPackage when downloaded with Chrome on MacOS
This is a MacOS specific issue when downloading the unitypackage with Chrome. When you extract a .zip file, you do not get the .UnityPackage file that you can import into the Unity editor but instead get its content (a lot of folders with three-file-contents). The solution is to download the .zip files for the modules using Safari on MacOS.