Hi FSS, thanks for reaching out to us.
Your question it's outside the support purview of the SDK Team and, hence, we can't help. I also recommend refraining on talking, in this forum, about software reverse engineering or software hacking: this is not allowed under any circumstance.
Finally, if you need to script the plugin execution, consider reaching out to the software vendor which might provide, given his knowledge on the plugin design, more valuable insights.
Best, Riccardo
Hi @akramFex , I apologize for the long silence on our side. Unfortunately the thread fell through the cracks of the Xmas period and we lost track of it.
I'm glad you were able to find the solution and I'm grateful you wanted to share it with the rest of the community.
Cheers, R
@kbar said in The oldest SDK for Cinema 4D 19-25:
There should be no problem using the latest version of C4D for each release.
The MAXON_API_ABI_VERSION doesn't change between any minor release of a specific version. So the plugins will still run.
Although the MAXON_API_ABI_VERSION doesn't change across versions, the API_VERSION does and this has effect on plugin loading.
Building the plugin against the latest version of a certain C4D release will impede the plugin to run on earlier version of the same release (e.g. build against the shipped SDK of an RXX SP2 you can't get it loaded in RXX RC or RXX SP1). For this reason, it's always recommended, unless critical bugs are fixed regarding the API in a maintenance version, to build against the API shipped with the initial version of each release.
Since initial release gets replaced as soon as a newer version comes out on the official portal, I recommend checking the Maxon Registered Developer program and if you qualify send an email to the Maxon SDK Support Team to join it.
Cheers, Riccardo
Hi Community,
I'm glad to invite you having a look at the SDK Specialist job opportunity recently opened on the Maxon job-portal. The position is in Friedrichsdorf (Metropolitan Area Frankfurt), Germany or in Montreal, QC, Canada and its main responsibilities are:
Feel free to reach out our recruiters if you are interested in joining the Maxon Family and its SDK Team.
Best luck and look forward talking to those interested!
Riccardo
Hi Victor, please proceed on reporting the bug using Bugslife.
Thanks for the feedback.
With regard to @orestiskon saying in Interfacing with Gumroad's API:
The current license system in Cinema 4D implies that the user generates License Information and sends it to the plugin developer to get get a personalized key back.
please consider that a similar mechanism was in place even before R21 to let the plugin vendor generating the plugin license based on this customer information (see Licensing Plugins – Part I – Basics). So the UX is as much as was in the past and everybody is free to judge it.
With regard to @orestiskon saying in Interfacing with Gumroad's API:
Not only that but there are some very big limitations currently. If a studio account has 20 c4d licenses, I can't tie the plugin to a specific c4d version as I would with the serial numbers. I can only tie it to 1 machine, which is limiting and uncomfortable for the customer, or tie it to the account and allow them to only get 1 plugin license and use it in 20 different c4d licenses simultaneously.
it's not right, as proved in the Basic Licenses Workflow examples (blw_common, blw_pluginlicensedialog, blw_simplegenerator) where you can bind your license mixing up the following settings:
Wtih regard to @orestiskon sayng in Interfacing with Gumroad's API:
especially indie developers are struggling with it, as I've noticed in numerous people I talked with.
as far as I can see in this forum, I can count only 5 threads (including this) in the last 2 years. Please let your contact use the forum if the need support.
In the end I don't think that having still in place the old system would have helped on solving the issues reported here because that previous system was not addressing the issues that with Gumroad API you can address (like billing, license key generation and so on).
Nonetheless I'll ask PM to check again this topic and see if there's space in the future to accomodate with helpers eventually streamlining the plugin licensing process.
Thanks, guys, for providing hints and getting this discussion moving forward.
Although I see the point on @orestiskon saying in Interfacing with Gumroad's API:
I was surprised by the learning gap between developing a plugin and protecting it
I also think that what Gumroad offers is beyond the scope of the Cinema 4D API improvement. Offering a Maxon marketplace for freelance developers willing to get bucks out of their plugins it's something that might be interesting to discuss on a strategic level, but we can't for sure contain in the C4D API development roadmap.
However, I'll be glad to report to Product Management and eventually get the discussion moved on other tables.
At the same time, I must partially disagree with @kbar saying in Interfacing with Gumroad's API:
MAXON really need to sort this out and have an internal system for us developers. It is absolutely insane that they removed the existing system without implementing a replacement
The current system, which is more flexible on checking what hardware/entitlement Cinema 4D is running on and on making the plugin protection mechanism to react accordingly, compared to the previous existing one, is only lacking the ability to have the Maxon Licenses Server serving plugin entitlements to Cinema 4D. While this was handy to offer a floating-license provisioning mechanism for plugins, it has, imho, little to do with the numbers of little guys doing plugin-development and it covers only a fraction of a whole licensing-managing system that goes from selling the licenses to check the license in the host application.
Cheers, Riccardo
Hi Eddie, thanks for getting back but I ask you to specify what is not working or is not clear in the answer marked as Solution.
When posting code, I also recommend being sure that it's reduced to the bare minimum to reproduce the issue, that's properly documented and that a scene using it is attached to help us reproducing the issue rather than guessing what to do.
Riccardo
The issue has been recently investigated and it should have been just fixed.
Please confirm the links are correct now on your side.
Dear PluginCafé user,
on Thursday, May 27th 2021, from 06:00 to 07:00 CEST, due to planned maintenance activity, the services will be down and unreachable during this period.
Maxon SDK Team
Thanks @C4DS for reporting the recent positive experience.
Unless you experience the issue again in the future, we can consider the case closed.
Hi Daniel, sorry for coming back only now. I think it's a bug that has been introduced with the theme switch we've done but I'm a little bit puzzled because I can't reproduce it consistently.
If you click any of the top-right circle that appears in the notification drop-down, does the bell shows the counter?
Have you tried to clean-up the cookies, or using a browser in private-mode, to reproduce the issue?
Cheers, R
Hi Daniel, thanks for reporting.
We've not reported by others about this issue, nor we've seen this happening on our profiles. However I'll research next week to see what could be the cause.
Can you confirm which notification is missing? Email notification, forum notification or both?
Cheers, R
The updated version of the projecttool is available at this link.
Hi @mp5gosu, thanks for pointing it out but we prefer to stay consistent with the company new color palette.
Best, Riccardo
Hi community,
with the PluginCafè UI refresh from yesterday we are now shipping also on a dark-skin.
You can switch it by going to your profile settings and at the bottom of the page switch to Dark in Select skin for theme. Be sure to refresh your browser cache and you should be good to go!
Cheers, R
@Cairyn: thanks to nodeBB folks, the issue of infinite scrolling / infinite flickering should be resolved now.
Please let me know if it persists on your side, R
Hi @Cairyn, I've tested on different OS (macOS, Windows, Linux) and different browsers (Safari, Edge, Firefox) and, although I've spotted some other issues, I'm capable to dynamically scroll down like in an infinite scrolling mode.
The infinite scrolling mechanism although has a little lag that is "physiological" and can't be avoided: once reached the end of the scroll give the browser a little to refresh and load further pages.
What instead I'm still trying to fix is a sort of "infinite flickering" issue as visible below
I'll try digging down and for the time being as suggested by @ferdinand the best way to avoid this UX flaw is to active pagination under the User Settings
