VastPark Player requires the Microsoft .Net (v3.5 or above) to be installed. If your Windows computer needs updating you can get the .Net download here (A one time download from Microsoft). You need to be running Direct X 9c or above. The need for Direct X and .Net will be removed later in 2010. There is currently no Mac version available. This will also be addressed in 2010.

NOTE: If you have a previous version of the VastPark Player prior to v1.1, you must uninstall it before installing v1.3.

Follow these steps to get started:

1. Install	2. Launch	3. Sign up
Download the VastPark Player Click the Download link and start the process by clicking Run. This will start the installation process, then follow the simple instructions. (The image above is from Internet Explorer 7. Your browser may appear different from this screenshot)	Launch the Player Now you have installed the VastPark Player you are ready to launch the Player. Simply double click on the Player icon on your desktop. If this is the first time you have run the Player in this session, it may take extra time to start.	Register as a User to begin! Once the Player is running, you will be invited to login using a VastPark ID. If you have not registered, click on "New user? Sign up here". It's a simple process. You can also choose to enter as a guest and log in later. You are now ready to access worlds using the VastPark Player.

Notes:

Though you can enter as a guest without needing to sign up, some worlds will require you to be logged in before you are allowed to enter them.

It is important to know that this is the free version of the software. If you need something not yet included for a project, this can usually be accommodated in the Enterprise edition. If you are having problems, consult the VastPark forums.

Many corporations have a "proxy server". This causes problems for most virtual world platforms because they need real time connections to the virtual world server. The VastPark Player can work behind a proxy server, but you need to know the proxy information and add it to the Player's config file. If that's relevant in your case, you can find a solution described here.

The Player is built upon our open source codebase which is available in our public source code repository.