2 Revit 2015 2016Programme Auf Einem Rechner

Calculate system requirements and compatibility for running Revit 2015 and 2016 simultaneously on one computer

Comprehensive Guide: Running Revit 2015 and 2016 on the Same Computer

Installing and running two different versions of Autodesk Revit (2015 and 2016) on the same computer is a common requirement for architecture, engineering, and construction professionals who need to maintain compatibility with various project files and collaborators. This comprehensive guide explores the technical requirements, potential challenges, and best practices for successfully operating both Revit versions simultaneously.

System Requirements Overview

Before attempting to install both versions, it’s crucial to understand the system requirements for each:

Requirement	Revit 2015	Revit 2016	Combined Recommendation
Operating System	Windows 7 SP1 64-bit, 8.1 64-bit	Windows 7 SP1 64-bit, 8.1 64-bit, 10 64-bit	Windows 10/11 64-bit (most stable)
CPU	Intel® Pentium®, Xeon®, or i-Series 3.0 GHz+	Intel® Xeon® or i-Series 3.0 GHz+	Quad-core 3.0 GHz+ (8+ cores recommended)
RAM	4 GB (8 GB recommended)	4 GB (8 GB recommended)	16 GB minimum (32 GB for large projects)
Storage	5 GB free space	5 GB free space	20 GB SSD minimum (50 GB recommended)
Graphics	1 GB GPU, DirectX® 11	1 GB GPU, DirectX® 11	4 GB GPU, DirectX 12 (workstation class)
Display	1280×1024 with true color	1280×1024 with true color	1920×1080 minimum (4K recommended)

Technical Considerations for Parallel Installation

1. Installation Order Matters: Always install older versions first (Revit 2015 before 2016). Autodesk products often share components, and newer versions may overwrite files that older versions depend on.
2. Separate Installation Paths: While the default installation paths are typically different (e.g., C:\Program Files\Autodesk\Revit 2015 and C:\Program Files\Autodesk\Revit 2016), you can specify custom paths during installation to better organize your system.
3. Shared Components Conflict: Both versions will install some shared components like material libraries and family templates. These will typically be stored in shared locations (e.g., C:\ProgramData\Autodesk\RVT 2015 and C:\ProgramData\Autodesk\RVT 2016).
4. License Management: You’ll need separate licenses for each version. Autodesk’s license manager can handle multiple product versions, but you may need to switch licenses when launching different versions.
5. File Association: Windows will typically associate .rvt files with the last installed version. You can manually change this in Windows settings or use Revit’s “Open with” option.

Performance Optimization Techniques

Running two resource-intensive applications simultaneously requires careful system optimization:

• RAM Allocation: Close other memory-intensive applications when running both Revit versions. Consider creating separate Windows user profiles for each Revit version to isolate memory usage.
• CPU Affinity: Use Task Manager to set processor affinity for each Revit process, assigning different cores to each version to prevent competition.
• Graphics Settings: In each Revit version’s graphics settings, adjust the graphics mode to “DirectX” (rather than “Software”) and enable hardware acceleration.
• Project Caching: For large projects, use Revit’s “Worksharing Monitor” to manage local files efficiently when switching between versions.
• Temp File Management: Configure each version to use separate temp file locations to prevent conflicts (Options → File Locations).

Common Issues and Solutions

Issue	Cause	Solution
One version fails to launch	Missing shared components or registry conflicts	Repair installation via Control Panel or reinstall in correct order
Performance degradation	Insufficient RAM or CPU resources	Close other applications, upgrade hardware, or use one version at a time
File corruption when saving	Version compatibility issues with shared libraries	Use “Save As” with explicit version selection, maintain separate template files
Add-ins not working in both versions	Add-in installed for wrong version or API conflicts	Install add-ins separately for each version, check developer documentation
License errors	License manager conflict between versions	Use Autodesk License Manager to specify versions, or use network licensing

Best Practices for Long-Term Management

To maintain a stable dual-version Revit environment:

1. Regular Updates: Keep both versions updated with the latest service packs and hotfixes from Autodesk. Check for updates monthly.
2. Separate Project Folders: Maintain distinct folder structures for projects worked on in each version to prevent accidental file version conflicts.
3. Document Versioning: Clearly label all project files with the Revit version used (e.g., “ProjectX_2015.rvt” and “ProjectX_2016.rvt”).
4. Backup Strategies: Implement automated backups for both versions’ configuration files (found in %APPDATA%\Autodesk\Revit).
5. Virtualization Option: For critical projects, consider running one version in a virtual machine to completely isolate the environments.
6. User Training: Educate all team members on the proper procedures for switching between versions to prevent data loss or corruption.

Alternative Solutions

If maintaining two versions proves too challenging, consider these alternatives:

• Cloud Collaboration: Use Autodesk’s BIM 360 or similar platforms to maintain separate project environments without local dual installations.
• Dedicated Workstations: Maintain separate physical or virtual machines for each Revit version in your office.
• Version Conversion Services: Use third-party services to convert files between versions when needed, rather than maintaining both locally.
• Containerization: Advanced users can explore Docker containers to run each version in isolated environments.

Industry Standards and Compliance

The practice of running multiple BIM software versions is common in the AEC industry due to:

• Project Longevity: Many construction projects span multiple years, during which software versions may change.
• Client Requirements: Some clients mandate specific software versions for consistency across consultants.
• Regulatory Compliance: Certain building codes or standards may reference specific software versions in their documentation.
• Collaboration Needs: Different disciplines (architects, engineers, contractors) may standardize on different versions.

Industry Resources:

For official Autodesk guidance on running multiple versions, refer to:

• Autodesk Revit Knowledge Network – Official support documentation
• National Institute of Building Sciences (NIBS) – BIM standards and interoperability guidelines
• BIMForum – Industry best practices for BIM implementation

Future-Proofing Your BIM Workflow

As the AEC industry evolves, consider these strategies to reduce version dependency:

1. Adopt IFC Standards: Industry Foundation Classes (IFC) provide a neutral format for exchanging BIM data between different software versions and platforms.
2. Implement Model Checking: Use tools like Solibri Model Checker to validate models regardless of the creating software version.
3. Cloud-Based Collaboration: Platforms like Autodesk Construction Cloud reduce the need for specific local software versions.
4. Standardize on LTS Versions: When possible, standardize on Long-Term Support versions of software to minimize version proliferation.
5. Document Version Policies: Create clear office policies for software version usage and file exchange protocols.

Running Revit 2015 and 2016 on the same computer is entirely feasible with proper planning and system configuration. By following the guidelines in this comprehensive guide, AEC professionals can maintain productivity while ensuring compatibility with various project requirements. Remember that hardware capabilities play a crucial role in the success of this setup, so invest in quality components to support your BIM workflows.