Open_Tutorials.cmdscript in the Apparance directory. All the instructions you need are embedded as notes within the actual tutorial procedures.
- Tutorials - Intro to finding your way round the editor and some basic procedure authoring
- Walk-throughs - Guides you through a few quick starting places to explore
- Directory Structure - Where all the files live and what they are for
- Projects - How procedures are organised
- Launching The Editor - Editing environment where all the magic happens
- Launching The Player - Standalone player for flying round procedural scenes
- New Project - How to set up a new (empty) project
A project specifically for learning the basics of the editor and procedure creation has been included to get you going. It is recommended that you start here to familiarise yourself with a few basic controls and concepts before diving into the examples and tweaking procedures.
Open_Tutorials launch script to get started.
To get stuck in, here are a quick list of steps to get you in and viewing the Future City demo.
- Launch the editor with the
- It should open on the main
City.Future Cityprocedure, and the scene 'rez-ing up' in the 3D view
- Press Space to switch to the large preview window
- Use Right to look around the 3D view, and WASD to explore the city. Additionally Wheel can be used to adjust movement speed.
- If you want to try another city, change the
Variation#property in the property panel to a new value (The
City.Future Cityprocedure must still be selected for this option to appear)
To have a play with the web-site generation project try the following:
- Launch the editor with the
Site.Homepageprocedure should be open and have been run ('viewed').
- Go to the directory you ran the editor from and navigate to the
- Open the
index.htmfile in your browser to view the generated page.
Site.*and accept the prompt. This will run all 13 procedures after each edit or F5 run.
If you'd like to have the procedures run when you edit the source markdown files (e.g.
Data\Web Site\content\pages\about\about.txt) then you need to point the watch folder at
There are lots of test and example procedures collected over the development of Apparance available for exploring in the 'Dev Procedures' project. Here's a quick guide to some of them:
- Launch the editor with the
- It should open with the Crate procedure open in the editor panel and the Test Crates scene appearing in the 3D view.
- To view each of the suggested procedures below, select them in the Procedure Browser on the left hand side and click the View button at the TOP LEFT of the UI.
Art.Main- A reproduction of an art installation at a sculpture park
City.City- An old test city populated with skyscrapers
Crate.Test- The wooden crate test scene (view
test.Crateto play with a single crate)
Dungeon.Main- Room connectivity and sub-division experiments
Fable._Demo Pages- Old house in the style of a popular RPG game (click on the Design# property slider track to generate new houses).
Fractal.Main- A few fractal constructions (double click the Main procedure and rewire the output to select between Cantor Dust, Hilbert Curve, and Menger Sponge).
Fractals.Main- A dynamic detail version of the Menger Sponge. The closer you get, the more it recurses.
Graphing.Main- Playing with line drawing and recursion to graph a function
House.Main- Early house test, with manual detail control parameter
Landscape.Main- Early landscape test, manual detail control
Line Art.Main- Triangle line fills, example of re-use and recursion
Office.Main- Modelling test-case, the office desks we used to have at Lionhead
Scaffolding.Main- Stage trussing components
Skyscraper.Main- More early skyscraper tests, assorted parameters to play with
Space Ship.Main- Testing space-ship surface panels, in tower form. Change seed for new version.
Street.Testbed- Early street test, manual detail control
Tests.Columns- Simple row of columns, iteration test
Tests.Cube Array- A simple iteration example used in the Apparance docs.
Tests.Panel Tests- Recursive subdivision of a flat surface to provide detail
Tests.Sphere Tests- An egg
Tests.Stacking- The stacking example used in the Apparance docs.
Tests.Test Noise- Testing noise distortion operator
Tree.Main- Early tree experiment, change seed for new tree
- Data Folder - Where the procedures live, grouped into project folders.
- Bin Folder - Executable programs, editor and supporting libraries.
- 3rdParty Folder - External utilities, sometimes used by Apparance
- Launch Scripts - Shortcuts to a few projects
Procedures are segregated into Projects, each with its own sub-folder in the Data folder. You can only work on one project at a time, specified on the command line with the
Launching The Editor
There are a number of launch scripts that can be used to get started, or you can create a short-cut and add your own command line parameters to select project. Running the editor will start the Apparance engine, open the main UI, load all the projects procedures and restore the last procedures you were editing and viewing ready to carry on.
Open_Tutorials- Some basic tutorials to follow within the editing environment
Open_Examples- A collection of procedures and tests accumulated during development
Open_Future_City- The main technical demo, a large futuristic city
Open_Web_Site- The procedures set up to build this website
Open_Guildford_Game_Jam_2016- The game-jam entry 'Two Choices' game
Open_Birthday_Cake- A bit of fun with procedural cakes
Open_Christmas- Playing with snowy landscapes for a greetings card
Open_New_Project- An empty project if you want to start a-fresh
Launching The Player
There is a stand-alone version of Apparance for exploring procedural scenes without all the editing functionality. There are a few launch scripts to get you started.
Play_Future_City- Explore the main technical demo, full-screen.
Play_Guildford_Game_Jam_2016- Play the game-jam game 'Two Choices', full-screen.
Play_Examples- View the Crates test scene, full-screen.
Play_Christmas- Explore the snowy landscape greetings card scene, full-screen.
To create a new (empty) project, take a copy of the
New Project folder and give it a new name. This can then be opened in the editor using the
-project="My Project" command-line parameter.
If you want to 'import' procedures from another project, you can do this, but it is currently a manual process and prone to problems. At the moment, there isn't an easy way to trace any dependencies between procedures so it's likely you will miss one.
log.txtnext to the executable) though.