Skip to content
Model VistaModel Vista Web Documentation

Compatibility and troubleshooting

Model Vista Web supports glTF 2.0 content, Draco-compressed GLB geometry, Model Vista Create INNOWORKS_configurables schema versions 1 and 2, embedded PNG and JPEG images, asset and States thumbnails, and version-2 turntable-offset sidecars.

It reconstructs common glTF, URP, and HDRP material properties as Three.js standard or physical materials. It preserves unknown shader-state values for project-specific mappings.

Unity and HDRP shaders cannot run directly in WebGL. The viewer maps known physically based properties to its Web renderer, so a Web presentation can differ from Unity or the desktop Model Vista runtime. Local HDRP reflection-probe blending has no exact Web equivalent and is not rendered as a local probe.

Camera States drive the Web viewer camera. Metadata and reflection-probe records are preserved with the loaded model even when the browser has no visual equivalent.

Marker-based augmented reality requires Model Vista Web to run over HTTPS, or on localhost during local development. The browser and device must provide a usable camera through the browser camera API.

The bundled marker works without preparing another image. A custom marker must be a PNG, JPEG, WebP, or SVG image of at least 640 × 480 pixels. Model Vista Web center-crops custom images to a 4:3 tracking area and reports whether the image quality is Good, Fair, or Poor.

  • Confirm that the main file is .glb, .gltf, or .fbx.
  • For .gltf, select its .bin buffers and texture files together with the main file.
  • Open Properties > Analyze and address validator errors.
  • If the asset declares a newer Model Vista schema, treat the compatibility warning as an indication that not every feature can be reproduced.
  • Open System > User libraries and use the reconnect action.
  • Grant read access again if the browser cleared the folder permission.
  • If browser storage was cleared, add the folder again.
  • A browser without persistent directory access uses a browser-local copy; clearing site data removes that copy from the viewer but does not delete the original folder.
  • Open the deployed HTTPS application. A plain LAN http:// address cannot start camera AR; use HTTPS or localhost.
  • Allow camera access when the browser asks. If access was denied previously, restore the site’s camera permission and try again.
  • Confirm that the device has an available camera and that another application is not preventing access to it.
  • Reload Model Vista Web if the AR runtime fails to load or takes too long to start.

The marker is not detected or tracking is lost

Section titled “The marker is not detected or tracking is lost”
  • Keep the complete marker visible, flat, well lit, and free of glare.
  • Point the camera at the marker and hold the device steady until the status changes to Tracking.
  • For a custom marker, prefer distinct, asymmetric details and use the displayed quality rating as guidance.
  • If you printed the marker, use Actual Size or 100% scale and enter its measured width in Printed marker width.
  • If tracking is lost, point the camera at the marker again. The viewer briefly preserves the last pose while it attempts to recover.
  • With Auto fit enabled, 100% fits the loaded scene to the marker. Use Initial model size before starting or the minus and plus controls during AR to adjust it from 25% to 400%.
  • For physical scale, turn off Auto fit. One glTF unit then equals one metre, and the value in Printed marker width calibrates the scene.
  • Confirm that Printed marker width matches the marker’s physical width. The supported range is 50–180 mm.

For the complete procedure, see Use marker-based augmented reality.

  • Enter a prompt; the submission button remains disabled when the prompt is empty.
  • Select Sign in, use a verified account, and complete the reCAPTCHA.
  • If the viewer reports that setup is required, open the account dialog and finish setup.
  • Check the daily credit balance and the cost shown on the button.
  • Reload the page and sign in again if the session expired.
  • Confirm that a model is loaded before enhancing the current 3D view.

Open System and select Reset viewer settings if panels, camera projection, lighting, or background settings produce an unexpected view. Reloading the page clears the current scene and temporary AI results but keeps browser-saved preferences and user libraries unless site data was removed.