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

Site model export: what teams send to Unity from GenAnywhere

The scene leaves the browser as a general file, and the importing team decides what it becomes.

Site model export is where a browser scene turns into something a game team can use. GenAnywhere previews the model and exports a general GLB, which carries geometry and materials into Unity and other tools. This article covers what travels, what changes on import, and the checks that keep a handover from turning into a rebuild.

Aerial view of a city block with a new excavation on site

1 What the export is

1.1 Which file comes out?

The file is a general GLB, exported after a preview in the browser. It holds the scene as geometry with materials, not as a project file for any one application. That neutrality is the point: the same file can go to a game engine, a design tool or a GIS viewer.

The GLB format is maintained through the Khronos Group and is widely read. Widely read is not the same as identical everywhere, and the differences appear at import rather than at export. Test the file in the destination before the team depends on it.

1.2 What does it carry?

It carries buildings, terrain, water and vegetation as geometry, with materials attached. It does not carry a design history, authored properties or a survey record. What it carries is shape, and shape is what a game scene needs at the blockout stage.

Layers may survive as separate objects or may arrive merged, depending on the receiving tool and the way the scene was prepared. Check the object list after import, because a merged scene is hard to edit and easy to spot.

The file also carries the scene at the scale it was generated. That is convenient at import and worth confirming for every later one, because a second export can come from a differently drawn area.

Close view of a brick building beside a gravel road

2 Before export

2.1 How do you set the area and layers?

Draw the area with the neighbours included, then review each layer on its own. A building that sits oddly, a missing block or a water edge in the wrong place is easier to fix in the browser than in the engine. The fix takes a moment and saves a later argument.

Decide which layers the receiver needs. A game team may want buildings and ground without a vegetation band, while a planning team may want all three. Exporting just what is needed keeps the file smaller and the scene clearer.

2.2 What do you check in the preview?

Check the scene at the angle the receiver will use. A model that reads well from above can look thin at eye level, and a Unity scene is often viewed from inside. Orbit the site at ground level before exporting.

Check the scale against a known feature. A road width or a building footprint is enough to confirm that the scene has not been resized somewhere in the process. If the number looks wrong in the browser, it will look wrong in the engine.

Check the ground too. A terrain edge that sits above a road in the browser will sit above it in Unity, and the error is much harder to see once the camera is inside the scene.

3 Import into Unity

3.1 What about scale and origin?

Scale is the opening check. Import the file, place a known object beside it and compare. If the scene arrives at a different size, fix the import settings rather than scaling the model by eye, because an eyeballed correction is hard to repeat.

Origin is the second. A scene that sits far from the world origin can behave oddly when the camera moves, and the problem looks like a rendering fault. Check the pivot and the position before adding lights or scripts.

Aerial view of a campus with sports fields and trees

3.2 What about materials and lighting?

Materials arrive with the geometry, and their appearance depends on the lighting in the receiving scene. A model that looks correct in the browser can look flat in Unity until a light and an environment are set. That is normal, and it is worth saying so in the handover.

The materials are also a starting point rather than a finish. A game team will usually replace or tune them for its own pipeline, and the exported set gives that work a base.

Lighting is the larger variable. A neutral environment and a single directional light are enough to judge the geometry, and a full lighting setup comes later. Trying to match the browser view point for point is usually wasted effort.

4 What changes on import

4.1 What happens to names?

Object names can change, merge or disappear. A scene that had a clean layer structure in the browser can arrive as a handful of meshes with generic names. The geometry is intact and the organisation is not.

If names matter, plan for it. A short list of the objects the team will edit, agreed before export, keeps the rework small. The alternative is a session spent renaming objects that nobody planned to touch.

Grouping helps more than naming in some pipelines. If the engine team works by parent object, a clean grouping survives the trip better than a long list of individual names.

4.2 What happens to performance?

A district-scale scene can be heavy for a real-time engine. The geometry that reads well in a browser may need simplifying before it runs smoothly in a game. That work belongs to the receiving team, and it should be expected rather than discovered.

Deciding what to keep is part of the design. A blockout does not need every tree, and a review scene does not need every roof detail. Export the scene that matches the use.

If the scene is heavy, split it by district rather than by layer. Loading one part at a time keeps the view responsive and makes the boundary between areas explicit.

5 Handover discipline

5.1 What goes in the note?

The note names the source, the date, the area, the layers and the person who checked the import. It also says what the scene is for and what it does not carry. Five lines cover most of it.

Add the import settings that worked. A scale factor or an axis convention written down saves the next person a morning of trial and error, and it makes the handover repeatable.

Keep the note with the export rather than with the browser scene. The person who opens the file in Unity may never see the project folder where the scene was made.

5.2 How do you handle versions?

Give each export a clear name with a date. Keep the version that matches the current design and retire the others, or move them to an archive folder. A folder of files called final and final2 is a reliable way to send the wrong scene.

Preview an export in the GenAnywhere app and preview the scene before the opening export of a project.

6 When to stop

6.1 When is the scene enough?

The scene is enough for a blockout, a lighting test or a background context. It is enough when the game team needs shape and scale rather than detail. Many early prototypes never need more than that.

6.2 When do you rebuild?

Rebuild when the design has moved beyond the source. A proposal that has changed massing, height or access needs a new scene rather than a patched one. Rebuilding from the current area is usually faster than repairing a stale file.

6.3 When does another pipeline fit better?

Another pipeline fits when the work needs authored elements, measured geometry or a documented history. A design tool or a survey carries what the GLB does not. The export remains useful as context beside those sources.

Follow the export path in the GenAnywhere workflow.

7 FAQ

FAQ-1 Is this a Unity plugin?

No. The export is a general GLB that Unity can import, and there is no plugin to install. The workflow is a file handover rather than a live link, so changes made in the browser reach the engine through a new export. That suits a blockout stage and a team that plans its imports. It also means the engine copy does not update by itself.

FAQ-2 Which formats are available?

The export is a general GLB, and other formats depend on the workflow and the tools involved. The receiving application decides what it can read, so check that side before promising a format. The site lists the workflows the team supports, and those are the safest guide. Ask the receiving team what it already imports.

FAQ-3 Do textures come with it?

Materials come with the geometry, and their appearance depends on how the receiving tool handles them. Some teams keep them, some replace them and some rebuild the look from scratch. Treat the exported materials as a base and plan a short pass in the engine. Texture paths are the usual source of a missing surface.

FAQ-4 What about colliders?

Colliders are a game-engine concern and are not part of the exported scene. The importing team adds them where the scene needs collision, using the geometry as a guide. A blockout usually needs simple shapes rather than a collider for every surface, and that choice belongs to the engine team.

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.