R12+VS2005+FBX2010=Error C4263?

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 03/02/2011 at 05:19, xxxxxxxx wrote:

I will give it a try later today.

cheers,
Matthias

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 03/02/2011 at 07:02, xxxxxxxx wrote:

I tried to compile your test project with R12 and I get the same warnings and errors as you described. Here they are C4263 and C4264 erros as well. I will see if I can find a solution.

cheers,
Matthias

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 03/02/2011 at 07:18, xxxxxxxx wrote:

Howdy,

Thanks Matthias. Maybe it is some compiler settings or something?

The project is a copy of the cinema4dsdk project that came with the R12 Demo, I believe the version I downloaded was the first released demo. I haven't updated it, although, I don't know if the sdk project gets updated with it?

Adios,
Cactus Dan

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 03/02/2011 at 07:24, xxxxxxxx wrote:

your server is unreachable so I cannot download it for a trail run but will try again later.

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 03/02/2011 at 07:38, xxxxxxxx wrote:

Howdy,

Yeah, my web hosting service is experiencing an outage. !Ouch[URL-REMOVED]

But here's what I did, if you want to try it from scratch: I simply made a copy of the cinema4dsdk project and deleted all of the files except the main.cpp file. Then in the main.cpp file, I deleted most of the code and added the include files for the fbx sdk like this:

/////////////////////////////////////////////////////////////
// CINEMA 4D SDK                                           //
/////////////////////////////////////////////////////////////
// (c) 1989-2004 MAXON Computer GmbH, all rights reserved  //
/////////////////////////////////////////////////////////////
  
// Starts the plugin registration
  
#include "c4d.h"
#include <string.h>
  
// fbx sdk includes
#include "fbxsdk.h"
#include <fbxfilesdk/kfbxio/kfbxiosettings.h>
#include <fbxfilesdk/fbxfilesdk_nsuse.h>
  
Bool PluginStart(void)
{
	return TRUE;
}
  
void PluginEnd(void)
{
}
  
Bool PluginMessage(LONG id, void *data)
{
	//use the following lines to set a plugin priority
	//
	switch (id)
	{
		case C4DPL_INIT_SYS:
			if (!resource.Init()) return FALSE; // don't start plugin without resource
			return TRUE;
  
		case C4DMSG_PRIORITY: 
			return TRUE;
  
	}
  
	return FALSE;
}

... added the fbx static library for VS2005, and compiled.

Edit:
Also, I followed the instructions in the pdf file for "Installing and Configuring" for Windows.

Adios,
Cactus Dan

[URL-REMOVED] @maxon: This section contained a non-resolving link which has been removed.

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 03/02/2011 at 08:17, xxxxxxxx wrote:

hmm, I can only download the fbx 2011 sdk libraries from the autodesk website. I'll see if I get the same errors with that one.

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 03/02/2011 at 08:21, xxxxxxxx wrote:

Howdy,

There is a link on their site to older versions. You can actually download all versions back to 2005.

Adios,
Cactus Dan

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 06/02/2011 at 07:40, xxxxxxxx wrote:

Howdy,

Any solutions yet?

Adios,
Cactus Dan

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 07/02/2011 at 10:16, xxxxxxxx wrote:

Well, I tried it now and the same happens with the 2011 library. Same warning and also C4264 is treated as error even. So this is a persistent issue I assume.

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 07/02/2011 at 10:25, xxxxxxxx wrote:

Oh just to mention, I used your project that you provided.

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 07/02/2011 at 10:31, xxxxxxxx wrote:

Howdy,

The question is what is it in the R12 sdk project that is different from the R9, R10 and R11 sdk projects, because those compile fine with the fbx library on Windows?

Is the built in fbx exporter compiled like a plugin, too? If I go to "resource/modules/fbx2010/" I see 2 files:
fbx2010.cdl
fbx2010.cdl64

Adios,
Cactus Dan

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 07/02/2011 at 10:32, xxxxxxxx wrote:

Howdy,

Originally posted by xxxxxxxx

Oh just to mention, I used your project that you provided.

If you start from scratch and strip out all the code from a copy of the sdk project as I did, do you get the same errors?

Adios,
Cactus Dan

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 07/02/2011 at 10:38, xxxxxxxx wrote:

yes, even with a clean c4d sdk, as soon as I include the
#include "fbxsdk.h"

I get the warnings and errors (of course I added the according lib and include paths to the settings beforehand)

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 07/02/2011 at 11:00, xxxxxxxx wrote:

Originally posted by xxxxxxxx

Howdy,
The question is what is it in the R12 sdk project that is different from the R9, R10 and R11 sdk projects, because those compile fine with the fbx library on Windows?
Is the built in fbx exporter compiled like a plugin, too? If I go to "resource/modules/fbx2010/" I see 2 files:
fbx2010.cdl
fbx2010.cdl64
Adios,
Cactus Dan

As I said earlier in the thread: We don't encounter these warnings - and yes, we do use the same API (and compile plugins) like you do when creating those cdl/cld64 files.

There is no special api or sdk for Maxon developer - we're eating the same "dog food" If Matthias doesn't find a workaround for you in the next days, I'll have a look at it (but I'm currently too busy with other stuff...).

Best regards,

Wilfried

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 07/02/2011 at 11:32, xxxxxxxx wrote:

Howdy,

Thanks for the info, Wilfried.

Can the fact that I'm using std::vector to create lists of structures cause any issues.

A warning I was getting was this:

c:\program files\microsoft visual studio 8\vc\include\vector(1141) : warning C4530: C++ exception handler used, but unwind semantics are not enabled. Specify /EHsc

... which seems to be pointing to the vector include, so I turned on C++ exceptions in the Code Generation setting to get rid of that warning. Is that safe to do? That same setting change was made in my R9, R10 and R11 projects.

Adios,
Cactus Dan

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 08/02/2011 at 01:02, xxxxxxxx wrote:

Unfortunatly I am rather clueless regarding this issue. I can only confirm the problem. I made some comparisons between the 11.5x and 12.x SDK and found some small differences, for instance the default warning level was 3 in 11.5x where it is 4 in R12.x. In any case changing these settings made no difference. I am afraid we have to rely on Wilfried's help here.

Interesting is if you change the warning level to 4 in 11.5x how many warnings you will get by compiling the SDK examples, mostly for the API library though

cheers,
Matthias

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 08/02/2011 at 07:30, xxxxxxxx wrote:

Howdy,

Yeah, I noticed that difference in the warning level, too. In the R12 project I tried decreasing the warning level, but those warnings still showed. The project does compile without problems using the:

#pragma warning(disable : 4263 4264)

... but I also have a crashing in the R12 version of my plugin, and I don't know if that's contributing to it or not (because of my lack of experience) So, if I seem panicky about these warnings, that's the reason.

The bug report shows the crash happening inside a function in the fbx library, but I haven't been able to determine what is triggering the crash, because it won't crash when running the debugger.

If I can resolve the crash issue, then I probably won't be as worried about the warnings and using the pragma to turn them off.

Adios,
Cactus Dan

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 12/02/2011 at 12:04, xxxxxxxx wrote:

Howdy,

Well, I may have resolved the crash issue. I'm still testing, though.

It seemed like it would never crash the first time I imported a file, but it would crash the second or third time or sometimes even wait until the fifth time importing a file before it would crash.

I went through all of my code and found quite a few memory leaks, where I created memory for a char string in a separate function, and then wasn't freeing that memory in the calling function.

I fixed those and a couple of others, and now the importing of the files seems stable.

Is it possible that the memory leaks could've been the source of the crashes?

Adios,
Cactus Dan

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 13/02/2011 at 07:33, xxxxxxxx wrote:

Originally posted by xxxxxxxx

Howdy,
Yeah, I noticed that difference in the warning level, too. In the R12 project I tried decreasing the warning level, but those warnings still showed. The project does compile without problems using the:
#pragma warning(disable : 4263 4264)
... but I also have a crashing in the R12 version of my plugin, and I don't know if that's contributing to it or not (because of my lack of experience) So, if I seem panicky about these warnings, that's the reason.
The bug report shows the crash happening inside a function in the fbx library, but I haven't been able to determine what is triggering the crash, because it won't crash when running the debugger.
If I can resolve the crash issue, then I probably won't be as worried about the warnings and using the pragma to turn them off.
Adios,
Cactus Dan

And here 's the answer to your questions.

Is this a bug in your source or Cinema's SDK?

- No.

Why does this happen when compiling with the r12 SDK, but not in older SDKs or with Autodesk's sample projects?

- r12 sets additional error checks and warnings in the file "DebugWin32.vsprops" which you find in the _api_lib-Folder. This file is inherited by projects based on the api/SDK samples. If you look in the VS properties for the project, you'll find a entry called "command line" in the compiler settings. Under this entry you find all command line options that are passed to the compiler.

The options that matter here are "/w44263" and "/we4264" which enable the checks (and treat it as an error). In the "command line" entry there is a text box, where you can enter additional options. If you enter these options (without the " !!) in Autodesk's own sample projects, you get (tada) the same error message you reveived in your plugin example.

How to fix it?

- As we can't fix AD's source, you can either disable these warnings in the project settings or the source like you did, or you can do that in an external include file which contains something like:

#ifdef __PC
#pragma warning (push)
#pragma warning (disable: 4263)
#pragma warning (disable: 4264)
#include <Autodesk's stuff >
#pragma warning (pop)
#endif

This way you still can utilize the enhanced warning and error checking level in your code.

Best regards,

Wilfried

P.S.: I have to give props to Win7's fantastic desktop search function, which seems to be unable to find something simple like the above in a text file on the hd...

Helper

THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

On 13/02/2011 at 08:46, xxxxxxxx wrote:

Howdy,

Thanks for the info, Wilfried.

So, something like this?:

// fbx sdk includes
#ifdef __PC
    #if API_VERSION > 11999
        #pragma warning (push)
        #pragma warning(disable : 4263 4264)
        #include "fbxsdk.h"
        #pragma warning (pop)
    #else
        #include "fbxsdk.h"
    #endif
#else
    #include "fbxsdk.h"
#endif

Adios,
Cactus Dan