Test Run

From Tygron Support wiki
Revision as of 09:33, 13 August 2015 by Joris@tygron.com (talk | contribs) (Created page with "==Test run== The "Start Testrun" button allows you to test the game. When the button is pressed, the game is started. In the Virtual 3D World, you will experience...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Test run

The "Start Testrun" button allows you to test the game. When the button is pressed, the game is started. In the Virtual 3D World, you will experience the game from the perspective of the stakeholder you have selected in the editor menu bar. The game starts from the point where the players has just passed all the starting screens and is presented with the 3D environment for the first time. The cinematic at the start of the game is displayed, and afterwards all actions can be taken as though you are actually playing the game.

You can switch between stakeholders by using the "Switch Stakeholder" dropdown menu in the editor menu bar. When you switch stakeholder, you will notice the interface in the Virtual 3D World panel changing, most notably the actions on the left of the panel and the indicators at the top. You can only switch to a stakeholder that is not yet seletected by another user. when a user switches stakeholder, the original stakeholder is again available for selection.

To stop the testrun, press the button in the editor menu bar again, now labeled "Stop Testrun".

Note that it's also possible to start a testrun by directly taking an action, without pressing the "Start Testrun" button. When doing so, the flythrough at the beginning is skipped. The testrun can still be stopped in the same way, by pressing the "Stop Testrun" button.

When a testrun is started, all editing is temporarily suspended. Although the editor will remain active, all editing panels will be temporarily disabled. Most options in the editor menu bar will be greyed out as well. This holds true for all editing users, meaning that when you start a testrun, no user can edit until the testrun is stopped.

When a testrun is started, no other user can edit for the duration of the testrun. Editing can continue when the testrun is stopped.