Troubleshooting common issues

This page lists some common problems that you may run into when using Stingray.

For strategies you can use to get a better idea of what's going on in a running game, see also Ways to get runtime feedback.

Game crashes without errors / crashes at startup

If your game crashes without sending any errors to the Log Console, you are probably running out of memory on your target platform. This is particularly likely if the crashes occur when running on iOS or Android, but not when testing on a Windows PC.

If the crash occurs at startup, the cause is usually that the boot package is attempting to load too many resources into memory. This is likely to happen eventually if your boot package uses wildcards to load in all resources of certain types.

For help, see the list of techniques under Optimize memory usage, and consider setting up multiple resource packages that your project can load and unload dynamically. See Loading and unloading packages.

Objects and materials are missing when running the project, but they show in Test Level

You may need to add your resources to your boot.package file, or to another package that you load into memory yourself during the course of the project. For details on how package loading works, see the topics under Loading and unloading content at runtime.

Fatal error when testing levels

Shut down Stingray and delete the editor.config file. You can find this file at C:\Users\<user name>\AppData\Local\Autodesk\Stingray\Settings\editor.config. When you restart, the problem should be corrected.

General misbehavior

If things aren't working the way you expect, give the following options a try and see if any of them correct the problem.

Common errors and warnings

`Connections: Failed to connect to "PS4". Please ensure the PlayStation 4 engine run-time can be accessed at . Error Invalid DevKit: ``