I have found a bug. If I assign LightMap texture to the object, I will have kFBTextureUseSphericalReflexionMap instead of kFBTextureUseLightMap in the UseType property of FBTexture.
It’s a nice service for holding some code notes. Welcome to my page on GitHub Gists. In my opinion interesting moments in my gists like these: remember about fact that connect in/out animation nodes will be automaticly removed in a
“buffer overrun issue” – thats was an error in release version of my plugin, when I have added a new property with type Vector2d. I don’t know whats wrong inside this type, but I have replaced it with two FBPropertyDouble
There is a bug in method declaration ClosestRayIntersection of the FBModel class. The last argument specified as FBNormal type (float precision), but to tell the truth function operate with FBTVector (double precision) type. As the result there is a stack overflow
In OR SDK (MotionBuilder SDK) we operate with scene and models through simple pointers. Developer is responsible for the vigilance of the real existence of the model. I’m talking about situations when the user has deleted the model or opened