Tips & Tricks to help Optimize your files for Virtual Reality
How smoothly and successfully your model appears in virtual reality is affected by a series of items, including but not limited to hardware and model size, which in turn affect your frame rates.
Our goal is to provide the smoothest in VR experience and always have you viewing your model at 90 frames per second but if upon entering your model you notice that it is "blurry" or shuddery, here are some external factors to check for:
1. Check and confirm that your computer has the necessary hardware to run virtual reality software. Our recommended computer specs are posted here.
2. Check and confirm that all your virtual reality headset cables are plugged in. This can seem an obvious step, but with use, cables can become loose and not transfer data properly. If using an HTC Vive without the sync cable, consider adding the cable for stability.
3. If you're using a laptop, we strongly recommend keeping it plugged into the charger whenever possible. Powering a VR experience is very intensive, and relying entirely on battery power is known to cause degraded performance.
Review the model you are using for possible optimization. Here are some options for optimizing your model:
1. Turning off pieces of the model that are "nice-to-haves". For example, trees, people, and cars can make a 3D file grow quite large and lower frame rates very quickly.
2. If you are using 3D components from product manufacturers, check them for excess details. For instance, chairs, windows, kitchens that can be downloaded from the internet are often modeled in very high detail including components such as highly detailed tiny screws. These are useful for drawing sets, but not always necessary for seeing in virtual reality.
3. Consider bringing in a smaller version of the 3D model. For example, if you have a 10 story building or a 10-mile campus massing model, trimming down the area to 5 stories or a few blocks can quickly improve the quality in-VR.
At IrisVR, we are constantly working on optimizing our core technology so that you do not need to make little to no adjustments to your model, but as we're constantly pushing the boundaries of what hardware is capable of, these tips are designed to help ensure the highest degree of success possible given current constraints.
Filetype Specific Suggestions
Visibility & Graphics - V/G settings for the selected 3D view have some features that Prospect will respect when bringing your file into VR. Using the V/G menu to hide items is a good way to eliminate geometry that isn't critical to your VR experience. Anything hidden in this menu for the current 3D view you bring into Prospect will be omitted from the export.
Section Box - The section box feature that can be enabled via the properties tab in Revit is an excellent way to limit the scope and overall geometry being imported into Prospect.
Properties Tab - Updated Prospect plugins have enabled the ability to customize the metadata fields that are brought into VR. We encourage users to make use of this properties tab in our plugin exporter, to eliminate any fields that aren't especially useful for your needs. This not only helps reduce the overall data being imported to Prospect but also enables you to scroll through fewer metadata fields to get to what's important to you.
Selection Tree - The selection tree in Navisworks is immensely useful when preparing a file for VR with Prospect. Using the selection tree to hide items is a good way to eliminate geometry that isn't critical to your VR experience. Anything hidden in this menu will be omitted from the export.
Section Box - The section feature that can be enabled in Navisworks is perhaps the primary way to limit the overall geometry being brought in. For large and complex models, this could be a necessity - particularly if Quest is your intended headset for interacting with your files.
Properties Tab - We encourage users to make use of the properties tab in our plugin exporter. eliminate any fields that aren't especially useful for your needs. Not only will this help reduce the overall data being imported to Prospect, but it also enables you to import and view only fields that are useful for your design review in Prospect.
1. Turning off pieces of the model that are "nice-to-haves". For example, trees, people, and cars can make a 3D file grow quite large and lower frame rates very quickly. Alternatively, consider reducing and/or replacing these items with low poly options, or using a tool like Skimp to help with the reduction of poly counts for the content in your SketchUp models.
2. Consider how many instances of an object there are in a scene, and consider reducing. If you're working on a project where there are numerous rooms with the same or similar layouts, consider having "typicals" that are indicative of how the rest of the rooms would be laid out, but allow you to leave some rooms unfurnished.