I have a GLB model of engineering data (pipes) without textures, which is 40MB size.
During loading using the BinaryBoomBox test scene with the model as the URI, Unity freezes for approximately 2.5mins during the file read operation but seems to execute the GLTF parsing component in less than 1 second despite a low frame budget.
In comparison, the total file read and parse time using Dan McCurdy's online viewer is less than 5 seconds.
Also, I am not sure if significant memory usage is a normal behaviour, it appears that over 800MB of memory is needed when the file is used.
I have a GLB model of engineering data (pipes) without textures, which is 40MB size.
During loading using the BinaryBoomBox test scene with the model as the URI, Unity freezes for approximately 2.5mins during the file read operation but seems to execute the GLTF parsing component in less than 1 second despite a low frame budget.
In comparison, the total file read and parse time using Dan McCurdy's online viewer is less than 5 seconds.
Also, I am not sure if significant memory usage is a normal behaviour, it appears that over 800MB of memory is needed when the file is used.
I attach the file in question here: https://www.dropbox.com/s/rjxjxmvejxj6ug1/Mercury_Trinity.glb?dl=0
Is the freezing and large memory usage an issue to rectify or a fundamental limitation of loading files in this way?