cdl64 not loaded

On 14/09/2015 at 14:53, xxxxxxxx wrote:

User Information:
Cinema 4D Version:   R16 
Platform:   Windows  ;   
Language(s) :     C++  ;

---------
Hello!

I have created a plugin that runs in my system as it supposed to (using Visual Studio 2013).
It creates a folder MyPlugin along with the corresponding menu item.
Everything works fine.

Sometimes though, when i transfer the plugin folder to other PCs, it is not loaded in Cinema4D.
Even when i try to run Cinema4D using visual studio (via cinema4dSDK) i get the messages:

'CINEMA 4D.exe' (Win32) : Loaded '<path>/my_plugin.cdl64'. Cannot find or open the PDB file.
'CINEMA 4D.exe' (Win32) : Unloaded '<path>/my_plugin.cdl64'

Why does it unload the plugin?

Thank you.

On 15/09/2015 at 03:43, xxxxxxxx wrote:

you need to recompile it, I guess you are doing it in debug mode, in release mode you won't encounter this problem.

On 15/09/2015 at 04:34, xxxxxxxx wrote:

Hello.

I build it in release mode and then i install it in different PCs.

Thnx.

On 15/09/2015 at 05:53, xxxxxxxx wrote:

Hi,

my first bet would be the version of Cinema 4D (actually the API_VERSION). If the plugin id build on a higher version than the version trying to load the plugin, it will fail.
Usually you can expect your plugins to be upward compatible. For example, I still have plugins running in R17, that have been built against R13. The other way around won't work.
So, this would be the first thing to check.

On 15/09/2015 at 06:24, xxxxxxxx wrote:

Hello !

The plugin is built using the R16 Api.
It also runs in R15 and R17 but it doesnt in R16.

On 15/09/2015 at 06:34, xxxxxxxx wrote:

Please check also the minor version. For example there was a problem within R16, which made it necessary to bump the API_VERSION during R16.

On 16/09/2015 at 23:54, xxxxxxxx wrote:

I have the same issue.

I compiled on 16.59 and it runs.
It also runs on 16.050 (Build RB131856).
I will check with the customer which version he runs.

For what versions will it fail?

On 17/09/2015 at 00:33, xxxxxxxx wrote:

Hello.

Thank you very much for your answer.
Updating Cinema4D version solves the problem.

thnx.