3DNature

3D Landscape Design & Visualization Software published and supported by AlphaPixel

Menu
A topographic map with green, orange, and gray elevations. A crosshair marks a central location.
Getting Started with VNS 3: Terrain Basics

Part 3B. Tiling & Layers

1. After data import is complete, save the project and go to the Render Task Mode. Open the YNP Camera and rename it Main.

Screenshot of the Camera Editor - Main window, showing settings for the camera. Includes sections for name, floating option, camera type (targeted, non-targeted, planimetric), and a message about hidden controls.

2. Use Edit Next on the editor titlebar to move to the YNP Planimetric camera and rename it Plan.

Screenshot of a Camera Editor window with tabs like General, Lens, and others. The Name field is being typed with "Plan" and options for camera type include Targeted and Planimetric.

3. Open the Main view, Plan view, and Database Editor.

A computer screen displaying Visual Nature Studio software with terrain modeling tools on the left and a 3D terrain map in progress on the right. Various control panels and settings are visible.

4. Open the Plan Camera View Preferences to the Terrain page and check the Terrain Polygon Edges box.

A software settings window labeled "View Preferences 1 (Island Planimetric)" with options for Terrain, including Control Points, Reference Grid, Active Object, DEM Edges, and more, with various checkboxes.

5. Use the + key or mouse scroll wheel to zoom into the wireframe representation of the 3D terrain surface. It’s a grid of regularly spaced georeferenced points, each with an elevation.

A computer screen displaying a grid with a triangle at its center, under the window titled "Island Planimetric." Several tool icons are at the top-right corner.

6. Go to the Database Editor. Along with its new look and tabular organization, you can undock and expand the window. You’ll need to resize it again before docking it. Turn to the Extent page. Slide right to the NS Grid and EW Grid columns. The grid size is 10 m by 10 m. 10-meter DEMs are sometimes referred to as having a 10-meter resolution. At render time, grid cells are divided into triangular polygons. The degree of polygon subdivision is determined by the Maximum Fractal Depth. The Plan grid with the square cells divided into 2 triangles represents a Maximum Fractal Depth of 0.

A screenshot of a database editor displaying coordinates for North, South, East, and West along with corresponding NS Grid and EW Grid values. A cursor points to one of the grid cells.

7. Return the Plan Camera to its default location. Uncheck the Terrain Polygon Edges box in the View Preferences window and close it.

8. Alt-click the Main Camera to activate it and Crtl-click a new location in the drainage about here.

A computer screen displaying a terrain map with grid lines, showing varied topography in green, brown, and gray colors. A cursor points to a location on the map.

9. Give it an elevation of 2100 meters.

A dialog box titled "Value Request" prompts the user to enter a new elevation for the camera. The current entry is "2100," and the cursor is hovering over the "OK" button.

10. Render a preview.

11. Depending on the amount of RAM you have, one of 2 things will happen. VNS will either take some time to think about it and start rendering and or give you a Memory Allocation Failure error.

A computer screen displaying a landscape in a 3D modeling program, featuring a gray terrain with hills and a clear sky background. A mouse cursor is visible on one of the hills.

12. To save time, VNS only renders the DEMs it has to. In this project, our Main camera is only seeing a part of the total terrain. Since we only have 1 DEM, VNS has to make calculations for the entire DEM, which is a big waste of time and memory. The solution is to tile the DEM, that is, subdivide it into several smaller DEMs. VNS will only have to render what the camera sees, resulting in fewer calculations and faster render times. Tiling is done during import for most data types but the gap-filling required by the SDTS DEM format precludes it. SDTS DEMs require a second import to tile the single DEM created by the first import.

13. Open the Import Wizard . Choose the YNP-10m.elev we just created, and Open it.

A file open dialog box titled "Import Data" showing the directory "YNP" with two files listed: "YNP-10m.elev" and "YNP.proj". The selected file is "YNP-10m.elev". The "Open" button is highlighted.

14. Next your way through the Import Wizard to the DATA POSITIONING window. Previously, this is where we accepted defaults and imported. We could do this now and the DEM would be tiled automatically, but we’d like to see what the Wizard is doing. Select Change Settings.

A software dialog box titled "Import Wizard: YNP-10m.elev" with options for loading data, "Load Now" or "Change Settings," and buttons labeled "Back," "Next," and "Cancel.

15. Click Next until you get to the OUTPUT DEMS page. The information box at the top explains tiling, telling us the render engine has to load an entire DEM into memory if any portion of the DEM is in camera view. The Import Wizard chooses DEMs Row-Wise and Column-Wise to divide the imported DEM into 300-row by 300-column tiles. That’s where the 7 and 10 come from. We’re not going to change anything so Import.

A software import wizard window displaying options for loading DEMs, including dimensions, DEMs rows and columns, output cells, and cell sizes. Includes buttons for Help, Cancel, and Import.

16. If you select an Object in the Database to refresh the list, you’ll notice that we now have 75 objects. That’s 4 quad boundary vectors, 70 tiled DEMs (10 rows times 7 columns), and the original DEM.

A screenshot of a database editor showing a table with columns: Name, Enabled, View, Render, Color, and Class. Rows contain various entries with checked boxes, names, color codes, and class types.

17. Select the original YNP-10m DEM at the bottom of the list. That makes it the active object, so it’s partially highlighted in the Main view where it overlaps matching DEM tiles. If we don’t disable or remove it from the Database, it will still render. Remove the DEM.

A software window titled "Database Editor" showing a list of database objects with columns for name, enabled status, view, render, color, and class. All items listed are enabled and classed as "DEM.

18. When asked if you want to remove the DEM from the disk, answer No; we might want the DEM later on. Save the project.

A dialog box titled "Database: Remove" asking to delete 1 DEM elevation file and remove 0 other objects from the database, with options "Yes," "No," and "Cancel.

19. Render another preview. Aside from going much faster, you’ll see from the Status window that we’re only rendering some of our 70 DEMs. The smaller tiles free up valuable memory for other operations, which we’ll need later on.

Computer screen showing a progress bar at the bottom labeled "DEM 5/24" with a lock icon, blue segments, and a red "X" icon.

20. Let’s group the 10-meter DEMs on a layer for easy selection. Select the first DEM and shift-click the last one to select all the DEMs. The titlebar will show 70 of 74 objects selected.

A screenshot of a Database Editor window showing a list of items with properties such as Name, Enabled, View, Render, Color, and Class. All items are checked as Enabled.

21. Go to the Layer page and Show Properties Panel . You’ll see TOP, which is the default layer VNS creates on import.

Screenshot of a database editor window showing a list of objects with names beginning with "YNP-10m" and an active layer named "TOP".

22. Click Add and enter DEM 10m into the Input Request window for the Layer Name. This will add all the 10-meter DEMs to a layer named DEM 10m.

A dialog box titled "Input Request" with the prompt "Enter new Layer Name." The text field contains "DEM 10m," and an arrow cursor is hovering over the "OK" button.

23. To test it, select any object in the list and select the DEM 10m layer. Use the Select button to select all objects on that layer. This may not seem like much help now, but it will be when you have hundreds of database objects.

Screenshot of a database editor software interface showing a list of layers including "MOUNT JACKSON", "MADISON JUNCTION", and "LOWER GEYSER". A hand cursor is hovering over the "Select" button.
Scroll to top
Skip to content