Hi everyone. I seem to be running into a problem where AR Quicklook fails. It says “the file is too large”. This doesn’t seem to have anything to do with overall size of the final objects but number of parts.
If I missed this covered elsewhere, please let me know.
Hi,
It is a device limitation. There is a limit of how big the overall file can be for AR to work.
Thanks for the reply.
Is there a framework to understand the limit? For example: Device/Ram/file size = works/doesn’t work
Further, are there ways of limiting the file size in order to get the AR function to work? Maybe not using some textures?
Thanks for the help.
Not really, it’s an Apple limitation.
Not using any textures surely helps, other than that, the less textures you use also the better chance it will work with AR.
The problem isn’t really the file size, but the memory usage, which aren’t always closely related. A large file without textures can end up using a lot less memory, then a smaller file with lots of textures used.
Would be great if we would get more feedback when the project is to large.
I’m using a iPad Pro m1 1GB with 16GB ram and a 82 object render doesn’t show.
How close am I? How much RAM does it need?
Is there a workaround? Can I export and use a external Viewer?
Seems like the wood material takes up a lot of ram…
Can make a huge AR model when I don’t use wood.
I’m having the same issue, same spec iPad as mentioned above, this is a major let down.
The textures are only very basic tiled images, no bump maps, no diffuse or specular layers just simple textures, it seems more to do the software. If it was hardware, why can I view a multi room lidar scan (in different software), which is a huge file and walk around in AR from a first person POV, with no issues?