calus wrote:calus wrote:vijay_thirukonda wrote:If you check the attachment, you will notice that the exported FBX crease values are scaled down by 10. Not sure why, but this is what octane is reading. So I scaled it up by 10 if the file is coming from Maya.
Are you sure this is specific to Maya FBX ?
maybe this is because autodesk FBX plugins in general just doesn't use the same units for storing crease values, might be an historical reason.
This could be confirmed or not by checking also fbx subdiv exported from 3DSmax.
As I expected, I can confirm this is not an issue in the Maya FBX plugin :
C4d fbx export have the exact same wrong crease result in Octane than Maya FBX.
Please consider when importing any FBX in Octane that :
subdivision surface sharpness values (crease) are stored in the FBX format with a different unit than what Octane naively expects (1 FBX crease unit = 10 Octane crease unit )
vijay_thirukonda wrote:Considering all applications, I added a sharpness scale setting to import preferences and default value is 10.
sharpness scalename for the setting might be confusing with the existing
subdivision sharpnesssetting which is not about the same sharpness,
crease sharpnessinstead ?
aastepfunction, it compiles but any OSl shader using this function will make GPU fail.
vijay_thirukonda wrote:calus wrote:I just discovered FBX support in Octane is way better than I expected, very good indeed :
I was amazed even the linked polygon caching format is supported, and as this cache format is the same as in Maya I can just update the animation cache directly from inside Maya without exporting again the FBX in Standalone, pretty amazing...
However I found annoying issues, some geometry are just not loaded in Octane,
I isolated sample objects having this problem in the attached FBX.
I found if I change the UV mapping of the objects or subivide the mesh, this would eventually solves the issue,
but I really don't understand this bug/limitation in Octane and how to avoid it ? (the FBX have no issue to load in other sofware)
Thanks for the bug report. This is fixed and will be in next release. There was an issue reading opacity for the FBX material as well, that is also now fixed. So please make sure transparency of FBX material is set properly from next version.
Users browsing this forum: kron98 and 2 guests