Veydris Open World

Documentation

A practical guide to the public build of Open World: installing it, finding your way around the editors, importing models and walking around your scene.

Before you start

Open World is in early development.

This guide describes the build you can download today. Features are checked by automated tests and by looking at real rendered frames, but much of the editor has had little hands-on use by people yet. Expect rough edges, and keep copies of work you care about.

Open World is a native C++ and Direct3D 12 engine for large open worlds. The download contains the engine, a scene editor, a world editor for terrain and roads, a physics sandbox and a small demo project called Coastal Town.

It is not a finished game engine. Gameplay scripting, audio and exporting a standalone game are not in the public build. The last section lists what is missing, and the roadmap describes what is being worked on.

Getting started

Install

  1. Check the system requirements: 64-bit Windows 10 (version 2004 or newer) or Windows 11, and a DirectX 12 graphics card with Shader Model 6.6 and a current driver.
  2. Get the installer from the Downloads page and run it. Windows SmartScreen may warn about an unknown publisher because the installer isn't code-signed yet: choose More info, then Run anyway.
  3. The installer needs no administrator rights. At the end it builds the Coastal Town demo project, which takes a few seconds and also confirms that your graphics card can run the engine.

What you get in the Start menu

ShortcutOpens
Open World EditorThe scene editor with the Coastal Town project loaded. Start here.
Open World - Play Coastal TownThe demo town straight in play mode, as a third-person character.
Open World Physics SandboxA stretch of beach with heavy test objects, a grab tool and the world editor.
Open WorldThe environment on its own, with a free-flying camera.

First start

On the first start, a tutorial walks you through the basics: the editor layout, the camera, selecting and moving things, undo, adding objects, pressing Play, walking around, stopping and saving. Each step completes by itself once you have done it. You can reopen it at any time from Help > Tutorial.

The engine also checks for a newer version when it starts. See how updates work.

Free camera and environment

Outside the scene editor you fly a free camera over the world. Press F4 at any time to switch between the free camera and the scene editor.

InputAction
MouseLook around
W A S DMove horizontally
Space / CMove up / down
Shift / CtrlMove faster / slower
Mouse wheelChange the base speed
EscRelease the mouse and open the Environment Editor, or recapture the mouse
F1Performance overlay on / off
F2Hide all interface elements, for clean screenshots
F12Take a screenshot
F4Scene editor on / off
Ctrl+PPlay / Stop

Environment Editor

Press Esc to open it. The first group, Environment controls, covers the things you will change most often: cloud coverage and density, wind speed, sun intensity, atmospheric haze, ocean wave amplitude, water clarity, terrain material variation and vegetation density.

Below that are detailed sections for the sun and time of day, atmosphere, clouds, wind, ocean, shoreline surf, terrain and vegetation, plus tabs for graphics settings, the camera, viewpoint presets, a profiler and the log. Save settings stores your changes as the engine's defaults, and Reload settings reads them back.

Scene editor

The scene editor is where you build a place: it runs inside the engine, so what you see in the viewport is the real renderer, physics and world. You build scenes from imported models, built-in street furniture, roads, lights and prefabs, and save them as projects.

Layout

AreaWhat it is for
Menu barFile (projects and scenes), Edit (undo, redo, duplicate, delete, group), Create (groups, lights, built-in objects, roads, prefabs), View (panels, grid, interface scale, camera), Tools and Help.
ToolbarThe Select, Road and Terrain tools; Move, Rotate and Scale; world or local axes; grid, angle and scale snapping; "stay on ground"; the sun and the streetlight mode.
Hierarchy (left)Everything in the scene as a tree, with a filter box. Roads and intersections are listed below the entities.
Inspector (right)Properties of whatever is selected: name, visibility, transform, ground alignment, model and materials, collision, light and prefab settings. It also shows settings for the road and terrain tools, and a list of problems in the scene.
Asset Browser (bottom)Your project's models with rendered thumbnails, the built-in objects and your prefabs. Import and place things from here.
Status barFrame rate, the current selection, the cursor position on the ground and the last action or warning.

Panels can be hidden and resized from the View menu, and View > Reset Panel Layout puts them back. The interface scales with the window height, and View > UI Scale overrides it.

Viewport controls

InputAction
Left clickSelect. Ctrl toggles, Shift adds. For a group or prefab, the first click selects the whole thing and a second click selects the member.
W / E / RMove / rotate / scale gizmo
XSwitch between world and local axes
DeleteDelete the selection (or the selected road point or road)
Ctrl+DDuplicate in place
Ctrl+GGroup the selection
Ctrl+Z / Ctrl+YUndo / redo. This covers everything: entities, roads, intersections and terrain.
Ctrl+SSave the scene
FFrame the selection in the view
EndSnap the selection onto the ground
Right mouse + W A S DFly. The mouse is only captured while the right button is held. Space / C go up and down, Shift goes faster.
Alt + left dragOrbit around the selection
Middle dragPan
Mouse wheelMove toward the point under the cursor
F12Screenshot

Snapping. Grid snapping applies to gizmo moves, road points and dropped models (1 m by default). Angle snapping applies to rotations and drops (15 degrees). Scale snapping is off by default. With "stay on ground" on, objects follow the terrain while you move them sideways; lifting an object with the vertical arrow detaches it from the ground until you press End.

A typical session

  1. File > New Project, then pick a folder and a name.
  2. Click Import... in the Asset Browser and choose a model, or drop model files from Explorer onto the window. The model loads in the background and gets a rendered thumbnail.
  3. Drag the thumbnail into the viewport. The model lands where you drop it, snapped to the grid, facing the camera and standing on the ground.
  4. Move, rotate and scale it with W, E and R, or type exact values in the Inspector.
  5. Lay down roads with the Road tool (see Roads and intersections).
  6. Duplicate things with Ctrl+D and choose their colliders under Inspector > Collision.
  7. Save with Ctrl+S. If you close the window or open another project with unsaved changes, the editor asks first.

Entities, lights and prefabs

Everything you place is an entity: an imported model, a built-in object, an empty group, a light or a character. Entities form a tree, so moving a parent moves its children, and grouping or re-parenting keeps things where they are in the world.

The built-in objects are a streetlight, path light, bench, bollard, trash bin, traffic cone and concrete barrier.

PropertyWhat it does
Ground alignmentTop-level entities can follow the ground. They sit on the terrain or road under them and are re-aligned automatically when you edit that terrain. "Tilt with slope" also tilts them.
CollisionAuto gives built-in objects a collider that matches their parts and models a box around their bounds. You can also pick an editable Box, Sphere or Capsule, use the model's own triangles with Mesh, or choose None. The surface setting controls friction and bounce.
LightA point or spot light with brightness, colour, range and cone, optionally on only at night. The nearest 128 lights are active at any time, streetlights included.
ModelTriangle, material and texture counts, the materials themselves, any warnings from the importer, and a button to reload the file.

If a model file goes missing, the scene still loads. The entity keeps its place and size, shows up as a red box and is named in the problems list. Put the file back and reload it to restore the model.

Tools > Drop Physics Test Box on Selection is a quick way to check that a collider behaves the way you expect.

Prefabs

A prefab is a reusable object made from an entity and its children. Select something and choose Create > Prefab from Selection. Prefabs appear in the Asset Browser and are placed by drag and drop.

  • Changing a prefab changes every instance of it.
  • Each instance has its own position, and its children can override visibility, light settings, collider settings, name and local transform. Overridden children are marked with * in the Hierarchy.
  • Apply Instance to Prefab writes an instance back to the prefab and refreshes the others, which keep their own overrides.
  • Not supported yet: prefabs inside prefabs, adding or removing children per instance, and reverting a single override.

Roads and intersections

Choose the Road tool, click points on the ground, then press Enter (or double-click, or right-click) to build the road. The terrain is flattened and blended under it, and streetlights are placed along it automatically.

  • End a road near another road to join it with a T intersection. Cross another road to make a four-way intersection.
  • Road ends snap to existing junctions and to free road ends nearby. A green marker shows the snap.
  • Select a road to edit it. Drag its points, Ctrl+click on the road to insert a point, and press Delete to remove the selected point.
  • The Inspector edits the road's width, sidewalks, smoothing, streetlights and the height of each point.
  • When you move or delete a road, the ground it flattened goes back to how it was, unless you have edited that ground since.

Intersections get their own surface with rounded corners, stop lines and, where both roads have sidewalks, curbed corners. Editing one road only rebuilds that road and its neighbours, not the whole network.

Not supported: bridges, overpasses, roundabouts, lane markings through intersections and traffic. Roads only connect to roads of the same kind, so a sidewalk or bike path crossing a road stays separate.

World editor and terrain

The world editor works directly on the ground, from the free camera, using a crosshair. Press T to turn it on and Tab to cycle between its three tools. Ctrl+Z and Ctrl+Y undo and redo in every tool.

ToolHow to use it
TerrainHold the left mouse button to apply the brush. Number keys pick the brush: raise, lower, flatten, smooth, erase, paint, ramp, roughen, add snow, remove snow. The wheel changes the radius, Shift+wheel the strength and Alt+wheel the falloff. M picks the next material. For a ramp, click the start and then the end.
Roads1 road, 2 sidewalk, 3 bike path. Left click adds a point, right click or Enter builds it, Backspace removes the last point, L toggles streetlights and Delete removes the road under the crosshair.
Objects1 to 7 pick a streetlight, path light, bench, bollard, trash bin, traffic cone or concrete barrier. Left click places it on the ground, the wheel rotates it in 15 degree steps, and Delete or right click removes the highlighted object.

F6 saves the world and F7 loads it. The last save is loaded automatically the next time you start.

Ground materials

You can paint rock, grass, dirt, concrete, asphalt and gravel on top of the natural sand and vegetation. A material is more than a look: it sets how much grip and bounce the ground has and whether it gives way under weight. Sand, dirt, grass and gravel deform; rock, concrete and asphalt do not. The values can be adjusted in the Environment Editor under the terrain physics section.

Snow, rain and tracks

  • Snow builds up and melts at rates you set, and you can add or remove it with brushes. Feet, wheels and heavy objects pack it down before they reach the ground underneath.
  • Rain soaks the ground, which darkens, becomes firmer and more slippery, and dries out again afterwards.
  • Footprints and tyre tracks are pressed into soft ground and stay there. A spinning wheel digs a deeper rut than a rolling one.

The large world

The beach at the centre is about 4 km across, and it sits inside a generated 16 × 16 km world of coast, dunes, highlands and valleys. The surroundings load in the background as you move. You can sculpt terrain, build roads and use physics anywhere in it, and saves only rewrite the parts that changed.

Importing models

The public build imports glTF 2.0 models, as .glb files or as .gltf files with their buffers and images. Importing copies the files into your project, so the project stays self-contained.

What comes across

  • Meshes, including several meshes and parts per file, and the node hierarchy.
  • Materials: base colour, metallic and roughness, normal maps, occlusion and emissive, each as a value or a texture, plus double-sided surfaces.
  • PNG and JPEG textures. Textures larger than 4096 pixels are scaled down.
  • Opaque, cut-out and blended transparency. Blended surfaces are drawn with a dithered effect rather than true sorted blending.
  • Missing normals and tangents are generated for you.
  • Rigged models: skeletons, skin weights (up to four bones per vertex) and animation clips. A rigged model dropped into the scene becomes a character (see Play mode and characters).

What does not

  • Morph targets (blend shapes), cameras and lights stored in the file, and a second set of texture coordinates.
  • KTX2, WebP and Basis textures, and texture transforms.
  • Draco or meshopt compressed geometry. Those parts of a model are skipped.
  • Points and lines. Unlit materials are drawn lit.
  • FBX and other formats. FBX import is being worked on but is not in the public build.

Where it can, the import still succeeds and shows a warning in the Inspector. Files that are damaged, have no triangles or need an unsupported extension are rejected with a message that says why.

Good to know

  • Units and orientation. Models are expected in metres with Y up, as glTF defines. The importer converts them to the engine's own conventions, so a model keeps its shape and faces the camera when you drop it.
  • Scale. You can set a scale when importing a model.
  • Caching. An imported model is decoded once and cached, so scenes load quickly. If you change the source file it is re-imported automatically, and Reload model file forces it.
  • Sharing. Every copy of a model in a scene shares one set of data, so placing many of the same thing is cheap.
  • Managing files. You can create folders and move models between them in the Asset Browser. Renaming and deleting model files from inside the editor is not available yet.
  • Licences. Only import models you made, commissioned or have a licence for, and keep the licence file next to the model.

Play mode and characters

Press Play in the editor toolbar, or Ctrl+P, to walk around your scene as the Player character. Press Stop or Ctrl+P again to return to the editor exactly as you left it: footprints, pushed sand and moved props are all put back.

InputAction
W A S DMove relative to the camera. The default pace is a jog.
Shift / Alt (hold)Sprint / walk
SpaceJump
Mouse, wheelOrbit the camera, change the camera distance
EscFree or recapture the mouse. The Stop button can be clicked while the mouse is free.
Ctrl+P or StopBack to the editor
F1 / F2 / F12Stats overlay / hide the interface / screenshot

The public build uses keyboard and mouse. Saving is disabled while you are playing.

Characters

  • Player. A third-person character that walks, jogs, sprints and jumps, climbs steps and curbs, is stopped by steep slopes and pushes loose objects. The camera pulls in when a wall is behind it.
  • Pedestrians. Characters that follow a route you draw in the editor, with a wait time and pace per point. Routes can loop, go back and forth or run once.
  • Animation. The engine picks idle, walk, jog, run, jump and fall clips by name, blends between them by speed and plays them at the pace that keeps feet from sliding. You can assign any clip to any slot in the Inspector.
  • Foot placement. Feet are planted on uneven ground and curbs, on rigs where the engine recognises the leg bones.
  • Footprints. Each planted foot presses into soft ground with the character's weight, so sand and snow keep a trail and paving does not.
  • Play-mode props. Mark an entity as a physics prop and it becomes a loose object while playing, then returns to its place on Stop.

Limitations

  • Pedestrians steer around small obstacles but have no path-finding. Draw routes along sidewalks and open ground, not through buildings.
  • The demo characters are deliberately simple placeholders, not finished art.
  • Camera sensitivity and similar options are not in the interface yet.

Physics Sandbox

The sandbox puts a 1.5 m concrete cube weighing about eight tonnes, and four lighter objects, on the dry upper beach so you can see the ground react. Aim with the crosshair and press F for the grab tool.

InputGrab tool
Left mouseGrab the object under the crosshair
Right mouseRelease
Mouse wheelChange the grab distance
MouseMove the held object. Look up to lift it, down to press it into the ground.
G / HDrag along the ground / steady hold, which keeps the object level
RReset the selected object
TOpen the world editor
F9Reset the sandbox, including all terrain changes
F6 / F7Save / load the world

Heavy objects sink into sand when they land, plough a furrow with ridges when dragged, and leave the ground changed. One known gap: weight is not passed down through stacked objects, so a cube resting on another does not push the lower one deeper.

Projects and saving

A project is a folder that holds your imported models, your prefabs and one or more scenes. A scene stores what you placed, your roads, the terrain edits, and its own lighting and editor camera, so each scene reopens looking the way you left it.

  • Scenes refer to models by their location inside the project, so a project folder can be moved or backed up as a whole.
  • Saving writes to a temporary file first and then swaps it in, so a crash while saving does not leave a half-written scene.
  • Terrain is saved in pieces, and only the pieces you changed are rewritten.
  • The project's cache folder only holds decoded copies of your models. It is safe to delete and is rebuilt when needed.

Updating or reinstalling the engine does not touch your projects, saves or captures. See how updates work.

Troubleshooting

ProblemWhat to try
Windows blocks the installerThat is SmartScreen reacting to an installer that isn't code-signed yet. Choose More info, then Run anyway.
The installer or the engine says the graphics card is not supportedThe engine needs DirectX 12 with Shader Model 6.6. Update the graphics driver first. Integrated graphics older than about 2020 are not supported.
A laptop uses the wrong graphics cardStart the engine with --adapter N, where N is the number of the card you want. The available cards are listed in the engine's log.
A model imports with warnings or not at allCheck it against the list under Importing models. The Inspector and the log say what was skipped or why the file was rejected.
The update check failsRun Help > Check for Updates to see the reason. You can always install the newest version over the old one from the Downloads page.
Something else went wrongThe engine keeps a log, and writes a crash report if it crashes, in the Logs folder inside its install folder. Please include them when you contact us.

Not in the build yet

So you don't go looking for them, these are not in the public build:

  • Gameplay scripting. There is no way to script behaviour in the public build. It is in development; see the roadmap.
  • Exporting a game. You cannot package a scene as a standalone game. Work on this has not started.
  • Audio. The engine has no audio system.
  • Vehicles, crowds and AI, missions and multiplayer.
  • FBX import and compressed textures.
  • Controller support and rebindable keys.

Known rough edges in the editor

  • Much of the editor has been verified by automated tests rather than by people using a real mouse and keyboard, so some interactions may feel off.
  • There is no box (marquee) selection, and scaling several objects at once scales each about its own origin.
  • Views are perspective only. The Top camera is a narrow-angle view from high up, not a true orthographic plan view.
  • Editing a road regenerates the streetlights that road placed. Lights you placed by hand are kept.
  • Undo history and road records for terrain-heavy scenes can use a lot of memory and disk space.

Found a bug, or stuck on something this page doesn't cover? Use the contact form on veydristech.com.