On 29/01/2013 at 03:57, xxxxxxxx wrote:
Cinema 4D Version: R13
Platform: Mac OSX ;
Language(s) : C++ ;
Hello there fellow coders,
Recently I started coding a plug-in for Cinema that exports the scene to another file format for use in a "2.5D" game engine.
I've done that already for another file format, so I'm certainly not new to this. However, back then I didn't need any resources or such, as it was only a simple SceneSaver.
So now I do need resources, because this time I'm utilizing Tags, which of course need parameters. Unfortunately, this is where I am new to. To get into that, I tried to make use of the "look at camera" tag from the SDK examples, putting every file needed for the descriptions in their places, renaming them, registered a test tag plugin which tries to load the resource files just like in "lookatcamera.cpp".
It builds just fine and also loads into Cinema, I can even assign this test tag to an object in the scene. However, it immediately tells me that Cinema couldn't load the file '<Cinema directory>/resource/strings_us/description/tpathsetuptag.str' ("tpathsetuptag" is the name I gave those files).
Putting every file into the corresponding directory in <Cinema directory>/resource/ does fix this, but I'm certain it is not supposed to work like that.
The plug-in directory is structured exactly like described in the SDK Help (and the c4dsdk-project).
Of course, I already tried searching for solutions to this problem, but generally just get results for people having problems even building their plug-ins.
Why is Cinema even looking there instead of the plug-in directory? Shouldn't those resource files be built into the dynamic library? Maybe this is what's going wrong here, misconfiguration of my Xcode (4.5.2) project.
Thanks in advance,