THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 16/04/2009 at 14:09, xxxxxxxx wrote:
Cinema 4D Version: R10+
Platform: Windows ; Mac OSX ;
Language(s) : C++ ;
For the past week or so, I've been working with some Maxon folks (Rick Barrett and Kai Pedersen) to come up with a working solution for getting my Riptide Pro plugin to work with the new License Server.
The impression I get after these discussions is that all currently available info (SDK Docs, Dev Kitchen notes, forum threads here) is incomplete or inadequite for 3rd-party developers to successfully develop a working solution, so this thread is my attempt to try to clarify some of the issue involved.
Also note that even though the License Server is only available as of R11, in my case, I was/am not yet using any R11-specific code, so the solution/methods presented below are compatible with building with the R10.1 SDK (ie. don't force yet another version-specific build).
Finally, keep in mind that dealing with serial numbers and license keys is a 'sensitive' (security) issue, so any values I use in examples below will be "made up" (not real) for the purposes of discussion. I will also need to talk in "general" terms about how keys are generated and used - much of which is up to each developer to implement.
(I'll be making several posts, to cover everything...)
If you only have a vague understanding of what the License Server is/does, then the first thing you should do is go and watch the (free) tutorial videos on installing and using the License Server at Cineversity.com - you can find them right on the front page, top-center "Sample Tutorials" section.
Registering Plugins - license key format:
The first thing to note from those videos is just 'how' serial numbers are entered into the License Server. Note that the interface differs from the "Personalize" dialog - it's just one big empty text-entry box where you basically "paste" the block of numbers that Maxon sends you. These strings all use a similar formatting, that looks something like so:
CINEMA 4D R11 : [11-0-1000] <<10100012345-AAAA-BBBB-CCCC-DDDD>> Mod: Adv. Render : [11-0-1002007] <<32300012345-AAAA-BBBB-CCCC-DDDD>> Mod: Dynamics : [11-0-1000308] <<36300012345-AAAA-BBBB-CCCC-DDDD>> Mod: Hair : [11-0-1017643] <<40300012345-AAAA-BBBB-CCCC-DDDD>> Mod: Mocca : [11-0-100001300] <<35300012345-AAAA-BBBB-CCCC-DDDD>> Mod: MoGraph : [11-0-1019455] <<41300012345-AAAA-BBBB-CCCC-DDDD>> Mod: Sketch & Toon : [11-0-1012309] <<37300012345-AAAA-BBBB-CCCC-DDDD>> Mod: Thinking Particles : [11-0-1001443] <<33300012345-AAAA-BBBB-CCCC-DDDD>> Mod: NET Unlim : [11-0-1001] <<30100012345-AAAA-BBBB-CCCC-DDDD>> Multi-License R11 (001) : [11-0-200000174] <<20100112345-AAAA-BBBB-CCCC-DDDD>>
...when you paste that into the entry box, the License Server will parse those strings and 'register' the individual plugins as part of a "serial package".
In order for your plugin to get registered with the server, you will need to provide (your customers with) a similarly formated license key string, so the next section (follow-up post) will take a look at the format and some of the specifics requirements of that string.