dast

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.

Some of you might have noticed that my plugins are not available anymore at the C4DCafe Store. I had requested Igor to temporarily disable or remove the plugins from the webshop. Reason for this is that I did not want potential customer to purchase a pre-R20 version, expecting to have a working version when Cinema 4D R20 is released. Since updating the plugins to R20 might require some time (once I have access to an R20 SDK), I had decided to make plugins available via the store only after their R20 version would be ready.

Some of you might have noticed that my plugins are not available anymore at the C4DCafe Store. I had requested Igor to temporarily disable or remove the plugins from the webshop. Reason for this is that I did not want potential customer to purchase a pre-R20 version, expecting to have a working version when Cinema 4D R20 is released. Since updating the plugins to R20 might require some time (once I have access to an R20 SDK), I had decided to make plugins available via the store only after their R20 version would be ready.

Another road sign that caught my eye, while biking. To the "untrained" eye, this would seem to be a regular sign helping out fellow road users finding directions. However, the geeky minds amongst us would frantically look around, and wonder where the "pan" and "rotate" are located ...

Yes, the registered version is fully functional. The unregistered version has limited features and as such is meant to discourage people uploading it to other fora ... and taking credit as the plugin being "their work". Since registering the plugin is free, I don't see why anyone would be using an unregistered version ... unless they don't have a legitimate and valid Cinema 4D serial number to provide.

I guess I have given plenty of time for those having downloaded the beta version to allow to provide their feedback. Time for this plugin to be released to the public. It has now been made available in my "C4DS plugins" blog. https://www.c4dcafe.com/ipb/blogs/blog/57-c4ds-plugins/ If you'd like to comment, make suggestion, ... please continue doing so in this thread.

Well, who would have thought. It is a funny coincidence that R20 does have this feature. We've been years without this ability and now suddenly solutions pop up in my mind as well as in MAXON's developers ones. There must be something in the air ... or we must have been smoking the same stuff. Oh right, I don't smoke. I don't know if this feature was already available in R20 betas, way before I dreamed up the solution. But I want to believe that MAXON's developers were inspired by this thread, and implemented their take on it. That way, the whole orphan point project at least wasn't "pointless". Still am jealous of @JLeaburn coming up with this terrific plugin name ... ROFLMOPO. My hat off to you, sir.

Yet another bike trip today (in a neighboring country, this time). Then, almost at the end of the trip, I encountered this township sign. I have to admit, the spelling is a little off, but I guess everyone knows which primitive object in Cinema 4D it refers too ...

Almost forgot I once made a short video demonstrating the workflow I used. The workflow heavily relies on the plugins I created, but things can be done without those (obviously with more manual work).

I haven't use Substance Painter in a while. Looking forward to continue with a project I put on the shelf a while ago. In the past I had created this utility plugin, which allowed me to import the generated Substance Painter textures into Cinema 4D in a more automated way. https://www.c4dcafe.com/ipb/forums/topic/92673-speti-and-tina I am still looking for a way to provide access to all my (non-commercial) plugins, without requiring a specific website, nor the C4DCafe Store ... but that's food for another story.

Not good enough ;) The whole idea behind the topic is to provide "own-made" photos of 3D terminology. No links allowed to images (or any other material), which you don't own the copyright of.

Hi, Not a stupid question at all. The beta download is over and release version has been created, ready to be uploaded. However, before I do so, I am just waiting to allow for the other 61 people who also downloaded the beta to voice their feedback. Good or bad.

I am providing an update to the plugin, which resolves an issue I encountered when performing a "Revert to Saved ...". (updated plugin provided in first post)