Posts

Post marked as solved
2 Replies
401 Views
I'm currently on a research project where we are making some trees for AR experiences and I'm having some issues with the PNGs I'm using for leaves. I model the trees in a program called Tree It and then export that into Maya to convert it to a GLB with Babylon.js' Maya Plugin. Then to test how it looks I put the tree into Babylon viewer and it looks perfect. The png transparency works fine and there is no hazy white background around the planes i'm using as leaves. Now comes the issue. When I drop the GLB into Reality Converter the pngs suddenly have a mostly transparent but still visible white background. It seems the issue is with Reality Converter since I don't run into this problem anywhere else in the pipeline. I vaguely remember reading something about Apple adding a faint white background to pngs but I can't remember if i just imagined that. Anyways here is a closeup of the issue:
Posted Last updated
.
Post not yet marked as solved
5 Replies
379 Views
I'm creating some AR trees for a research project and we're finally able to deploy the experience on Iphone after some updates made to reality converter. The only issue is that since it is a tree, it is made up of mostly cross-sectional planes that serve as the leaf cards for the model. When placed in AR, QuickLook is culling the faces on the tree, even though it is set as a double sided material in XCode. I can only select between cull front and cull back in XCode so I'm wondering if there is a way to change those options and export the USDZ so that when it is placed in AR it doesn't cull any of the faces. The screenshot attached is of the settings panel under the leaf material for the tree. Thanks!
Posted Last updated
.
Post marked as solved
3 Replies
465 Views
So I'm trying to convert an FBX to USD in reality converter and it's giving me a strange error. The first image is from Maya and is what the tree should look like. The second image is the output I got in Reality Converter. I even tried re-applying the texture but this is still happening. It seems like the UV information is lost during the conversion but I'm not sure. I think I saw someone post about a similar issue somewhere else but now I can't find the post again. Any help appreciated!
Posted Last updated
.