dast

With all my other plugins converted to R20, and temporarily out of the way before I start adding new features, I wanted to spent some time on finalizing EasyUV. As a first step I wanted to get the plugin working for R16-R19. Step 2 would be to port it to macOS. And final two steps would be to port it to R20 on Windows, then to R20 on macOS. Quite some work ahead. For Seamilar I had created all icons in a drawing application. But this time around I wanted to model them, as I figured it would be faster to adjust. As well as reuse and interchange parts between icons. And it allowed my to finally learn how to use the Takes system inside Cinema 4D. As each icon is a different Take I could "simply" set up all the Takes and then perform a single "Render Takes". And all would be output as 32x32 bitmaps at the press of a single button, for perspective or top-view cameras. The scattering of the icons is maybe not that artistic, but I found it nice looking ... and it helped to take my mind of from all the coding I had been doing all day long. With step 1 completed it's time to take the next one.

Dials and my other plugins are now available for R20, see blog post below

PolyGnome and my other plugins are now available for R20, see blog post below

Still an hour and a quarter to go, but we're off to bed ... Happy New Year.

Finalized version 1.1 and wrote the documentation. An early Christmas present sent out to those having donated ... check your e-mails. Others will need to wait for the official release, in a few weeks.

Thanks! Scripts are available in the download section now.

I wanted to send you a PM, but apparently you're not able to receive messages (inbox full ?), as such let me pass the message this way: Hi Hrvoje, I have been using a few scripts over the years, and moving to R20 I noticed I missed some. Apparently, these were COFFEE scripts, so I took the time to rewrite these in Python. Now, I was about to upload them to the C4DCafe's download section for others benefit, but noticed these original scripts were named VP_Reset Position and VP_Reset Rotation. I figured these must have come from a Vertex Pusher tutorial I had purchased in the past. So, before uploading the converted Python versions, I 'd first like to ask if it is OK with you to upload these. I don't want to take credit for these, as they are simply derived from your original work.

Still need to figure things out before making the official announcement, but probably all my plugins being ported to R20 will be available from 1st January 2019. As I planned a less feature rich sibling of Seamilar (announced as EasyUV), I am also planning a less feature sibling of PolyGnome. It's a little early now (and still haven't figured out an appropriate name), but I soon hope to be able to announce this "EasyMeshblender".

Thank you for your interest in PolyGnome. R20 version of the plugin is completed, and will be available to the public starting from 1st January 2019.

Also remember that when hovering over the favorite "dot" in the dial, the description/info of the favorite is displayed in the status bar (even user has entered description/info). I agree that colors are difficult to memorize when having tenfold of favorites, but I haven't found a better way ... yet.

If you create a favorite with "mixed" settings, one checkbox on another off ... what would the restriction be? Besides, why restrict? The user can adjust the colors the way s/he wants. It is up to the user to define his/her favorite, which values are on/off, positive/negative ... So, choose your color the way you want. I also figure everyone has their own methodology of what colors best fit with what settings. Who am I to restrict anything?

I am in the process of finalizing the update of Dials. Still a few minor changes to do, and then the usual building on macOS. As well as porting to R20 (both Windows and Mac). New in this update are : - drag-n-drop for adding tools - favorites (via drag-n-drop) - support for multiple tool sets While the plugin was originally designed to work for tools only, a side effect of its design is that other parts of Cinema 4D can be dragged to the tool sets as well. Scripts, primitives, deformers, ... And these can be executed from the dials just like the regular tools. Unfortunately, favorites currently only work for tools. Maybe in future updates this can be extended as well.

Since EasyUV is meant having very limited features, it would be better to provide your specific requests into the Seamilar plugin discussion here And could you then please elaborate on your request a little further. Are you referring to "stacking" of UV islands?

[Edit - Note: this thread should be located in the "Programming - C++" section of the forums. It ended up in the "Python" section by accident during one of the forums reorganizing sessions] EasyUV is based on my Seamilar plugin, but as a younger sibling with less features. It mainly focuses on the ease of unwrapping UVs, using the specifically created Seam Tool. A small list (not final) of the differences between EasyUV and Seamilar: Available for R16-R21 Windows and macOS. Latest version (v1.4 beta 1) available in the download section. Some demonstration videos Main overview: https://www.youtube.com/watch?v=Ph2MsXwQNXY Export UV canvas: https://www.youtube.com/watch?v=TPKDSk6sbXk Bounding Box Transformation: https://www.youtube.com/watch?v=zN1z0-B1Oqg

Thanks for the feedback "Toolsets" have been designed. But I still need to find a way to provide this into the configuration window.

Have been working on some more features. This was the main purpose of the whole Dials plugin ... being able to provide multiple "favorites" per tool. It did take up quite some time before getting to that point. And I am still not release ready. There are still quite a few hurdles before reaching the finish. But providing, now and then, some updates on the status of the work does help keeping focused on the end goal. Since its original release the plugin has been downloaded about 250 times. Sadly only 9 people have taken the opportunity to register it. And only 5 found the plugin useful enough in order to provide for a donation. A big thank you to them for supporting me. Unfortunately, while being generous, these few donations didn't manage to compensate for all the effort spent developing the original plugin. Let alone all the extra effort needed for the follow-up. Lesson learned. Note: one of the reasons I have taken down the registration for the plugin, is that more and more users where providing an invalid serial number (cracked software). Not to sure what to think of that, but yet another lesson learned.

You're welcome. Glad the script is working and useful to learn from. Just a note that the original COFFEE script you posted is not complete. So, for others learning to convert COFFEE into Python, note that that the COFFEE script is missing something like main() { right between the end of the comment and the var declaration.

What is the problem you encountered? With the help of MAXON's Python SDK documentation I was able to convert it into the following Python script. Having no experience with the Stage object, I actually don't know what to expect. I hope the converted script does what it is supposed to ... # CamSwitch.py # CamSwitch.CSC V1 B.Horgan 2010, converted to Python Daniel Sterckx 2018 # works with Stage Object to toggle between editor and and linked cameras in stage object # (just switches the stage on and off and refreshes the view ) # NB - rename the Stage Object to 'CamSwitch' for the script to work import c4d def main(): switcher = doc.SearchObject("CamSwitch") if switcher: state = switcher[c4d.ID_BASEOBJECT_GENERATOR_FLAG] if state == 0: switcher[c4d.ID_BASEOBJECT_GENERATOR_FLAG] = 1 c4d.CallCommand(12147) # redraw view to activate linked camera in Stage Object else: switcher[c4d.ID_BASEOBJECT_GENERATOR_FLAG] = 0 c4d.CallCommand(12202) # Switch to the editor camera if __name__=='__main__': main()

After all the trouble of updating my plugins to R20 I finally found some time to actually work on updating "Dials". Version 1.1 will provide for a drag-n-drop configuration. In the short demonstration video I am using the shortcut "Shift-C" to open the built-in Commander and look up the available tools. I then select and drag the required tool from the Commander to the Dials' configuration window. The same could be done from the "Customize command window", or any other means that allows tools/commands to be dragged. Still "work in progress" at this time, while looking to add some more features.

In a plugin you can gray out controls in the Attribute Manager via the GetDEnabling() function. But I am not sure you can gray out userdata controls. You can however show/hide userdata controls as has been set up in following scene file. PythonTag ShowHide Userdata.c4d

Glad you like the plugin. Yes, got Groboto a few years ago, but never really digged the user interface ... or the whole user experience in that matter. My hat off to you for being able to use it in your workflow. When I conceived PolyGnome I assumed I would be able to provide asset libraries on a regular base. Truth is that plugin development in general just takes up all my time, I don't find the time to actual model anything these days. As I cannot provide asset libraries on a regular base, nor even now and then, I had decided to provide an easier way for user to prepare their assets. As I read, the Asseziter does what it was meant too. Thanks for the feedback.

I am not yet set which direction I will be following for this. But to be honest, I first need to convert all my own plugins to R20, so this script and its future options will have to wait. First, it is not my intention to convert everyone else's plugin or script to run in R20. I quickly did this rewrite of the COFFEE script as I assumed it would take only an hour or two to complete, and allow many users to continue enjoying said script. As for IvyGrower, I don't think this is a COFFEE script. So, it isn't just a simple rewrite. Additionally, that plugin might even be a commercial one (don't know, didn't actually check). In order to rewrite a script from COFFEE to Python you actually need the COFFEE source code. If it isn't COFFEE, nor has it's source code freely available ... were do you expect someone to start? Same with PolyCircle.

I am planning to add the possibility to control the radius of the circle, but for now I just made a quick conversion of the original COFFEE code into Python. <file removed> Edit: Just to point out, the original COFFEE script is not mine. I don't want to take credit for this plugin, just provided a rewrite into Python. Edit 2: I have removed the script file in this thread, as it has now been uploaded into the download section of the forum.

Have tried my hands at making the plugin R20-compatible. I will refrain from describing the horror and frustrations ... As this was my first endeavors with the new SDK, I hope things will go smoother for other plugins I am wanting to update. Fingers crossed (*) I am sure I overlooked a few things in fixing the implementation to compile and run on R20, so don't be surprised when this version of the plugin explodes in your face. R20 version of the plugin has been made available in the blog (mentioned earlier). For those having registered the plugin (and provided some donation to obtain updates ... thank you for that) please provide the 11 digits of your new serial number in order to register the plugin for R20. (*) I don't have high hopes, as this plugin was a really "simple" one, still requiring quite some days of work to adjust to get it working on R20. Not really looking forward to the more complex plugins.

Thanks for reporting. I had tested by adding other plugins as entries in the wheel of tools, and that was working OK. However, I never tested the dial AFTER restarting Cinema. The problem is that when the plugin is loaded by Cinema it initializes the dials and its icons. Unfortunately, at that moment other plugins might not have been loaded yet ... and as such that particular plugin cannot be found, nor its icon. Edit: Plugin has been updated to v1.0.3, fixing all reported issues.