question

Marco Baccalaro avatar image
0 Likes"
Marco Baccalaro asked Marco Baccalaro commented

VR mode in millimeters

Hello @phil.bobo,

I'm trying to use the Oculus in a model build in millimeters.

The issue with xbox control can be easily solved (https://answers.flexsim.com/questions/42237/oculus-and-units.html).

But i can see just less than one meter from my point of view, everything more distant is not shown.

I tried changing some value in the view: viewnear, viewfar, something in OnDraw ... but without success.

What can I do?

Thanks

FlexSim 17.1.4
vrvr modeoculusmillimeters
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

1 Answer

Phil BoBo avatar image
1 Like"
Phil BoBo answered Marco Baccalaro commented

This is a bug introduced with 17.1. The clipping planes are hard-coded to a specific value. This value is bad when using units other than meters. I'll add a case to the dev list to fix this.

· 4
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Marco Baccalaro avatar image Marco Baccalaro commented ·

Do you think that the fix will be available in the 17.2? And in the meanwhile could it be there a workaround?

0 Likes 0 ·
Phil BoBo avatar image Phil BoBo ♦♦ Marco Baccalaro commented ·

I have partially fixed the rendering in Oculus Rift in non-meter units.

I fixed the near and far clipping planes so that they scale with the model units, and I updated the head position so that it scales with model units, but the avatar hand positions will require more time and effort to fix than we have before the 17.2 release. Those will need to be fixed in a later release.

1 Like 1 ·
Marco Baccalaro avatar image Marco Baccalaro Phil BoBo ♦♦ commented ·

Thank you so much Phil! This allows our customer to show simulations of their products through VR in an international exhibition so it's really appreciated!

0 Likes 0 ·
Phil BoBo avatar image Phil BoBo ♦♦ Marco Baccalaro commented ·

There is not currently a workaround. I'm not sure whether this fix will make it into 17.2 or whether it won't be fixed until 17.2.1.

0 Likes 0 ·