History

Wiki-home » About VastPark » Troubleshooting »

Diagnosing Client problems

Application fails to start

If any of the applications fail to start you should first check that your PC meets the minimum requirements.

Viewing Player Crashlogs

The Player writes crashlog information to text files at this path:

%USERPROFILE%\Local Settings\Application Data\VastPark\v1.5\Player\log\

You can visit this path by clicking on Start and then going to run (or hold down Windows Key + R). Paste the path in and hit enter.

If you see files named crash_<some number>.txt something is causing the application to crash. These crashlogs contain diagnostic information and can be analyzed to determine the cause of the crash.

Application fails to successfully download all the elements

If you are on a broadband connection and the world doesn't load and the queue doesn't progress for more than a few minutes then there is some sort of issue.

Diagnosing download issues:

There is a Debug Dialog window that you can get more information from. You can bring it up in the Player by going to Tools > Debug. This opens on the Load Queue by default. You'll also see any errors logged to the lower window by default. It's a great idea to open this prior to accessing the world you are having problems accessing/downloading.

When you tell the Player to go to a world, the Load Queue will fill with a list of items it needs to download. If you don't see green downloading bars actually progressing through these assets then you probably don't have access to the assets. I will ask the team to add information on where these are stored and give you a path so you can check with a browser on the same server.