Greetings,

Please take a look at the following code:

KFCurve* curve = new KFCurve()
curve->KeyModifyBegin()
KTime lTimeW;
lTimeW.SetSecondDouble(0.0)
int index = curve->KeyAdd(lTimeW)

This code used to work fine, but is no longer working after SDK 2011.2 upgrade. It crashes (segmentation fault) in the KeyAdd() function. I traced it in the debugger to the fact that lTimeW variable is not fully initialized. In particular, here is GDB dump:

(gdb) p lTimeW
$1 = {
mTime = 0,
static gsGlobalTimeMode = fbxsdk_2011_2::KTime::eFRAMES30,
static gsGlobalTimeProtocol = fbxsdk_2011_2::KTime::eFRAME,
static gsTimeObject = 0x0
}

Not that gsTimeObject is NULL. If however I initialize an SDK manager before executing the above code (i.e. just add one line [KFbxSdkManager* manager = KFbxSdkManager::Create()] in the beginning, everything works, and gsTimeObject is no longer null in debugger.

This sounds like a bug to me, as nothing seems to suggest that KTime is dependent on SDK manager. Thoughts?

Hi Matt,

KFCurve has some globals that are initialized in the KFbxSdkManager. We suppose that in the usual workflow, the first thing done is initializing a KFbxSdkManager.

The static function call, if you don’t want to create a manager, is

hope this helps,

Viviane, FBX Team

Viviane Rochon
Maya Data Platform
Autodesk

Oh yes, KFCurve::FreeGlobals() is called when the last KFbxSdkManager is destroyed.

If you create the manager before anything else, and destroy it at the end of your program, do you encounter other issues?

Viviane

Viviane Rochon
Maya Data Platform
Autodesk