I’m unable to have the geo5 to appear on my render.
Scale and position are totally fine, as seen with the geo6. The only difference is that the one animated doesn’t appear, but I added another animated and it was showing normally. Both are properly referenced in the Render TOP. In a light viewer it can be seen without issues, so I don’t really know what to try. It’s the only FBX import I’ve tried that doesn’t appear on any render.
Any ideas?
I would check the materials. Try overriding the material on geo5 with a constantMAT and see if it becomes visible. If so, the issue is probably with the imported materials in the FBX.
Thanks for the tip, unfortunately constantMAT doesn’t change anything.
If you’re not seeing any change at all it’s probably because the materials are set inside your FBX comp.
On the Advanced tab of the render TOP there’s an Override Material parameter that lets you override all materials. Maybe give that a try?
Otherwise, it would be helpful to post a link to your FBX so that people can help you dig into it further.
Override Material doesn’t work either, the other FBX appear except for this one.
This is the FBX, It’s free but I think it requires an account to download, so I’m not sure it’s ok to upload the model and share it myself.
Got it.
Seems like the main issue might be the scale of the asset. Setting the “Import Scale” parameter on the FBX comp to 0.01 and hitting “Import” made her appear right away.
I put the textures into the autpgenerated phongMAT at
/project1/rp_sophia_animated_003_idling/rp_sophia_animated_003_idling/rp_sophia_animated_003_idling_geo
attempting to remove it seems to break the animation and is probably not work the trouble of debugging for this.
Nada. It doesn’t work on my end. Even opened a separated project with only the FBX, did the import scale and changing the textures and still doesn’t appear.
Version 2023.117.60 on MacOS. Maybe OS issue?
I tested it with the version you specified on my Mac and yeah, it totally doesn’t seem to render. Moving to the current version fixed the issue for me.
I skimmed the release notes and didn’t see anything that would explain the behavior on the older release, but it does seem to be working properly in a more current build.
Well, that’s it then. Thank you so much for taking the time!
