Visiofy Articles

Did Your Visiofy Model Fail to Process or Look Off? Here’s What Usually Helps

Written by Visiofy | Mar 24, 2026 8:12:00 AM

Why Visiofy Models Fail to Process or Look Incorrect

Visiofy converts architectural models into browser-based, walkable virtual spaces. To ensure smooth performance for both creators and viewers, models need to meet certain technical requirements.

When something goes wrong, it’s rarely random. Almost all processing failures or visual issues fall into one of three categories outlined below.

Scenario 1: Too Many Triangles or Polygons

Maximum supported limit: 1 million triangles/polygons

If your model fails to process entirely, this is the most common reason.

Highly detailed elements—especially plants, trees, grass, and vegetation assets—can dramatically increase polygon count. Even a visually simple garden can push a model over the limit.

Scenario 2: Missing Textures in the Model

What usually helps

  • Hide or remove vegetation before exporting

  • Exclude decorative assets that are not essential for the walkthrough

  • Use simplified versions of furniture or landscaping objects

  • Export only the building and core surroundings

Once the polygon count is under 1 million, the model should process normally in Visiofy.

Scenario 3: Wrong File Format

If your model loads but surfaces show a “missing texture” pattern, the geometry is fine—but the texture files were not included.

This most commonly happens with Chief Architect and Archicad exports, where textures are stored externally instead of embedded automatically.

What usually helps

  • Make sure all texture image files are included when exporting

  • Keep texture files in the same folder as the exported model

  • Avoid renaming texture files after export

  • Re-export the model and upload it again to Visiofy

When textures are correctly linked, materials will display as expected in the Visiofy viewer.

How to Avoid Model Processing Issues in the Future

Visiofy currently supports only the following file formats:

  • .obj

  • .glb

  • .dae

Uploading any other format will result in weird-looking results, processing errors or failed uploads.

What usually helps

  • Double-check your export settings before uploading

  • Use the correct export format supported by your design software (here's a cheat sheet)

  • If needed, re-export the model using a supported format

Using the correct file format ensures Visiofy can properly interpret geometry, materials, and scale.

How to Avoid Model Processing Issues in the Future

To minimize errors and re-uploads, it helps to follow a simple checklist before exporting:

  • Keep polygon count under 1 million

  • Remove or hide vegetation and high-detail assets

  • Include all texture files if they are not embedded

  • Export only in .obj, .glb, or .dae formats

  • Test exports early when working with new project templates

These steps make your workflow faster and your client-ready virtual spaces more reliable.

Related reads

How to Make Your Sketchup Models Look Perfect On Visiofy

What is Z-fighting, Why Does it Occur and How to Fix It?

Cheat Sheet: Which Export format Works for Which CAD Software on Visiofy 

Frequently asked questions