Blender 3.6 and Blender 4.0 have conflicting version requirements for the OpenVDB library, making it impossible to install both Blender versions concurrently with their respective OpenVDB dependencies. When attempting to install Blender 3.6 and Blender 4.0 on the same system, I encountered an issue with the OpenVDB library dependencies: - Blender 3.6 requires openvdb version < 11. - Blender 4.0 requires openvdb version = 11. Due to these conflicting requirements, it is not possible to have both Blender versions installed simultaneously since each version of Blender depends on a different, mutually exclusive version of OpenVDB. This incompatibility prevents users who rely on both versions for different projects from maintaining a dual setup. Reproducible: Always Steps to Reproduce: 1. Attempt to install Blender 3.6 with openvdb. 2. Attempt to install Blender 4.0 with openvdb. 3. Notice the conflict in openvdb versions, resulting in an installation failure for one or both Blender versions. Actual Results: The installation process fails due to conflicting OpenVDB version requirements between Blender 3.6 and Blender 4.0, making it impossible to install and use both versions simultaneously. Expected Results: Users should be able to install both Blender 3.6 and Blender 4.0 on the same system with their respective OpenVDB dependencies without conflicts. Ideally, there should be a way to handle the dependency differences, such as: - Supporting multiple versions of OpenVDB concurrently. - Allowing Blender to dynamically link to different versions of OpenVDB as needed. This issue significantly impacts users who require multiple Blender versions for compatibility with different projects or plugins. Resolving this will greatly improve user experience and flexibility in managing Blender installations.
