Knowledge Base
Find answers to frequently asked questions about our services, products, and processes.
What 3D file formats does Augmento support?
Augmento supports all major 3D formats: GLTF/GLB (recommended for WebAR — lightweight, web-optimized), USDZ (Apple's AR format for iOS Quick Look), FBX and OBJ (for asset import and conversion), and standard image/video formats for textures and 2D overlays. Our pipeline automatically optimizes 3D models for mobile performance — compressing textures, reducing polygon counts, and generating LODs (Levels of Detail) for smooth 60fps rendering.
How does Augmento ensure AR experiences perform well on all devices?
Performance is critical for AR. Augmento uses several optimization strategies: automatic 3D model compression and LOD generation, adaptive quality scaling based on device GPU capabilities, lazy loading of assets (only downloading what the user needs), edge-cached CDN delivery for sub-100ms asset loading, efficient WebGL rendering pipelines, and frame rate monitoring with automatic quality fallbacks. We target 60fps on mid-range devices from the last 3 years.
How to optimize a large 3D real estate Gaussian Splat model to load faster on mobile browsers?
Gaussian Splatting models can be massive. Optimize by: reducing splat count through decimation while preserving visual quality, implementing level-of-detail (LOD) streaming that loads nearby detail first, compressing the point cloud data with quantization, and using progressive loading so users see a coarse preview within seconds while full detail streams in the background. Three.js and custom WebGL shaders are the primary tools for browser-based splat rendering.
What are the optimal export mesh settings for importing a 3D architectural model into Unity for VR?
For real-time VR performance in Unity: target under 500K polygons for the full scene, use FBX format for best Unity compatibility, bake high-poly detail into normal maps, limit texture atlases to 2K–4K resolution, and ensure proper UV unwrapping. Set the import scale to match Unity's 1 unit = 1 meter convention. For large properties, implement occlusion culling and LOD groups so only visible geometry renders each frame.
How to export a heavy architectural 3D rendering into a smoothly navigable VR walkthrough for clients?
Start by optimizing the architectural model: bake lighting into textures rather than computing it in real-time, reduce polygon counts using LOD (Level of Detail) techniques, and compress textures. Export as GLTF/GLB for web-based VR or FBX for Unity/Unreal Engine. In the VR runtime, implement teleportation-based navigation (rather than smooth movement which causes motion sickness) and ensure a consistent 72+ FPS for comfortable viewing.
How to divide a massive 3D BIM model into smaller sections to load faster on mobile AR applications?
Implement spatial partitioning: divide the BIM model into floor-based or zone-based chunks that load independently based on the user's GPS/AR-tracked position on the construction site. Use a location-triggered loading system — as the worker moves into a new section, the relevant 3D chunk streams in while distant sections unload from memory. Combine this with aggressive mesh decimation per chunk to stay within mobile memory limits (typically 1–2GB usable).