On 18/01/2017 at 13:58, xxxxxxxx wrote:
Cinema 4D Version: R18
Platform: Windows ; Mac ;
Language(s) : C++ ;
my customer uses the new RLM license server. The registration window doesn't accept the plugin license. I really don't know anything how clients behave under RLM. Please help.
On 19/01/2017 at 03:12, xxxxxxxx wrote:
The empty input field for the SplinePatch license key and the message next to the field suggest that the digits typed in by the customer are not applied at all.
On 19/01/2017 at 08:14, xxxxxxxx wrote:
Hi Klaus, thanks for writing us.
I confirm the behavior you've reported. We're investigating the problem and will keep you updated about its resolution
On 06/02/2017 at 05:05, xxxxxxxx wrote:
Before it's getting lost on page 3. Any news on this topic?
On 08/02/2017 at 06:12, xxxxxxxx wrote:
Hi Klaus, thanks for relisting the topic on the top.
We're actually focused on the topic working together with the Development Team in order to provide a solution to support plugin licensing via RLM mechanism. At its first incarnation RLM licensing schema was not meant to support plugin licensing as much as happens with standalone license or licenses issued by MAXON License Server.
I'll keep you updated on the topic as soon as I can.
On 21/09/2017 at 12:45, xxxxxxxx wrote:
now, R19 is out. Any news on the RLM issue? Seems, that I can't sell my plugins to customers running RLM.
On 22/09/2017 at 02:35, xxxxxxxx wrote:
In the R19 API the GeGetSerialInfo call delivers a RLM license key if present. This is a good start. But there isn't any way to hook plugin serials to the RLM, right? So this call can currently just be used to check, whether a client is running under RLM, isn't it?
So I think about a solution using a license file on the client to be used, if SERIALINFO_RLMLICENSE is set.
Any comments? Seems, that nobody else has customers using RLM ...
On 22/09/2017 at 06:29, xxxxxxxx wrote:
In R19 SP1 we have introduced a fix to partially address the issue that many plungin developers have faced with the introduction of the RLM licensing schema in Cinema.
In R19SP1, the GeGetSerialInfo() has been properly modified to support all the three licensing schemas currently available in Cinema:
• SERIALINFO_CINEMA4D for single-license standa-alone permanent case;
• SERIALINFO_MULTILICENSE for multi-license floating case with MAXON License Server;
• SERIALINFO_RLMLICENSE for multi-license floating case with RLM Server.
By introducing the latter, we've provided the developers with a mean to query and retrieve valuable information about Cinema from the RLM Server.
will have the SerialInfo instance (si) to be filled in with data similar to those retrieved by using the SERIALINFO_MULTILICENSE flag.
This introduction removes the limitation being not capable to know how many seats where sold of a specific product package which frequently resulted in the lack of capability to sell an adeguate number of plugin licenses.
That said, this addition combined with the use of the ReadPluginInfo() and WritePluginInfo() gives the chance to check 3rd-party plugins license even under RLM environment.
Schema is simple:
• the plugin developer requires the user to generate a license request string formatted as AA-B-CCC-DDDDD where "CCC" is the number of seats available for the package "DDDDD" of Cinema version "B";
• the developer generates the license string and provides it back to the customer ;
• the plugin (still in an unlicensed case) will then be used to register the license by using the [ https://developers.maxon.net/docs/Cinema4DCPPSDK/html/c4d__general_8h.html#aa69a9093991a83519f17aace2a05ac33 ]WritePluginInfo() storing the plugin license information locally on the customer machine;
• at the next plugin reload the plugin will check for its own valid license on the local machine using the [ https://developers.maxon.net/docs/Cinema4DCPPSDK/html/c4d__general_8h.html#a86b07b74719b5f77e6a01bfcfe2adaa5 ]ReadPluginInfo() and will validate the retrieved data both against the developer own schema and against the value returned back from GeGetSerialInfo().
This schema has the limitation that the plugin license should be installed on all the clients where the plugin is expected to be used but this can be considered a minor limitation compared to the previous situation. On the other side, if a plugin is expected to be installed on hundreds if not thousands of nodes it's pretty likely the developer to have integrated its own floating licensing technology or used some 3rd party floating licensing solution.
This information will be shortly provided through our blog (together with an example delivered on GitHub) and, with SP2, together with the Cinema SDK documentation.
On 22/09/2017 at 06:58, xxxxxxxx wrote:
Thanks for the info. Maybe a stupid question, but I can't answer it to myself in the moment:
If I extend the SERIALINFO enum in an older API, would a call to
GeGetSerialInfo(SERIALINFO_RLMLICENSE, &si;); return the RLM key on R19?
Btw.: I think you have accidentially swapped the parameters.
On 22/09/2017 at 07:07, xxxxxxxx wrote:
Hi Klaus, thanks for pointing out the swap.
With reference to the other point, unfortunately, it won't work.