Report issues
There’s now a dedicated github repo for reporting issues. As usual, please be as detailed as possible, keeping in mind that only you know all the details about your exact environment and situation. It’s crucial to be able to reproduce bugs in order to fix them, so please leave clear, step-by-step instructions on how to get to a state where someone else can see what you’re observing. And of course, if you’re having problems with a particular 3D model, attach it and any supporting files (materials, textures etc) to the ticket…
Click the icon to report a problem:
: 
Changes for Android 11+
Android 11 placed severe restrictions on unfettered file access by apps like this. Apps with large user bases like MX Player and VLC, which need to access arbitrary media file types, requested and were granted the new “Manage all files” permission. But unfortunately this app doesn’t have that kind of clout. Because there are dozens of file extensions for supported 3D models and textures, and one file may depend on another with a different extension, there was a big problem going forward, especially since so much of the core code uses C++.
The solution, while inefficient and rather annoying, is to present the user with a one-time system dialog to allow access to a folder containing 3D models, and to then copy those models to app-internal storage. This technique means that the app will require more storage than it should, since there are now 2 copies of the 3D models — the original, plus the one duplicated by the app. But thereafter the original code can function as normal, with arbitrary file access being freely available.
Of course, if running on Android 10 or older, there won’t be any need to duplicate files since the newer file system restrictions don’t apply; in this case the app will search under the “Download” folder so be sure to put your 3D models somewhere under that hierarchy.
A few tips
- 3D models bundled in archive files (.7z, .rar, .zip etc) need to be extracted manually; this app doesn’t understand archive files!
- Keep in mind that the app runs on mobile devices which are traditionally resource constrained compared to desktop workstations! Large 3D models (over a few MB) may
- cause the app to crash
- load very slowly
- perform poorly
- If textures look strange try reloading with “Flip UVs” checkbox ticked.
- If models pieces are clumped together try reloading with “Pre transform vertices” checkbox ticked.
And some caveats…
- Many 3D models, especially if not explicitly labelled as “low-poly,” are intended for high-end workstations. They can be huge and demand more resources than a mobile device can provide! The app may crash frequently when attempting to load models beyond the capabilities of the device.