Architectural Visualization

Architectural visualization in Unity versus Unreal Engine represents a critical technology decision for professionals creating interactive, photorealistic digital representations of architectural designs before physical construction. This comparison addresses the fundamental choice between two dominant real-time rendering platforms that have transformed how architects, visualization studios, and AEC (architecture, engineering, and construction) professionals present designs to clients and stakeholders ⁴. The decision matters significantly because each engine offers distinct rendering philosophies, workflow integrations, and deployment capabilities that fundamentally impact project timelines, visual fidelity, hardware requirements, and the feasibility of delivering immersive experiences such as virtual reality walkthroughs, interactive configurators, and real-time design reviews ¹⁴. As the AEC industry increasingly adopts real-time visualization technologies to replace traditional static renderings, understanding the strengths, limitations, and optimal use cases for Unity and Unreal Engine has become essential for making informed technology investments.

Overview

The emergence of Unity and Unreal Engine as architectural visualization platforms represents a paradigm shift from traditional pre-rendered workflows to interactive, dynamic environments where lighting, materials, and camera positions can be modified instantaneously. Historically, architectural visualization relied on offline rendering engines that required hours or days to produce single images or short animations. The introduction of real-time engines—originally developed for gaming—enabled architects to create explorable environments where design decisions could be evaluated interactively. Unreal Engine, developed by Epic Games, brought its physically-based rendering (PBR) pipeline and cinematic quality tools to architectural applications, while Unity's flexible rendering architecture allowed optimization across diverse platforms from mobile devices to high-end workstations ²⁴.

The fundamental challenge these engines address is the tension between visual fidelity, interactivity, and accessibility. Traditional rendering produced photorealistic results but lacked interactivity; real-time engines enable stakeholders to navigate spaces freely, modify materials instantly, and experience designs at 1:1 scale in virtual reality ¹¹. Over time, both platforms have evolved significantly—Unreal Engine 5 introduced Lumen for real-time global illumination and Nanite for virtualized geometry ⁵⁸, while Unity developed its High Definition Render Pipeline (HDRP) to compete with Unreal's visual quality ²⁶. This evolution has democratized high-quality architectural visualization, making immersive design communication accessible to firms beyond large studios with specialized rendering infrastructure.

Key Concepts

Physically-Based Rendering (PBR)

Physically-based rendering is a shading methodology that simulates how light interacts with surfaces using real-world physical properties, utilizing texture maps for albedo (base color), metallic properties, roughness, and surface normals to achieve realistic material appearance ². Both Unity and Unreal Engine employ PBR workflows as their foundational rendering approach, ensuring materials behave predictably under different lighting conditions.

Example: A visualization studio creating an interior presentation for a luxury residential project uses PBR materials to represent marble flooring. They source high-resolution texture maps including a diffuse albedo map showing the marble's color variation, a roughness map defining polished versus honed areas, and a normal map capturing fine surface detail. When imported into Unreal Engine's Material Editor, these maps combine to create marble that reflects light accurately—glossy reflections in polished areas and diffuse scattering in honed sections—allowing the client to evaluate how natural daylight from floor-to-ceiling windows will interact with the specified flooring material throughout the day.

Real-Time Global Illumination

Real-time global illumination calculates indirect lighting—light bouncing between surfaces—dynamically without pre-computation, enabling immediate visual feedback when modifying light sources or materials ⁵. Unreal Engine 5's Lumen system provides this capability, dramatically reducing iteration time compared to traditional lightmapping workflows that require lengthy baking processes.

Example: An architectural firm designing a museum gallery uses Unreal Engine 5 with Lumen enabled. As the architect adjusts the size of a skylight in the engine, the indirect illumination on surrounding walls and artwork updates instantly, showing how reflected light from the polished concrete floor bounces onto adjacent surfaces. This immediate feedback allows the design team to optimize the skylight dimensions during a client meeting, testing various configurations in real-time rather than waiting hours for traditional lightmap baking between iterations—a process that would have required overnight rendering in previous workflows.

Datasmith Integration

Datasmith is Unreal Engine's import pipeline specifically designed for CAD and BIM software, maintaining material assignments, object hierarchies, and metadata when translating architectural models from applications like Revit, SketchUp Pro, and Rhino into the engine environment ¹. This integration streamlines the workflow between architectural design tools and visualization platforms.

Example: A commercial architecture firm working on a corporate headquarters design in Revit uses Datasmith to export their 45-story building model directly into Unreal Engine. The Datasmith importer preserves the hierarchical organization of building systems (structural, mechanical, architectural), maintains the glass curtain wall material assignments with their specified transparency and tint values, and retains object metadata including room numbers and area calculations. This preservation eliminates hours of manual material reassignment and allows the visualization team to immediately begin lighting and camera work rather than spending days reconstructing the scene organization.

High Definition Render Pipeline (HDRP)

Unity's High Definition Render Pipeline is a scriptable rendering framework optimized for high-fidelity graphics on high-performance hardware, providing advanced features comparable to Unreal Engine including volumetric lighting, screen-space reflections, and physically-based materials ²⁶. HDRP represents Unity's answer to demands for photorealistic architectural visualization.

Example: A visualization studio creating an interactive configurator for a residential development chooses Unity with HDRP to balance visual quality with web deployment requirements. They configure HDRP's mixed lighting mode, combining baked global illumination for static architectural elements (walls, floors, fixed cabinetry) with real-time lighting for dynamic elements (adjustable pendant lights, movable furniture). This hybrid approach achieves photorealistic indirect lighting quality while maintaining the 60fps performance necessary for smooth interaction when clients customize finishes and furniture arrangements through the web-based interface.

Blueprint Visual Scripting

Blueprint is Unreal Engine's node-based visual programming system that enables non-programmers to create interactive functionality, game logic, and user interfaces without writing traditional code ¹¹. This accessibility makes Unreal particularly attractive for architectural visualization teams with strong artistic skills but limited programming resources.

Example: An architectural visualization artist with no programming background uses Blueprint to create an interactive material selector for a hotel lobby presentation. They construct a Blueprint graph where clicking on the reception desk triggers a UI panel displaying three stone finish options (travertine, granite, marble). Each selection node connects to a "Set Material" function that swaps the desk's material in real-time. Additional Blueprint nodes control the camera, smoothly transitioning to a close-up view when the material panel opens and returning to the overview when closed—all created through visual node connections without writing a single line of C# or C++ code.

XR Interaction Toolkit

Unity's XR Interaction Toolkit provides cross-platform virtual and augmented reality functionality, supporting diverse hardware including Oculus Quest, HTC Vive, HoloLens, and mobile AR devices through a unified development framework ¹². This cross-platform capability enables architectural firms to deploy the same project across multiple XR devices.

Example: A mixed-use development firm creates a single Unity project using the XR Interaction Toolkit to showcase their project across multiple contexts. The same core visualization deploys as a VR walkthrough for investor presentations using Oculus Quest headsets, as a desktop interactive experience for public community meetings, and as a mobile AR application that overlays the proposed building onto the actual construction site when viewed through tablets. The toolkit's abstracted input system means interaction code (grabbing objects, teleporting, UI selection) works identically across all platforms, reducing development time compared to creating separate applications for each deployment scenario.

Nanite Virtualized Geometry

Nanite is Unreal Engine 5's virtualized geometry system that enables rendering of film-quality assets with billions of polygons by dynamically streaming and processing only visible detail, eliminating traditional polygon budgeting and manual LOD (level of detail) creation ⁸. This technology fundamentally changes how architectural models can be imported and displayed.

Example: A heritage preservation project requires visualizing a historically significant building with intricate stone facade ornamentation. The team photogrammetrically captures the facade, generating a mesh with 250 million polygons capturing every weathering detail and carved element. In traditional workflows, this model would require aggressive decimation and manual LOD creation to achieve real-time performance. With Nanite enabled in Unreal Engine 5, the full-resolution mesh imports directly and renders at 60fps on modern hardware—the system automatically determines which polygon detail is visible at any given camera distance and streams only necessary geometry, allowing stakeholders to examine fine carved details up close while maintaining performance during distant overview shots.

Applications in Architectural Visualization

Client Presentation and Marketing

Architectural firms leverage real-time engines to create compelling marketing materials and client presentations that communicate design intent more effectively than traditional static renderings. Unreal Engine's cinematic rendering capabilities and ray tracing features enable production of photorealistic still images and video flythroughs that rival offline renderers ³⁵. Major architectural firms including Zaha Hadid Architects have adopted Unreal Engine for generating marketing materials, utilizing its Sequencer tool to choreograph camera movements through spaces and its post-processing capabilities to achieve architectural photography aesthetics. These presentations allow clients to understand spatial relationships, material palettes, and lighting conditions before construction begins, reducing costly design changes during construction phases.

Interactive Real Estate Configurators

Residential and commercial developers deploy interactive configurators that enable prospective buyers to customize finishes, furniture, and layouts in real-time, significantly enhancing the sales process. Unity's cross-platform deployment capabilities make it particularly suitable for web-based configurators accessible without specialized hardware or software installation ⁴. A typical implementation allows buyers to select from approved flooring options, kitchen cabinet finishes, countertop materials, and appliance packages while seeing changes reflected immediately in the 3D environment. These configurators often integrate with backend systems to calculate pricing adjustments based on selections, generating customized quotes and even feeding selections directly into construction documentation systems, streamlining the path from design selection to construction execution.

Virtual Reality Design Reviews

High-value commercial projects increasingly utilize VR walkthroughs for immersive design reviews where stakeholders experience spatial relationships at 1:1 scale, identifying design issues difficult to perceive in traditional 2D drawings or desktop visualizations ¹¹. Firms like Gensler and HOK maintain dedicated Unreal Engine pipelines specifically for VR client reviews. During these sessions, architects, clients, and end-users don VR headsets to evaluate ceiling heights, circulation patterns, sightlines, and spatial adjacencies. A healthcare architecture firm might use VR to allow hospital administrators and medical staff to walk through a proposed surgical suite, verifying equipment placement, evaluating workflow efficiency, and identifying potential operational issues—feedback that informs design refinements before construction documents are finalized.

Augmented Reality On-Site Visualization

AR applications overlay digital architectural elements onto physical construction sites, enabling stakeholders to visualize proposed designs in their actual context. Unity's AR Foundation framework supports cross-platform AR development across iOS, Android, and HoloLens devices ¹². A commercial developer might use tablet-based AR during community approval processes, allowing neighbors and planning commissioners to stand on the actual site and view the proposed building superimposed at correct scale and position within the existing streetscape. This contextualization helps stakeholders understand massing, height relationships, and visual impact more intuitively than traditional renderings or physical models, often facilitating more informed approval decisions and reducing community opposition based on misunderstandings of project scale.

Best Practices

Early Performance Budgeting

Establishing performance targets and polygon budgets at project inception prevents costly optimization work late in development. Professional workflows define target frame rates (typically 60fps for desktop, 90fps for VR), maximum draw calls, and polygon counts per scene before asset creation begins ⁸.

Rationale: Architectural models exported from CAD software often contain millions of polygons far exceeding real-time rendering capabilities. Addressing performance reactively after scene assembly requires time-consuming asset rework.

Implementation Example: A visualization studio beginning a mixed-use development project establishes a performance budget: 5 million triangles total scene complexity, maximum 2,000 draw calls, targeting 60fps on NVIDIA RTX 3070 hardware. They communicate these constraints to the architectural team, requesting simplified geometry exports that exclude non-visible structural elements. The team implements hierarchical LOD systems during asset preparation—building facades use high-detail meshes within 50 meters, medium detail from 50-150 meters, and simplified geometry beyond 150 meters. This proactive approach ensures the final presentation maintains smooth performance without emergency optimization that could compromise visual quality.

Modular Scene Organization

Structuring projects with modular, reusable components and clear hierarchical organization facilitates team collaboration, enables efficient version control, and supports iterative design changes ¹⁴.

Rationale: Architectural projects involve multiple team members working simultaneously and require incorporating design changes as architectural plans evolve. Monolithic scene files create merge conflicts and make selective updates difficult.

Implementation Example: A large hospital visualization project organizes assets into modular prefabs/blueprints: "PatientRoom_Standard," "PatientRoom_ICU," "NurseStation_Type_A." Each module exists as a separate file with its own version history. The main hospital scene references these modules, allowing the interior designer to refine patient room lighting while the architect simultaneously adjusts the building envelope without file conflicts. When the architectural team revises the standard patient room layout, the visualization team updates only the "PatientRoom_Standard" module, and all 200 instances throughout the hospital automatically reflect the changes—a workflow impossible with monolithic scene construction.

Hybrid Lighting Strategies

Combining baked (pre-calculated) and real-time lighting optimizes the balance between visual quality and performance, using baked global illumination for static architecture and real-time lighting for dynamic elements ²⁵⁶.

Rationale: Fully real-time lighting provides maximum flexibility but may sacrifice subtle indirect illumination quality or performance. Fully baked lighting achieves superior quality but prevents runtime modifications. Hybrid approaches capture advantages of both.

Implementation Example: A retail visualization project in Unity HDRP marks all architectural elements (walls, floors, ceilings, fixed millwork) as "Lightmap Static" and bakes high-quality global illumination overnight, capturing subtle color bleeding from materials and soft shadows. Movable elements (furniture, products, adjustable display lighting) use real-time lighting. This configuration allows the retail client to reconfigure product displays and adjust accent lighting during presentations while maintaining photorealistic indirect illumination on architectural surfaces—achieving visual quality approaching offline renderers while preserving interactivity essential for design exploration.

Platform-Specific Optimization Passes

Implementing dedicated optimization iterations for each target platform (desktop, VR, mobile, web) ensures acceptable performance across deployment contexts rather than assuming a single configuration suits all platforms ¹¹¹².

Rationale: Performance requirements vary dramatically across platforms—VR demands 90fps stereoscopic rendering, web deployment faces download size constraints, mobile devices have limited processing power. A desktop-optimized project will fail on other platforms without specific optimization.

Implementation Example: A residential development configurator targets three platforms: high-end desktop for sales center installations, WebGL for remote client access, and mobile tablets for on-site presentations. The team creates three build configurations: the desktop version uses full-resolution textures, real-time reflections, and complex post-processing; the WebGL build reduces texture resolution by 50%, disables screen-space reflections, and limits simultaneous light sources; the mobile build further simplifies geometry LODs, uses baked lighting exclusively, and disables volumetric effects. Each platform receives dedicated testing and profiling, ensuring the 60fps target is met across all deployment scenarios rather than discovering performance issues after launch.

Implementation Considerations

Engine Selection Based on Project Requirements

The choice between Unity and Unreal Engine should align with specific project priorities including target platforms, team skills, visual fidelity requirements, and deployment contexts ²³⁴. Unreal Engine excels in high-fidelity desktop and VR presentations where visual quality is paramount, offering superior out-of-the-box photorealism through Lumen, Nanite, and integrated Quixel Megascans material libraries ⁵⁸. Unity provides greater cross-platform flexibility, particularly for web deployment, mobile AR applications, and projects requiring extensive custom programming ¹².

Example: A visualization studio evaluating engines for two concurrent projects makes differentiated choices: for a luxury residential tower requiring photorealistic VR walkthroughs for high-net-worth buyers, they select Unreal Engine 5, leveraging Lumen for dynamic lighting and Nanite for detailed architectural ornamentation without manual optimization. For a commercial development requiring a web-based configurator accessible to thousands of potential tenants without software installation, they choose Unity with URP, prioritizing WebGL deployment capabilities and smaller build sizes over maximum visual fidelity.

Workflow Integration with Architectural Software

Evaluating how each engine integrates with existing architectural design tools significantly impacts iteration speed and project efficiency ¹⁴. Unreal's Datasmith plugin provides superior direct import from Revit, SketchUp Pro, and Rhino, maintaining material assignments and object hierarchies ¹. Unity's workflow typically requires intermediate FBX export, potentially losing metadata and requiring manual material reassignment.

Example: An architecture firm working primarily in Revit with frequent design iterations selects Unreal Engine specifically for Datasmith integration. When the structural engineer modifies column locations in the Revit model, the visualization team re-exports through Datasmith, and Unreal automatically updates only changed geometry while preserving custom lighting, camera sequences, and interactive elements added in the engine. A comparable Unity workflow would require manually identifying changed elements and reassigning materials, consuming hours per iteration—a critical consideration during active design-development phases with weekly model updates.

Team Composition and Skill Requirements

Engine selection should consider existing team capabilities and hiring market realities ⁹¹¹. Unreal's Blueprint visual scripting enables teams with strong artistic skills but limited programming resources to create sophisticated interactive experiences ¹¹. Unity projects typically require C# programming knowledge for comparable functionality, but Unity developers are more abundant in many markets due to Unity's broader adoption across gaming, simulation, and enterprise applications.

Example: A small architectural visualization studio with three talented 3D artists but no dedicated programmer chooses Unreal Engine, enabling the artists to implement interactive material selectors, animated building sections, and VR teleportation systems through Blueprint without hiring programming staff. Conversely, a larger AEC technology firm with existing C# developers supporting internal tools selects Unity, leveraging their programming team to create custom import pipelines, integrate with proprietary project management systems, and develop advanced configurator logic that extends beyond visual scripting capabilities.

Licensing and Cost Structures

Understanding licensing implications affects project budgets and long-term sustainability ⁷⁹. Unity requires Pro licenses ($2,040/year per seat) for projects exceeding revenue thresholds and to remove splash screens—costs that accumulate with team size ⁹. Unreal Engine charges 5% royalty on gross revenue above $1 million, but this is typically waived for architectural visualization work, making Unreal more cost-effective for visualization-focused studios ⁷.

Example: A visualization studio with eight artists evaluating five-year costs calculates Unity Pro licensing at $81,600 (8 seats × $2,040 × 5 years) versus Unreal Engine at $0 for architectural visualization work. This $81,600 difference influences their decision toward Unreal, particularly since their revenue model (fixed-price visualization services rather than per-view licensing) means they'll never trigger Unreal's royalty threshold. Conversely, a software company developing a commercial real estate platform charging subscription fees might prefer Unity's predictable per-seat costs over uncertainty about whether their revenue model might trigger Unreal's royalty obligations.

Common Challenges and Solutions

Challenge: Managing Polygon-Heavy CAD Imports

Architectural models exported from CAD and BIM software often contain millions of polygons including non-visual elements like structural annotations, mechanical systems, and construction details, far exceeding real-time rendering budgets and causing severe performance degradation ¹⁸.

Solution:

Implement aggressive mesh optimization workflows before engine import. Use CAD software export settings to exclude non-visual elements (dimensions, annotations, hidden layers). Apply mesh decimation tools like Simplygon or Unity's Mesh Simplifier to reduce polygon counts while preserving visual fidelity—targeting 70-90% reduction for distant elements. Create hierarchical LOD systems with 3-4 detail levels: full detail within 20 meters, 50% reduction at 20-75 meters, 75% reduction at 75-200 meters, and simplified proxies beyond 200 meters. For Unreal Engine 5 projects, leverage Nanite virtualized geometry for hero assets requiring extreme detail, while still optimizing secondary elements ⁸. Establish import protocols requiring architectural teams to provide "visualization-ready" geometry exports with appropriate simplification rather than construction-documentation models containing unnecessary complexity.

Challenge: Balancing Lighting Quality with Iteration Speed

Achieving photorealistic lighting quality often requires lengthy lightmap baking processes—sometimes hours for complex scenes—creating tension between visual fidelity and the rapid iteration necessary during design development ²⁵⁶.

Solution:

Maintain parallel lighting configurations optimized for different workflow stages. Create a "working" lighting setup using real-time or low-resolution baked lighting (512-1024 lightmap resolution) that bakes in minutes, enabling rapid design iteration and client feedback sessions. Develop a separate "presentation" lighting configuration with high-resolution lightmaps (2048-4096 resolution) and additional quality settings, baked overnight or during non-working hours for final presentations and marketing materials ²⁶. For Unreal Engine 5 projects, leverage Lumen for working iterations, providing immediate feedback without baking, then optionally supplement with baked lighting for final delivery if Lumen quality proves insufficient for specific scenes ⁵. Implement automated build systems that trigger high-quality lighting bakes during off-hours, ensuring presentation-ready builds are available each morning without consuming artist time waiting for baking processes.

Challenge: Version Control with Binary Engine Files

Both Unity and Unreal Engine use binary file formats for scenes and assets, creating significant version control challenges—merge conflicts are difficult to resolve, file sizes strain repository systems, and simultaneous editing by multiple team members risks data loss ⁴.

Solution:

Implement Git LFS (Large File Storage) or Perforce to handle large binary assets efficiently, preventing repository bloat. Establish strict asset ownership protocols where specific team members "own" particular scene sections or asset categories, reducing simultaneous editing conflicts. Structure projects with maximum modularity—separate scene files for building exterior, each floor, landscape, and interior zones—allowing team members to work in different files simultaneously ¹. Use Unity's prefab system or Unreal's level streaming to reference shared assets rather than duplicating them across scenes. Implement clear check-out/check-in procedures for shared resources, using project management tools (Trello, Jira) to communicate who is actively editing which assets. Schedule regular integration sessions where team members merge work in coordinated fashion rather than continuous asynchronous merging. For critical milestones, create tagged repository snapshots enabling rollback if integration issues arise.

Challenge: Client Hardware Limitations

Visualization projects optimized for high-end development workstations often perform poorly on client hardware, creating disappointing presentation experiences when clients cannot achieve acceptable frame rates on their systems ⁴⁹.

Solution:

Survey client hardware specifications during project kickoff, establishing minimum target specifications (GPU model, RAM, CPU) that presentations must support. Create scalable quality presets (Low, Medium, High, Ultra) that adjust texture resolution, shadow quality, post-processing effects, and lighting complexity, allowing the application to run acceptably across hardware ranges. Implement automatic quality detection that benchmarks client hardware on first launch and selects appropriate preset. Provide clear minimum specification documentation with project deliverables, including specific GPU models and driver version requirements. For critical presentations, offer to provide rental hardware (gaming laptops with appropriate GPUs) ensuring consistent experience regardless of client equipment. Consider cloud streaming solutions like NVIDIA GeForce NOW or Parsec that render on remote servers and stream video to client devices, eliminating client hardware constraints entirely for web-based presentations—particularly valuable for WebGL deployments where browser performance varies significantly.

Challenge: Material Translation from Architectural Specifications

Architectural specifications describe materials using industry terminology (paint colors, stone types, fabric names) that don't directly translate to PBR texture maps, creating ambiguity about how materials should appear in real-time engines ²⁴.

Solution:

Develop a material library workflow that bridges architectural specifications and PBR implementation. Create a studio material database cataloging common architectural materials (paint colors, wood species, stone types, metals, fabrics) with corresponding PBR texture sets, manufacturer information, and reference photography. When specifications reference "Benjamin Moore White Dove OC-17," the database provides the corresponding albedo color value and appropriate roughness/metallic parameters. For custom or unusual materials, implement a material approval process: create PBR material interpretations, render test swatches under standard lighting conditions, and obtain client approval before applying throughout the scene. Partner with material manufacturers (tile companies, paint manufacturers, fabric suppliers) to obtain or create PBR texture sets for their products, building a library that ensures accuracy. Use physical material samples during client meetings alongside digital representations, acknowledging that screen color accuracy limitations mean digital materials approximate rather than perfectly replicate physical materials—managing client expectations about the inherent differences between physical and digital material representation.

References

1. Epic Games. (2022). Datasmith Overview for Unreal Engine. https://docs.unrealengine.com/5.0/en-US/datasmith-overview-for-unreal-engine/
2. Unity Technologies. (2025). High Definition Render Pipeline. https://docs.unity3d.com/Manual/high-definition-render-pipeline.html
3. Epic Games. (2021). Unreal Engine 5 is Now Available in Early Access. https://www.unrealengine.com/en-US/blog/unreal-engine-5-is-now-available-in-early-access
4. Unity Technologies. (2025). Architecture, Engineering & Construction Solutions. https://unity.com/solutions/architecture-engineering-construction
5. Epic Games. (2022). Lumen Global Illumination and Reflections in Unreal Engine. https://docs.unrealengine.com/5.0/en-US/lumen-global-illumination-and-reflections-in-unreal-engine/
6. Unity Technologies. (2021). High Definition Render Pipeline Package Documentation. https://docs.unity3d.com/Packages/com.unity.render-pipelines.high-definition@12.0/manual/index.html
7. Epic Games. (2021). Forging New Paths for Game Developers on the Epic Games Store. https://www.unrealengine.com/en-US/blog/forging-new-paths-for-game-developers-on-the-epic-games-store
8. Epic Games. (2022). Nanite Virtualized Geometry in Unreal Engine. https://docs.unrealengine.com/5.0/en-US/nanite-virtualized-geometry-in-unreal-engine/
9. Unity Technologies. (2025). Unity Pro. https://unity.com/products/unity-pro
10. Unity Technologies. (2025). Shader Graph. https://docs.unity3d.com/Manual/shader-graph.html
11. Epic Games. (2025). VR Development in Unreal Engine. https://www.unrealengine.com/en-US/vr
12. Unity Technologies. (2025). XR Interaction Toolkit. https://docs.unity3d.com/Manual/com.unity.xr.interaction.toolkit.html