Good evening, everyone.
I am a D5 Pro user with a perpetual license.
Given the reluctance of D5 support to resolve the issue of sharing projects with clients through the Virtual Tour (where, for some reason, only the Teams version can access this function), I was advised by support to present projects to my clients using VR headsets.
So, I decided to make this investment and purchased the Meta Quest 3, which is rated by many as the best VR device for the consumer range. Now, after using it for a few hours, I need to understand whether the issue lies with the D5 Launcher application or if my headset is defective. Therefore, I am asking the community whether they encounter the same problems:
The viewing fluidity is unsuitable for presenting projects; everything stutters, and after five minutes, it causes headaches.
With the right eye, I see shadows more prominently, while with the left eye, the image is much clearer and more defined.
The ability to move only by teleporting, rather than simply using the joysticks to navigate, is detrimental for older clients.
Therefore, I am asking support or the community if they are capable of providing me with a decent solution for presenting projects to my clients. After all, this software was created for this purpose, considering that we architects—if we truly deserve this title—should not need to use this software, as we should be able to foresee and design a space using our creative skills.
I look forward to the staff or the community providing a solution to this major issue.
Daniele
I apologize for the inconvenience this issue has caused. In VR mode, D5 will render two cameras in real time (corresponding to the left eye and the right eye), so it has higher requirements on the graphics card.
Some VR devices have the function of detecting whether the VR glasses are normally worn. When the VR glasses are not normally worn (placed upside down on the table, kept picking up and putting down, and so on), the frame rate will automatically drop, resulting in laggy performance. In addition, if the number of lights in a scene is very large, it may also cause lagging issue.
Are there a lot of light assets that were inserted in your File? You can try checking or enabling Statistics to see the exact amount.
Finally, please ensure that the driver version of the graphics card is updated, and do not turn on the high-resolution or high frame rate function of the VR device.
I think it’s very unlikely that the problem is with my GPU, also I had the same problem with the old PC that had an RTX 3080 with a 5900x and 64gb of RAM.
Thanks for these images. Indeed, your GPU is new and can certainly handle heavy tasks. Aside from that, your GPU Drivers are updated. Is it your first time using VR with D5 Render, or were you able to have this workflow even before Version 2.10? Since I would also like to confirm if this issue persisted in the previous version. Nevertheless, Ill be reporting this issue further to my team. Thank you.
If the device is primarily intended for D5 Render and the current issues render it unusable, a return might be the most practical option. While VR optimization is a key area of development for us, and we plan to introduce improvements in upcoming releases, we cannot provide an exact release date at this time.
Our community feedback indicates that the Oculus Rift and Rift S are the most commonly used VR devices with D5 Render. The Quest 1 has also shown relatively positive results, albeit with some known limitations. If you decide to exchange your device, we recommend looking into these models.
We deeply regret the difficulties you’re experiencing.
I think D5 needs to optimize the support for the new meta quest headsets since oculus rift and rift s stopped production around 2021. All the new headsets that are sold from meta now are in quest format , the ones being sold this year are in version 3. Most architecture firms I know in the southeast of the USA are using Quest 3 now .
