Jump to content


C4D Cafe Seller
  • Content count

  • Joined

  • Last visited

  • Days Won


C4DS last won the day on June 19

C4DS had the most liked content!

Community Reputation

185 Good


About C4DS

  • Rank
    Respected community member.
  • Birthday 06/04/1970

Profile Information

  • First Name
  • Last Name
  • C4D Ver
    19.024 Studio
  • Location
  • Interests
    Electric guitars, Radio controlled electric airplanes, 3D, Video editing

Recent Profile Visitors

5,273 profile views
  1. Wheel of Tools

    Thanks. I assumed I wasn't the first one to come up with this idea. But as far as I know, there hasn't been any plugin available which provides this functionality. I am still wondering why this is? To be honest. This idea had been in my mind for a long time now. It's only recently that I was able to implement it.
  2. While working on a plugin I got the idea of making this small utility: Wheel Of Tools. It allows the user to set up a list of most used tools, which are presented as a circular palette to select from. Available directly within the viewport. Current state of the plugin is only a concept, and I am mostly focusing on the actual tool selection. The part where user does set up the tools still needs to be worked out. For those familiar with PolyGnome, you probably already understand where I will be heading to ... Wheel Of Tools, once fully implemented, will be the base for a new way of interacting for the main part of the PolyGnome plugin.
  3. I don't have the python SDK in front of me, but I guess NBIT_OHIDE is that flag you're looking for
  4. While version 1.3 is currently in beta, I couldn't resist working on yet another feature: interactive rotation of assets. As always, I first prepare some concept to try out and see if things can get worked out. While being far from fully functional, I simply had to share next concept video showing off the interactive rotation (interactive scaling is next on the list). I am not planning to include this feature in the 1.3 version as this would delay the release, but hopefully will get it ready for a next update.
  5. With a bit of scripting (and some knowledge of the Cinema 4D SDK) you can store whatever you want into the object, or a tag. The only issue there is ... you need to store it in a "safe" place. Safe in the sense of "not overwritting other important information". So, what you could do is obtain a unique plugin ID from the official MAXON plugincafe. And write the original object name into the object using the obtained plugin ID as key of a BaseContainer. Not sure if you want to go this route, so I won't go into much detail, just mentioning this as a possible solution.
  6. For sure I remember your request during beta testing. Back then I mentioned this was a very nice feature, with great added value. But I also mentioned I wasn't able to provide a user-friendly solution, and as such it needed to wait before being implemented. As a result of the newly added Assetizer, I could now easily introduce this feature. Apologies for taking so long to finally get your feature implemented. Welding is performed by the plugin. No manual weld/optimize is required. I tried showing it in the video, but I just realized now I erroneously used points instead of polygons to demonstrate the feature.
  7. Further adding features to the latest version. For those assets that require some helper / placeholder / proxy / whatever you may call it: Disposable Polygons. This is something I wanted to provide for a long while now, but needed the "Assetizer" functionality to be able to handle this feature.
  8. It has been decided to put the plugin on an early retirement scheme ... The alternative solution using a script and short-cut key(s) is a much more user-friendly approach, which I actually prefer over a plugin. And it's platform independent, as well as release independent (unless the R20 SDK does break it). But all effort to make the original plugin is not gone to waste. Firstly, I learned a few things while implementation this "sneaky background" action. Secondly, it resulted in a much easier to maintain scripted solution. I will probably provide some update to the script, as I figured out a few extras. But I am currently too busy, so that will have to wait for a while.
  9. While I still believe the current plugin to be obsolete, I agreed to let user @natevplas beta test it. If only to test the provided mechanism does work without introducing any lag or delayed user response. This mechanism could then, potentially, be used in future for other purposes Why I believe the plugin to be obsolete? Well, it is only a matter of creating appropriate short cut keys in order to provide the current behaviour (keep unused points), or the custom behaviour (auto remove points). Currently, the backspace and delete keys are assigned to the current behaviour. But people can simply assign a different short cut key to the current behaviour and assign the backspace and delete key to the above script. This way, it's up to the user to define the default and custom behaviour ... without the need of a plugin (which will probably not work in future releases anyway).
  10. Copy following code into the Script Manager window and save it as i.e "Delete+Cleanup" Then with "Customize Commands", filter on the entered file name, and assign it "Shift+Delete" as shortcut keys ... and Bob's your uncle. Makes this whole AROP plugin I made completely obsolete ;-) Just why I didn't think of that before starting this whole plugin. import c4d def main(): # perform the delete (ID=12109) c4d.CallCommand(12109) # perform the clean up # get the currently active polygon objects objects = list() activeObjects = doc.GetActiveObjects(c4d.GETACTIVEOBJECTFLAGS_CHILDREN) for obj in activeObjects: if obj.IsInstanceOf(c4d.Opolygon): objects.append(obj) # remove unused points settings = c4d.BaseContainer() settings[c4d.MDATA_OPTIMIZE_UNUSEDPOINTS] = True res = c4d.utils.SendModelingCommand(command = c4d.MCOMMAND_OPTIMIZE, list = objects, mode = c4d.MODELINGCOMMANDMODE_ALL, bc = settings, doc = doc) c4d.EventAdd() if __name__=='__main__': main() Edit: Had some typos in the code, fixed now.
  11. Well, the very first name I used when setting up the research for this project was "Auto Orphan Killer". It's just a name, I thought at that point. And while it might sound funny in a way, I don't think many would have appreciated it. Another plugin of mine (PolyGnome) was originally meant to contain "enjoliver" in its name (french for embellish-er). Guess I better not call this new plugin "enjoliver twist" then. Nice idea, I didn't think about that. However, deleting is handled by Cinema itself, then the plugin does some post-processing. As such it does not detect the "delete" nor "shift-delete". Currently when you use "shift+delete" nothing happens, as Cinema does not know what that shortcut actually means. Had a quick look in "customize commands" and apparently the delete key (when meant to delete the current selected polygons, edges, points) is assigned ID 12109. For the "shift+delete" to work the way you mentioned you could assign it to some script, which does a delete + clean up. Which is probably easier to create than this whole plugin I made ... Again, didn't think of that. My pleasure.
  12. I am working on a new plugin, and would like to query for user interest. Background info: I am not an expert at modeling, but from time to time I create some objects for short stories I am making, or other projects I am working on. For the past 2 years or so, I have spent most of my time writing some plugins. As such I didn't quite follow the progress of modeling tools (or lack thereof) in the recent Cinema 4D releases. Recently I was creating a mesh, representing a faceted low-poly gnome to be used as illustration for one of my plugins, when I noticed that removing polygons still left orphaned points behind. Same behaviour as always, from the early days I worked with Cinema, till the last time I modeled something before focusing on plugin writing, and then even today. So, over the span of 10 Cinema 4D releases (R9 - R19), nothing seems to have changed regarding this behaviour. Now, I can understand some of the reasoning behind the current behaviour. Still, I wonder how many requests I have submitted to MAXON over the years, to provide an option to allow the user to decide if orphan points should, or should not be removed automatically when deleting polygons. I don't know what R20 will bring, but I didn't want to wait any longer for MAXON to provide said option, and decided to write my own plugin to perform the task of removing these orphan points ... while providing an option to do so or keep the current behaviour (avoiding the need of removing the plugin when user wants to switch between these different behaviours). The plugin: It's a free R17-R19 plugin, currently Windows only, but will be made available for MacOS when time permits. It might also become available for R16, but nothing promised at this time. The plugin is document based, and simply runs in the background. No user interaction is required, as removal of orphan points is done automatically, whatever mode the user is working in. Simply enable the plugin (scene configuration) ... and model away. Naming request: Since the project is still ongoing, I haven't decided for a final name yet. The project is currently named AROP, short for Auto Remove Orphan Points. But could as well end up being named URP (Unused Point Remover), or anything closely related. If anyone comes up with a fancy name, just let me know. Beta testing request: As with all my plugins, it is closely based on the workflow I am familiar with. While good enough for me, this might not be the case of more expert users, or even beginners for that matter. As such, I'd like to ask for a few people's time to spend testing this plugin, before being officially released. Contact me for details. Most important feedback I am looking forward to: - is the plugin slowing down the performance of Cinema 4D - any lag related to the use of the plugin on small or large objects - are there any orphan points still left untouched by the plugin - what's the total user experience using this plugin Thanks for reading Daniel
  13. When I started creating this plugin there were a few features I had in mind, but simply could not find a way to provide these. And while this plugin is no rocket science (far from it), things require quite some tricky solutions now and then. Luckily, I seem to be getting smarter day by day ... yeah, I wish! Still, features I didn't quite know how to implement then, seem to be feasible now. A result of this is that I now have introduced an "auto setup" for assets, which -in theory- should work for most of the assets people are creating. In occasions where the auto setup fails to detect the necessary base and orientation, extra tools are provided to make the manual set up more user friendly. Here's a demonstration video of the latest alpha version I am working on, before going to beta: Another "feature" of this version is a change in library format. Each library used to be a single Cinema 4D scene file, making sharing and distributing single assets a nightmare. I have reworked the whole plugin to work with separate asset files instead. A conversion utility is part of this newer version to convert from the old format to the new one. There is however a major drawback on this new way of storing assets. Cinema 4D takes about 70 to 100 milliseconds to load a scene file. No big deal, you would think. But what if a library consists of 50 assets? That would then take approx. 5 seconds to load and display. Trust me, 5 seconds is a very long time to wait after you selected a library. As such, I also had to introduce a caching mechanism to reduce the loading time of libraries again and again. You'll only have to wait the first time a library is selected. Next times, it should like in a blink of an eye. Next to these changes, the usual bug fixes and optimizations ... no big deal ;) Public release of this new version will be announced when beta-testing has been completed. Thanks for reading.
  14. While your current UV mapping isn't that bad at all, the fact you encounter this (small) distortion is related to the fact that the relation between your mesh and your UV isn't optimal. If you look at the ring of UV polygons at the edge of your circular UV island representing the top of the apple, you'll notice that these polygons are more or less similar in size. Compare this to your mesh polygons of that same ring, you'll notice that the polygons where the checkerboard distortion happens are somewhat larger than their neighbors. In order to get the optimal mapping without distortion, you'd want the relation between mesh polygon and UV polygon to be relatively equal over all polygons. In your case you could move that single mesh vertex to make the polygons more equally sized. Alternatively, you could modify the UV vertex (in the opposite way) to mimic to mesh polygons.
  15. Haven't used Xpresso lately, but there is a Memory node, if I recall correctly, which allows for a history level.