You Noticed Vista Pro Has Something You Need

If you have been using Vista long enough to build a working terrain workflow, you probably noticed the moment it happened: you clicked into a feature, read the description, and saw "Vista Pro" next to it. Then you spent a few seconds weighing whether your project needs it.

This post is for that moment.

It does not try to sell you on Vista as a tool. You are already using it. The question is whether a specific set of workflow capabilities matches where your project is actually going.

What Pro adds on top of Indie

Vista Personal gives you the full procedural graph, natural simulations, unlimited biomes, and support for both Unity Terrain and Polaris. Indie builds on that with hand painting, MicroSplat integration, nav mesh baking, and the Productivity Boost graph editing tools.

Pro is not the tier where the terrain gets better. Resolution increases from 512px at Personal to 4096px at Indie, and Pro matches Indie there. What Pro adds is a specific set of workflow integrations for projects that need to work with real geography, place authored paths and shapes in the scene, or surface graph parameters to the rest of the team.

The three additions are:

• Splines: use scene-placed splines to drive terrain operations.

• Real World Data: import DEM elevation and satellite imagery as graph inputs.

• Expose Property: surface graph node properties as Inspector controls on each biome.

Each one targets a different kind of project. If none of them match your situation, Pro is not the right step.

Splines

The terrain looks natural at scale, now you want something man-made

You have procedural terrain that reads well at scale. But some features in your world are not procedural: a road that follows a specific route, a mountain pass at a deliberate elevation, a cleared area where a village sits, a river valley that narrows at a particular point. These need to exist where you put them, not where the graph decides.

Without splines, the workaround is usually a combination of painted masks, manual stamp placement, and graph adjustments that need to be redone whenever the layout changes. It works, but the relationship between the layout change and the terrain update is manual.

Splines in the scene become graph inputs

Splines lets you place a path in the scene and use it as a direct input to your terrain graph. The terrain responds to the spline at graph execution time. Move the spline, regenerate, the terrain updates.

Four graph nodes drive the operations:

Ramp takes the spline's height profile and conforms the terrain to it. The output is both a modified height map and a ramp mask. This is how a mountain pass gets carved at the right elevation, or a road bed gets a consistent grade across rolling terrain.

Path rasterizes the spline into a grayscale mask: a stripe the width you configured, with soft edges. Feed that into a weight or color blend node to texture the road surface.

Thin Out Along removes foliage instances near the spline. Used with an inverted mask, it keeps only instances near the spline instead. This handles vegetation clearing for roads, rivers, or clearings without manually sculpting a mask.

Spline Extract outputs raw spline data: anchor positions, sample points, a coverage mask, a height map, and a bounded region. For specialized operations (spawning objects along a route, constraining a procedural pass to a defined corridor) this is the node that makes it possible.

One spline GameObject can carry multiple Spline Evaluator components, each with its own ID, width, and purpose. A road might use one evaluator with a narrow width for the Path node and a second with a wider width for Thin Out Along. Same spline, two operations, independently configured.

Vista supports Unity Splines (free via Package Manager), Polaris Spline Tool, Curvy Splines, Dreamteck Spline, and Bezier Solution.

Real World Data

The outside-Unity pipeline problem

You are working on a terrain based on a real location. If you are pulling elevation data and satellite imagery separately and feeding results in manually, the pipeline lives outside Unity. When the terrain scope changes, the process repeats.

Geography as a graph input

The core payoff is straightforward: draw a rectangle over any region on an interactive world map, download elevation and satellite imagery directly into a project asset, and connect that asset to your terrain graph. Real geography becomes a graph input in a few clicks.

Data sources include USGS (elevation and imagery, with strong US coverage), Open Topography (global DEM datasets), and any custom tile service via URL template. Once downloaded, the Load Real World Data node pulls height and color data into the graph like any other input.

Height scale: Use the Real World Height Remap node when you need geographic scale in your output. If you only need the terrain shape, you can stay in normalized space and adjust visually with a Levels node instead.

Real data as a starting point: The more common workflow is using elevation and satellite color as inputs to a broader procedural graph. The height map gives you a geographically accurate silhouette. The satellite color, processed through an HSL Selector node, generates masks (forested areas by saturation, snow coverage by lightness, water by hue) that feed into texture and foliage nodes. The data provides the geography. The graph provides the artistic and runtime control on top of it.

Expose Property

When the graph becomes a bottleneck

You have a terrain graph that works. You also have ten biomes in a scene that each need slightly different versions of it: same structure, different parameter values for different locations. Managing ten graph assets for one conceptual graph is its own maintenance problem.

And when someone else on the project needs to tune a specific parameter (the height falloff of a mountain range, the blend width of a snow cap, the density curve of a forest), they either need to understand the graph well enough to navigate it safely, or you need to make the change yourself. Either way, the graph is the only door into the terrain's creative controls.

Tune biomes without opening the graph

The template workflow is the main value: one graph that defines the structure, with a set of parameters surfaced as labeled Inspector controls on each biome. Many biomes in the scene uses the same source graph but stores its own override values.

For teams, this creates a clean division of work. The graph author defines what is adjustable and what is not. The level designer opens a biome Inspector, sees grouped and labeled controls (sliders, color pickers, curve editors, dropdowns) and adjusts from there, without touching the graph.

The source graph always stays clean. What you expose and what you keep internal is entirely up to you.

What can be exposed: Settable public instance properties that Vista can expose include integers, floats, booleans, strings, Vector2/3/4, Color, Gradient, AnimationCurve, enums, and Unity Object references. Height curves, color ramps, texture references, density values: most authoring-relevant properties are in scope.

Grouping and labeling: Exposed properties are organized by Group name in the Inspector. Labels and descriptions are yours to define. These are what a collaborator reads, so making them specific is worth the time.

Is Pro the right step for your project?

Pro is the right edition if your project needs at least one of these three workflow integrations and Personal or Indie does not provide it.

The clearest signal: you already tried to use one of these features and saw the edition gate. That is not an accident. You were at a Pro workflow boundary for a reason.

Choose Pro if:

- Your terrain has authored paths, roads, rivers, or clearings that need to track geometry placed in the scene.

- You are building from real elevation or satellite data.

- You need to surface graph parameters as Inspector controls on each biome, whether for your own workflow or for a collaborator.

Ready to upgrade?

If you read this far and recognized your project in at least one of these sections, Pro is likely the right step.

You already have the terrain workflow. You already know Vista. The upgrade adds the specific capability your project needs without changing anything that is already working.

Upgrade to Pro