GenAnywhere Generate Now

Select a map area. Generate a 3D city model with AI.

No drone survey required. Turn map data into editable 3D buildings, terrain, water and vegetation for BIM, GIS and 3D workflows.

Generate now

VR training games: three site checks before a GenAnywhere build

Layout, task path and change over time decide whether a site base is worth building on.

A training game built on a real site needs three checks before the environment work starts: the layout has to match the working site, the task path has to hold at human scale, and the scene has to be dated so someone can tell when it stops matching. A generated site model can supply the geometry those checks run against, and it cannot supply the procedure, the equipment or the judgement a trainee is meant to practise.

Loading bay of a German distribution centre with roller doors and marked lanes

1 Name the task before the site

1.1 What must the trainee be able to do?

Write the task as an action a person performs, such as isolate a valve before maintenance or walk a loading route without entering a vehicle lane. The wording decides which parts of the site matter and which can stay as context. A scenario described as an awareness module gives the environment team nothing to build against.

Keep the task small. Three clear actions taught well beat a tour of a whole facility, and a narrow scope is easier to keep aligned with the site over the life of the project.

Write down what the trainee should notice as well as what they should do. A scenario about spotting a hazard before entering a bay depends on the view from the doorway, and that requirement changes how the space has to be modelled.

1.2 Which parts of the site does the task touch?

Mark the route, the surfaces the trainee stands on and the objects the task interacts with. Those three areas need the most care, and everything beyond them is background that can be simplified. A trainee notices a wrong handrail long before a wrong rooftop two streets away.

Draw the areas on a plan and keep the plan with the build. When a reviewer asks why one corner has detail and another does not, the plan answers without a meeting.

2 Check one: does the layout match the working site?

2.1 Which reference settles the layout?

Use the drawing the site team works from, then confirm it against photographs taken on a normal working day. Drawings describe intent, and sites drift: a rack moves, a partition goes up, a door stops being used. Ask the supervisor which version of the layout is current before assuming the drawing is right.

Walk the site yourself when the route is short. Ten minutes in the real space settles questions about noise, floor markings and the things people leave in corners, and none of those show on a drawing.

2.2 Where do generated footprints mislead a trainee?

GenAnywhere builds an editable site model from mapped data, with footprints, estimated heights, inferred building types and surrounding vegetation held in separate layers. The output describes the outside of a building, so anything inside a wall, such as a plant room or a partition, has to come from the site team. Inferred types are a guess from mapped evidence, and a warehouse that reads as an office in the scene will send a trainee to the wrong door.

Treat the generated scene as the shell, then place the working layout inside it. This is AI 3D generation for context, and the training content carries the operational truth.

3 Check two: does the task path hold at human scale?

3.1 How do you walk the procedure in a blockout?

Stand the trainee avatar at the start point and follow the steps as written, speaking each one aloud as you go. Stop wherever the view does not let the next step happen, since a valve behind a pipe or a panel at the wrong height breaks the procedure even when the room looks correct. The walkthrough is a test of the layout and of the script at the same time.

Repeat the walk with someone who does the job. They will point at a step that reads fine on paper and feels wrong in the space, and that comment is worth more than a review meeting about the blockout.

3.2 What breaks when an aisle is narrow?

Clearance problems appear early in VR and they are hard to argue with. A route that leaves half a metre beside a rack forces the trainee to shuffle, and a doorway that fits a model but not a person wearing equipment changes the whole approach. Check the path with the widest item a person will carry, not with an empty avatar.

Ask the site supervisor what people actually do at the tight point. Workarounds are common, and a training scene that ignores them teaches a procedure the site does not follow.

4 Check three: will the site still match next quarter?

4.1 How do you date a scene?

Record when the area was generated, what imagery the platform held and who confirmed the layout. Put the date where the build team will see it, not in a project folder nobody opens. A scene without a date becomes an unanswerable question the moment someone asks whether it is still current.

Add the site's own revision number when it has one. Two dates, one for the model and one for the site's last recorded change, tell a reviewer how far apart the two are.

4.2 What triggers a rebuild?

Any change to the route, the equipment or the room triggers a review, and so does a new site drawing. Rebuild the parts the task touches and leave the background alone. A full regeneration is not needed when one wall has moved, and a partial update needs the same review as a new scene.

Set a review rhythm with the site team as well. A quarterly conversation about changes costs an hour and catches the drift that a rebuild cycle misses.

Aerial render of a large waterfront campus with office buildings

5 Set up the build so the site stays reviewable

5.1 What does the build need from the export?

The scene can be previewed and exported as a general GLB for 3D, BIM, GIS and game engine workflows. Export the layers the build needs, name them for the people who will open the file, and keep the source scene for reference when the site changes. Interior equipment, interaction volumes and collision are built in the engine, and none of them arrive with the site.

Test the import with a human-height marker before the scenario work begins. A base that arrives at the wrong scale will make every interaction volume wrong, and the error is easier to find in an empty scene.

Try the site step in the GenAnywhere app with a facility you can visit in person.

5.2 How do you separate training logic from site geometry?

Keep the site in its own group or level, and put triggers, scoring and procedure steps somewhere else. When the site is updated, the training logic should survive without being rebuilt from scratch. Teams that mix the two spend their review time untangling objects instead of checking the scenario.

If the build ships in a browser, read the WebXR specification published by the W3C before the scene is split. It describes how a session presents content to a headset, which shapes the choices about what loads with the site and what loads with the procedure.

Aerial view of a dense city district beside a wide river

6 Decide what the scene cannot carry

6.1 What belongs to the training designer, not the site?

Procedure order, feedback, difficulty and the consequences of a mistake belong to the designer. The site supplies the space those decisions happen in, and it says nothing about how a trainee should be guided through it. Be clear about the split when the scope is written.

A useful rule is that the site can be replaced and the scenario should still work. If swapping the building breaks the training design, the design was leaning on the model rather than on the task.

6.2 How do you review the scenario without claiming outcomes?

Review the match between the scene and the site, the clarity of each step and the behaviour of the build under test. Leave learning outcomes to the training team and their own evaluation, since a site model cannot demonstrate that anyone learned anything. Keep the review notes factual and dated.

Separate the two kinds of finding in the notes as well. A geometry mismatch belongs to the environment team, and a confusing step belongs to the designer, and mixing them in one list slows both.

6.3 When should the team commission a survey instead?

When the task depends on a dimension nobody has verified, when the site is changing during production, or when the equipment layout has to be exact for the procedure to make sense. A survey or a laser scan carries the authority a mapped scene does not, and the training build will need that authority in writing.

7 Questions training teams ask about site bases

FAQ-1 Can a generated site support a procedure walkthrough?

Yes, as the space the walkthrough happens in. The scene gives rooms, routes and building masses to scale, and the procedure itself is scripted in the engine. Walk the steps in the blockout before building interactions, because the layout will expose problems in the script earlier than a completed scene will.

FAQ-2 How do you handle equipment the map cannot show?

Place it from the site's own drawings, photographs and asset list. Racks, machines, vehicles and pipe runs are operational detail, and a mapped scene will not contain them. Ask the site team for a walkthrough video as well, since it usually reveals the objects nobody remembered to list. Photograph the equipment in use, not just in storage, because a machine with its guards open is a different training object.

FAQ-3 Can the scene be edited after the build starts?

Buildings can be replaced, moved, rotated and retyped inside the platform, and heights adjusted before a new export. An edit produces a new file, so the build team has to decide what to re-import and what to keep. Version the exports and note which one the scenario was tested against.

FAQ-4 What does the licence allow for internal training?

Exports carry a permanent commercial licence for project use. Resale of the source files, use of the data for AI training and claims of ownership over the underlying imagery fall outside the licence. Check third-party data terms with your legal contact, and confirm the intended training use with them before the build is distributed.

Follow the map-to-engine steps on the GenAnywhere workflow page.

Content and technical notes

This article was prepared by the GenAnywhere team with AI-assisted drafting and human review.

Product features, formats, and availability change as the platform evolves; refer to the official GenAnywhere website for current details.

For technical questions or corrections, contact support@genanywhere.com.

Last reviewed: 2026-11-06.