Platform Tutorial Trying Out Your World
From Multiverse
Now that you have created your world's terrain and added some objects to the world, you are ready to actually test out your world. To do this, you must set the world file to the new world file you created and then create an asset repository containing all the 3D asset files (meshes, materials, textures, and so on) that your world requires.
Set the world file and copy scripts
This is the easy part. In order for your tutorialworld to work properly you need to copy ALL the .py files from the mv_home/config/sampleworld folder into your mv_home/config/tutorialworld folder. If you don't you may find that you recieve "Internal error" or "No default instance" errors when the client trys to connect with your server.
Next, you must point your server at the new world file you created with World Editor.
- Stop the servers if they are running.
- Edit your properties file. Change multiverse.worldname to "tutorialworld". The server uses this property to determine which world file to load. Make sure you have saved your world (.mvw) file to the
mv_home/config/tutorialworlddirectory. This directory should also contain a file namedvillage.mwc(a World Editor collection file). - Start the Multiverse servers, as you did previously in Verify your installation.
Edit the client world settings file
Now, edit the world settings file, client_home\world_settings.xml and change the world ID from "sampleworld" to "tutorialworld":
<loopback_world_response world_id="tutorialworld">
Now, the client will store all assets it downloads in the client_home\tutorialworld directory.
Enter your world
Start the Multiverse Client again:
cd client_home\bin MultiverseClient --development --world localhost
You will be able to walk around in the world you created with the World Editor.
When you are done, press Alt-F4 to exit the client.
