The Mixed Reality Forums here are no longer being used or maintained.
There are a few other places we would like to direct you to for support, both from Microsoft and from the community.
The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.
For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality.
If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.
And always feel free to hit us up on Twitter @MxdRealityDev.
Frame Rate Question
I have been trying to get my FPS to 60 when trying to view a large FBX file exported from REVIT but have been unsuccessful. Below are a list of the things I have done, but can only seem to achieve 30 FPS which looks very choppy and the location of the hologram is very unstable:
-Fast quality settings
-Simplygon to reduce mesh (got it as low as 109,000 triangles, began at roughly 340,000)
-Holotoolkit shaders on all materials (standardfast)
-One material per mesh
-Tried combining meshes in 3ds max for a lesser number of unique renderers
-using the Holotoolkit main camera of course
-using shader preloading, rendering path -> forward, and 16 bit depth buffers
-using very basic scripting, not complex update function
I haven't tried writing my own shaders, assuming that the one's given with the holotoolkit are efficient enough, but I could be wrong. Are the triangles too large? or is there something else I should try?
Best Answer
-
Options
mark_grossnickle
✭✭✭
Try to get below 100k triangles. 30k would be a good goal if possible.
Don't use standardFast. Try vertexLit or lambert.
How many draw calls do you have? Anything you can batch?
As for the location being choppy, can you confirm you are using the stablization plane?
Taqtile
5
Answers
Try to get below 100k triangles. 30k would be a good goal if possible.
Don't use standardFast. Try vertexLit or lambert.
How many draw calls do you have? Anything you can batch?
As for the location being choppy, can you confirm you are using the stablization plane?
Taqtile
I only have 6 draw calls currently. Once I get below 100k triangles the object is barely recognizable anymore. I don't believe I am using stabilization plane, could you expand on that @mark_grossnickle
Well, are you using the latest HoloToolkit? Last I checked they built the stabilization plane into that. You can see a sample of what that code looks like here: https://developer.microsoft.com/en-us/windows/holographic/hologram_stability
Taqtile