VR gaming worlds: where GenAnywhere maps a real site
How a real place becomes the frame of a game world, and where invention has to take over.
GenAnywhere maps a real site by generating an editable 3D model from an area drawn on a map, which hands a game team real street widths, building masses and terrain before any art exists. That covers the outside of a place and little else. Interiors, props, lighting and the rules of play come from the studio, and the site file works well as a frame the game is built inside.

1 Decide what the real place has to do
1.1 Why build a game world from a real site?
A game set in a recognizable place borrows its credibility from the street pattern. Players who know the area notice when a junction sits on the wrong side of a park, and players who do not still feel the difference between a layout that grew and one invented to look grown. Real geometry supplies that difference without a modelling pass.
The reason is practical rather than reverent. A real street pattern has already solved problems a designer would otherwise solve by hand, such as where views open, where a route has to bend and where a district changes character.
1.2 What has to be inside the drawn boundary?
Draw wide enough to include the routes players will use and the landmarks that orient them. AI 3D generation runs over that area, reading the map and satellite data available and producing buildings, terrain, water and vegetation, with terrain matched to the buildings it places. Heights are estimated and building types inferred, which is enough to plan circulation and not enough to describe a facade.
Keep the boundary in the project record. A second area drawn six months later will not line up with the earlier one unless somebody wrote down what the earlier one included.
2 Read the generated site honestly
2.1 Which features come through clearly?
Footprints, street blocks and the broad shape of the ground come through well enough to plan against. Vegetation is analysed and placed, water bodies appear where the map shows them, and the massing reads correctly from a distance. For a game world, that is the layer players navigate by, and it is the layer a blockout needs before anything is modelled.
The value shows up early. A designer can stand at a junction and ask whether the turn is legible at running speed, then answer it the same afternoon.
Because the platform keeps buildings, terrain, water and vegetation apart, a designer can hide the vegetation and study the ground on its own. That small control is what makes a quick comparison possible without a modelling pass in between.
2.2 Where does the mapped data run thin?
Anything inside a building is absent, and so is everything smaller than a mapped feature: kerbs, steps, the wall between two gardens, the alley that exists but was never recorded. Imagery ages as well, so a scene built from an older capture describes the place as it was. Treat every surface as a claim worth checking against a photograph or a visit.
The thin spots are predictable. They cluster at the scale a player stands at, which is why the site model carries the layout and the art team carries the detail.
Compare the scene with two sources before trusting it: a recent satellite view and a ground photograph of the same corner. Where all three disagree, the photograph usually wins, because it is the one a player will recognise.
3 Turn a real place into playable space
3.1 How much of the real layout should survive?
Keep the street pattern and the massing, and expect to change almost everything else. Players need routes that read at speed, which usually means widening a lane, removing a wall or opening a sightline the real place closes. Fidelity survives in the arrangement rather than in the dimensions.
Decide that compromise district by district. A hub area can afford closeness to the original, while a route players sprint through cannot, and the two decisions do not have to match.
Width is the usual argument. Real streets were sized for cars, carts or pedestrians in a different century, and a game that expects two players to pass each other needs room the place may not have. Widen the street in the blockout and mark the change, rather than letting an artist discover the problem during the art pass.
3.2 Where does level design overrule the site?
Wherever play and place disagree. A courtyard that works as a courtyard can be a poor arena, and the fix is usually to move a wall rather than to move the game. Mark each move on the blockout so the distance between site and design stays visible to everyone reading the scene.
Those marks become the record. Two years later, the annotated blockout explains why the game does not match the place it started from, which is a question that arrives with every press build.

4 Rights, records and real locations
4.1 What should a team check before building a real place?
Ask about permissions, imagery terms and landmark rights before the world is built, and ask the studio's own advisers rather than a forum thread. Map and satellite providers license their data on their terms, and a recognizable building can carry rights of its own. A generated model settles none of those questions.
Write the answers down and keep them with the project. A world can be rebuilt; a release window spent on a rights question cannot.
Ask early, because the answers change the design. A building that has to be altered or removed is a district plan revision, and a revision after the art pass is the expensive kind.
4.2 How do you keep invented content separate from site data?
Keep two groups in the project: what came from the site and what the team invented. Name objects accordingly, and give invented props their own parent so a single click can hide them. When a partner, a journalist or a player asks which parts are real, the answer should be a folder rather than a memory.
That separation helps production too. Invented content can be moved, scaled or cut without disturbing the geometry the rest of the team is measuring against.
5 Working across a team
5.1 How do artists and designers share one scene?
Share one exported GLB rather than twelve screenshots. The platform keeps buildings, terrain, water and vegetation on separate layers and exports the scene as a general file, so an environment artist can work on buildings while a designer checks routes on the ground layer. Agree the import settings once, then treat them as part of the project setup.
Someone has to own the scene. Two copies of a site file diverge faster than two copies of a document, because nobody notices a moved building until a route stops working.
Delivery is a separate question. A browser build reaches a headset through WebXR, the W3C specification for immersive content on the web, while a native build goes through the engine's own XR layer, so confirm which path the prototype uses before the scene is prepared for it.
5.2 How do you hand a site over to someone new?
Pass on the boundary, the imagery date, the units and a short list of what was changed. Include the reason for each change, since the next person will otherwise restore something that was removed on purpose. One page covers it, and it saves the opening week of a new starter.

6 Use the site as a frame, then let it go
6.1 When is a real site the right foundation?
When the place is part of the premise. A game about a port, a border town or a mountain pass gains from the real arrangement of streets and ground, because the geography is doing narrative work that no amount of prop dressing replaces.
That test is worth applying early. Teams sometimes adopt a real site for texture alone, then spend production fighting constraints that were never asked to do a job.
6.2 When is a fictional site better?
When the place is a mood rather than a premise. A fictional town lets the team invent the landmarks the game needs without arguing over which real building gets sacrificed. Real sites bring constraints, and constraints earn their place when they answer a design question.
6.3 How do you document the difference?
Record the site the world started from, the boundary and the capture date, then list the departures. A short comparison note serves the studio during production and answers the question later, when someone asks how the world was made and which parts of it are borrowed.
Keep the note short enough that people read it. A page of dates, boundary notes and five listed departures beats a forty-page document that nobody opens twice.
Map the real site in the GenAnywhere app before the layout is fixed, then measure the streets against it.
7 FAQ
FAQ-1 Can GenAnywhere map any place?
No. The platform generates from the map and satellite data available for the area you draw, and coverage and detail vary between regions. Check the area before a premise depends on it, and look closely at the streets the game will use rather than at the middle of the boundary. Where the data is thin, plan for more art work or shift the site slightly.
FAQ-2 Does the model include building interiors?
No. A site model describes the outside of a place: footprints, heights, terrain, water and vegetation. Interiors, stairs, floor plans and room layouts are authored in the engine or come from survey drawings the studio holds. If play happens indoors, treat the generated model as the shell and the street context around it.
FAQ-3 How close should the game world stay to the real place?
As close as the premise needs and no closer. Decide per district, write the decision down and annotate the blockout where the design departs from the site. Keeping a real street pattern while changing a courtyard is a normal result. Explaining why is what separates a considered world from an inconsistent one.
FAQ-4 What belongs in the project record?
The boundary, the capture date, the units, the licence terms, the list of departures and the name of whoever reviewed the scene. Keep it beside the exported file rather than in a chat thread. Six months from now that page answers the questions a new artist, a partner and a lawyer will each ask in a different way.
See how a drawn boundary becomes an exported scene in the GenAnywhere workflow overview.
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.