Jump to content


Regular Member
  • Content Count

  • Joined

  • Last visited

  • Days Won


Cairyn last won the day on November 6

Cairyn had the most liked content!

Community Reputation

179 Great

About Cairyn

  • Rank

Profile Information

  • First Name
  • Last Name
  • Location
  • Website URL

Hardware | Software Information

  • C4D
  • OS
    Windows 10
  • CPU
    i7 3930
  • GPU
    GTX 1080

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. It's not that difficult to realize if you just want to implement your algorithm exactly that way. (I suppose the result will be a new spline object that is inserted after the multisegmented one.) Unfortunately you may need to program it yourself (if you have Python knowledge) or commission a script (if you have a budget). It's really very specific. Fortunately, 200 points is really not that high a number, so you may get something to work with a brute force approach. Finding the closest point on each spline to each first point on another spline will not be that challengi
  2. Oh, I thought you meant a feature of the R23 release. This folder existed back in the R19 already (probably since the vertical tags were introduced, but I wouldn't swear on it...)
  3. Default folder? I may have missed that as a new feature, and I can't find it in the help, could you point me at the functionality?
  4. The vertical tag concept has two issues: first, it changes the way you select. Normally, the object side and the tag side of the object manager window work "independently" when it comes to clicks and selections. When vertical tags are activated, tags become a part of the object list on the left side - clicking a tag means deactivating an object that may be selected. (etc, I don't want to describe the full behavior). This could have been avoided if the tag list would still appear on the right side, but vertical and with names. Maybe the current design has been chosen so a vertical-tag object ma
  5. That's not always giving you the shortest connection. You already throw away potential candidates for shorter connections in the first step, and do not measure the length of the spline segments at all. Your graphic image happens wo work because you set it up to, but imagine the last point of the middle spline would veer off to the right. Then the shortest overall distance would require that you jump from the upper spline to the lower spline directly, although the p2p connection there is longer. You also get suboptimal solutions when the spline with the closest jump point is actually meandering
  6. I had read this on PluginCafé. Just confirms that there is an issue... It would already help if we could move the priority of the spline, but that is not possible, and the spline apparently is not moved in priority either when it has tags which are executed much later. I don't quite understand how the C4D priorities arrange themselves when it comes to prios that are defined by the user in the tag list - certainly it doesn't work like I'd expect to...
  7. There are more icons that adapt their image to the current state. Try the dynamics tags for example. (The light icon also comes in the light's color...) Programmatically, C4D asks your plugin for the icon, and you can return one of any number of icons depending on what major status you want to convey to the user. I'm more astonished about the icons that can arbitrarily change color, because there you need to mask the actually colored area and modify the bitmap on the fly. On the other hand, the vertical tag concept could be better. You cannot use it for single obje
  8. I don't know whether it's completely unfixable, maybe there is a convoluted way of doing it through history states, or by replacing the whole thing by Python code, but I don't know whether I want to spend more time on the issue at the moment. However, it is known that C4D has some issues regarding priorities; this may be an example. Only MAXON could truly tell.
  9. I still have a subscription to 3D World, because I am old, and I like to have some curated content that I can read in bed. Sadly there have been many issues lately, from missing download content (I told them; they never reacted), lost issues (I told them; they didn't answer), a pest of so-called "advertorials" (I can have that on the web for free, thanks), and COVID-related delays. They also restricted the number of issues that you can get replaced, and the issues I most wanted this summer are exactly the ones that got lost, and they don't offer replacement, so I am pissed at them and wil
  10. I had a look at the file, and I don't see an obvious error or a way to fix the priority. The spline is always evaluated before its points have been modified, and there is no way to move the spline to another place in the priority list. I tried to replace the XPresso by Python (node and separate tag) to no effect. Even sending the spline a message (points changed, update, set dirty) has no effect (R23; I suppose these messages are not sent from a tag anyway?) If the XPresso tags on the nulls are reduced to Expression, the nulls themselves start to lag (although nominally they are still evaluate
  11. You can expand your script to merge layers, if you take care that you generally don't have layers of the same name (which would also be affected even if not imported): Go through the list of layers. For each layer, look at all following layers. If there is a layer of the same name, move all objects in that layer to the first layer (from memory, I don't remember whether there was a function for that; if not, you need to go through the object and material lists). Delete the second layer. This of course means that if the 2nd layer has the same name but some other prop
  12. If you're working with R23, you can use the Retarget workflow. But don't use the retarget tag, rather use the Character Definition and Motion Solver tags (read the description in the help). This will allow you control one rig with the animation in another.
  13. "ceased to operate", as in? Error message? Doesn't start, without comment? Crashes?
  14. A, B, and C are all Chest. The bones are set to "To Child" so if the chest joint has three children, you get three bones in the viewport. In other words, you have no shoulder (Upper Arm begins right after the chest, with no shoulder or clavicle in between).
  15. I don't think it's possible to check which object/material is "older" than another, especially when they are from different scenes. This may be more complicated than you think. If you want to go deep, you could insert your own data into the BaseContainer of the material and thus mark it as "original", but that's nothing you scribble down in two minutes.


We are dedicated Cinema 4D Community of friendly and passionate artists, hobbyists and developers. Feel free to join us and share your knowledge, your art and anything that might help Community to grow. We are providing guidance, free plugins and files, feedback, sponsorships and various discounts for our Contributors. :cowboypistol:




  • Create New...

Copyright C4D Cafe © 2020 Powered by Invision Community