VU.CITY Logo
+44 (0)20 8432 7000
Facebook iconLinkedIn iconYouTube iconInstagram iconX (formerly Twitter) icon

Privacy policy | Cookie policy - Terms and conditions for: Private Sector | Public sector

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
© 2025 All rights reserved VU.CITY Limited.
VU.CITY Knowledge Base logo
Search...
  • VU.CITY Hub
    • Getting started
      • Introduction to VU.CITY Hub
      • Personal Drive and Project Drive
      • Purchasing a subscription
    • Account Management
      • Sign up to the Hub
      • Update account settings
      • Setting VU.CITY 3D environment
    • Organisation Management
      • Creating an organisation
      • Updating organisation settings
      • Organisation roles
      • Inviting members to join
      • Joining an organisation
      • Assigning subscriptions
      • Removing organisation member
    • Project management
      • Managing project and file access
      • Creating a project
      • Deleting a project
      • Updating project access
      • Launch a project in 3D
      • Upload files to project drive
      • Assigning a primary file
      • Update file access
    • Purchasing geometry
      • Using the coverage map
      • Formats available
      • Pricing
    • Release notes
      • Release notes - Hub
  • VU.CITY 3D
    • Getting started
      • Introduction to VU.CITY 3D
      • Navigating the VU.CITY 3D
      • Cloud session control
      • Request city model split
      • Reporting city model errors
    • Selecting your environment
      • Cloud vs Desktop
      • Network requirements and system - Cloud
      • System requirements - Desktop
      • Network configuration - Desktop
      • Network configuration - Cloud
    • Importing Models
      • Model requirements
      • Model optimisation
      • Geolocation
      • 3D model submission
      • Import workflows
    • File management
      • Merge
      • Auto and manual save files
    • Create
      • Create tool
      • Creating your first model
      • Exporting your model
    • ZTV
      • ZTV model requirements
      • ZTV analysis
      • Understanding the ZTV
    • Data
      • Data layers
      • Protected views
      • Timeline
      • Reporting missing Timeline data
      • Add your own point data
    • World scene tools
      • Measure
      • Style
      • Highlight
      • Hide
      • Tag
    • Cameras
      • Camera tool
      • Visibility states
      • Viewshed
      • Presenter
      • 180° and 360° Panoramic Views
      • Add your views from a CSV
    • Release notes
      • Release notes - VU.CITY Cloud
      • Release notes - VU.CITY Desktop
  • SiteSolve
    • Getting started
      • Introduction to SiteSolve
      • System and networking requirements
      • Data storage and file handling
    • Project management
      • Starting a project
      • Saving and loading project
      • Importing files
      • Importing settings
      • Exporting files and data
    • Setting up a site
      • Setting up a site boundary
      • Adjusting the site geometry
      • Exclusion zones
      • Managing height and zone tools
    • Create the geometry
      • Generating the geometry
      • Drawing blocks and footprints
      • Modifying existing building blocks
      • Modifying site geometry
    • The analysis
      • Navigate and analyse the project
      • Analyse data
    • Release notes
      • Release notes - SiteSolve
  • Plugins and Tools
    • VU.CITY plugins
      • Auto-Update service
      • Blender plugin
      • Revit plugin
      • SketchUp plugin
    • VU.CITY tools
      • 360 Viewer
  • FAQ
  1. Home
  2. VU.CITY 3D
  3. Importing Models
  4. Model requirements

Model requirements

Last updated: 23 December 2025 16:29 BST

VU.CITY supports models in FBX format (2011 or newer) and also supports OBJ files.

If your chosen CAD/BIM software cannot export to FBX, you can convert DXF, DAE, and 3DS files using this FBX converter from Autodesk.

Converting different CAD/BIM formats to FBX/OBJ can produce mixed results, so please review the following to understand what constitutes a good FBX/OBJ file.

Meshes and faces

VU.CITY supports meshes only. NURBS, curves, or surfaces must be converted into mesh to be rendered.

Faces within these meshes should either be triangles or quadrilaterals, as n-gons are not supported.

Models with multiple meshes can't be selected by the ZTV, object highlighter or camera tool. We suggest merging models into a single mesh/node for full compatibility.

Materials and textures

Models can include standard Autodesk materials; Revit and other app-specific materials are not supported. While VU.CITY can import UV-mapped models, this feature is best utilised witha software capable of integrating UV maps into materials, such as the latest version of 3ds Max.

File Size

While there is no theoretical file size limit, we recommend keeping files well below 128MB for performance reasons.

It is not necessary to join/collapse/merge/explode your geometry, though doing so can greatly improve rendering performance and reduce your file size. To further help keep your file size down, we recommend exporting only the externally visible geometry (i.e. not exporting interiors / furniture etc), and leaving out terrain / surrounding buildings (VU.CITY already contains both).

Geolocation

For the UK, geolocation should conform to the British National Grid (GBOS).

For Ireland, geolocation should conform to Irish Transverse Mercator (ITM).

All other supported locations use UTM projection.

Geolocating and georeferencing are not the same thing, and it's important for architects and BIM managers to understand the difference to get the best out of VU.CITY. Please see here to learn about the difference, and how to position/orient your model in a way that works for rendering formats like FBX and OBJ.

Elevation / AOD

A good practice is to extrude your model downwards so that the base of it sits at sea level (i.e. AOD 0). This helps prevent visible gaps between the building base and the VU.CITY terrain, particularly when the model is placed on a slope or hill, ensuring it does not appear to float above the terrain. This approach is especially useful in schemes involving landscaping. However, it may affect ZTV results. The part of the model below ground level is assigned a red band, which is not visible in the analysis. As a result, the ZTV output may appear to lack red tones corresponding to those hidden areas.

Previous:

Network configuration - Cloud

Did we answer your question?

Next up:

Model optimisation