This introductory tutorial to Ürban PAD will help you get a basic understanding of how the software works. Knowing your way around the Editors and City Designer will allow you get to the most out of Ürban PAD.
Using the Ocean Isle tutorial parcels included with the Ocean Isle city project, you will:
A current version of the Ocean Isle city project is available for download from the following locations:
Highlights of this tutorial include:
To start using the tutorials in your trial version:
Next, return to the workspace by clicking Edit Mode in the Modes window. Open the Layers window. This will bring up the semantic description of the parcel, or activity template.
Now, let’s look at some of the ways Parcel Editor operations create visual diversity in the Diner parcel.
Using a Rectangular Filler Expanding Policy, one of the Expanding Policies, is an easy way to fill spaces in parcels with objects, textures, or other parcel links. This is useful when you want to quickly create a visually uniform area and save time in manual placement.
We can see how this works by clicking the Layers Window and right-clicking on the parking_lot line. Select Edit to bring up the properties of this sub parcel.
There is one child object under the sub parcel: parcel_link_cars:
As discussed on the Expanding Policies page, the sub parcel is given a Rectangular Filler Expanding Policy. Child Index 1 is selected, since the sub parcel will be filled with parcel_link_cars:
Data is composable in Ürban PAD. Individual meshes, textures, and decals, as well as full parcel templates, can be re-used and incorporated into other parcel templates.
This parcel link parcel_link_cars was created as a separate parcel, cars.gcf. As you can see in the following diagram, a Select Expanding Policy was added to the parcel, and eight different colored cars were added:
As we saw in Expanding Policies, we can expect that adding a Select Expanding Policy will randomize the selection of a different colored car at each instanciation.
If we define a Rectangular Filler Policy filled with parcel_link_cars, we can expect that the parking lot (gray texture) will be filled with separate instanciations of the cars.gcf parcel. Rather than placing each car manually, we have used a one-step operation to automatically fill the parking lot with randomized content.
The appearance of the parking lot therefore varies from instanciation to instanciation. Here, using Select Expanding Policy and Rectangular Filler Policy has added variety to the look of the parcel.
Using context and tags is an easy way to perform a complicated task: changing the global appearance of an activity template with a touch of a button. This feature is useful when you want to globally change the appearance of an area. This could be necessary, for example, when you want to show the same city under daytime and nighttime conditions.
Let’s take a closer look at how this works in the Diner activity template.
As you see in the images above, the cars and tables are absent from several of the screenshots. Notice that when they are present, they are present together. Likewise, when one of them is missing, the other is absent, too.
The explanation is simple: we have designed the Diner to change its appearance according to opening and closing times. When the diner is “open,” the cars and exterior tables are present. When the diner is “closed,” the tables and cars are absent.
How does this simulator “know” when the Diner is open and when it is closed?
The explanation is simple: you can create context by adding a semantic tag to an object. When the activity template is regenerated, the simulator chooses between the tag values that you define and applies that tag to the template display.
We can see how this works by clicking the Layers Window and right-clicking on the parking_lot link. Select Edit to bring up the properties of this sub parcel.
You see here that a String Tag Value Policy has been defined as an Existence Policy for parcel_filler_parking.
This String Tag Value Policy has been defined through the ntextgen. The name of the tag used here is opening hours and has two values:
These values set context for the activity template. Object existence will vary with the application of these values.
Here, the opening time value means that the cars in parking_lot_filler will be present when the opening_time context is selected by the Context Generator and applied to the activity parcel.
We have set the same opening_time value for the tables, meaning that they will be present when this context value is applied to the parcel template.
By setting these tag values, we can create the appearance of an open Diner during opening time, and a closed diner during closing time by specifying that cars and tables will be present only during opening time.
These values can be applied globally through the City Project Settings option in the Properties window.
A short tutorial for creating a string tag, using opening_hours as an example:
You can check which context value(s) apply at a given regeneration of your parcel by clicking the sun-and-cloud context icon tab at the top of the screen:
A small window will appear at the bottom of the screen showing the current context value.
You may also click the red Error triangle to get a full report of which objects were not placed in the current regeneration. This is useful when a parcel contains many context tags, or when you want a report of placement problems unrelated to context: