dast

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.

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)

Glad it's useful. And thanks for providing feedback. Very much appreciated. I wish everyone downloading and using this and other plugins would do so, as it provides the motivation to work on other plugins.

Made some changes here and there. Preparing for a release ...

A member over at CGTalk requested a way to select an object in the viewport and let the Object Manager automatically update its view to show the selected object, no matter the dense hierarchy. There is, by default, in the Object Manager's menu an entry "Scroll to First Active" which can be called using the shortcut key "S". I created a small plugin to perform this automatically, and also provided an option to enable or disable this behaviour. The option is added into the Object Manager's menu, as a toggle entry right after the "Scroll to First Active". Enabled by default. Included zip file should be extracted into the plugins folder. Scroll2Object v12.zip (works with R16 upto R23)

Thanks for the feedback. The import/export WAS on my todo list, but I have removed it, as I didn't really see a benefit. The whole idea behind this plugin was to provide for a speed up in switching between most-used tools. Setting up these most-used tools is usually a one-time action. As such, I didn't want to spend lots of time (compared to the whole plugin development) into providing a setup interface. Therefore, no drag-n-drop, no fancy graphics, nor extreme customizable setup. If you need to "shift/offset" the dial, you can do so by adding tools at the end, removing ones at the beginning. The whole drag-n-drop feature would also provide for shifting. I could implement that, but I won't. At least not for the current version. I need something for a future update ;-) Additionally, since selection of tools should be a quick and easy, I especially do not want to provide a too complex main GUI. No presets, nor sub-level selection, ... I agree there is a potential need to want to group tools in separate dials. I have been looking into a way to provide multiple dials. One for modeling, one for animation, etc ... But have not yet found a way to allow for an easy and dynamical way to access these, except for providing them as sub-plugins. This is the way the "Wheel of Tools" and "History Dial" are organized. Each sub-plugin can be assigned a shortcut, but each also needs a unique plugin ID. And this cannot be made dynamically. So, I am afraid beta 4 will become the release version.

While biking around I encountered this road sign. And thought it would be amusing to start a topic containing photos (made by C4DCafe members) of traffic signs or other street furniture, representing 3D related terms. Where the every day man in the street wouldn't now why we, 3D nerds, have a chuckle at.