Jump to content


Regular Member
  • Content Count

  • Joined

  • Last visited

  • Days Won


Cairyn last won the day on July 5

Cairyn had the most liked content!

Community Reputation

162 Great

About Cairyn

  • Rank
    Cafe Junior

Profile Information

  • First Name
  • Last Name
  • Location
  • Website URL

Hardware | Software Information

  • C4D
  • OS
    Windows 10
  • GPU

Recent Profile Visitors

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

  1. I did link my Patreon with a specialized course on Python in connection with C4D: https://www.patreon.com/cairyn There may be an e-book later with the first six sections. If you mean "for free", you can find pure Python courses on the web, and you can use the documentation on the C4D Python API, although that is not very good for the first steps. I think there are also some YT videos, just search for the newest appropriate content.
  2. Virtual Walkthrough is ultimately only a camera movement, though. I could replace it with a bit of scripting. The functionality of the sound rendering, on the other hand, is impossible to reproduce now with onboard means, unless you know how to mix and distort sound for multi-speaker channels and program your own plugin in C++ ("onboard means", haha).
  3. I cannot use it because it's no longer there. Does anybody know a free sound program that can import 3D position data of microphones and speakers, and render the sound effects appropriately?
  4. Thanks for the info. ...I just bought this upgrade two days ago, and I already seriously doubt that decision.
  5. I just can't find the commands for Loudspeaker or Microphone any more. How's sound rendering working in the R23 now?
  6. B too - with the basic Attribute Manager functionality
  7. While nodes may be somewhat equivalent to programming (a "visual click and connect" way so to say) one should keep in mind that even an algorithm of medium complexity will become a nightmare spaghetti of nodes and connectors when expressed through nodes. Setting up (or editing) a simple formula in e.g. XPresso takes many times longer than in plain code form, and it is less readable. Which is why I tend to insert Python nodes in XPresso, and replace whole XPresso setups by Python tags. A question here would be how well Scene Nodes parallelize (which I assume they do, or you wouldn't
  8. Um - then I don't get it. MAXON stopped updating the COFFEE API long before they dropped it completely. Is there anything COFFEE can do that Python cannot do? Is there any reason at all why users would need to learn not only the universal Python, but also a proprietary language? Or a reason why MAXON should expend twice the effort on keeping two scripting languages up to date? (Plus, of course, the C++ API.) If this is just about legacy models, well...
  9. I think (I hope) the COFFEE remark was irony? Leave poor Greta alone, she isn't responsible.
  10. After watching the video, I have an idea of what you want... So far, you have just framed your selected elements. The camera is not in the correct position though: If you just rotate it, so it looks into the opposite direction of a surface normal, then it would lose the framed polygons from its field of view. So, it needs to be positioned on a line that is defined by the middle of your selection and the selection's normal. What you need to do is: 1. Get the selected polygons from the selected object: bsel = selected_obj.GetPolygonS() 2. For all polygons in this BaseS
  11. Hello; what do you mean by "in front of" the selection? You will need to define a position and a rotation, unless you just take the 0,0,0 rotation in your script and position the camera straight ahead - in this case you just need to determine an appropriate distance, but no normal. The easiest way would be: 1. Get the currently selected elements from the object tree 2. For every polygon object among these (you said polygons), get the selection and determine the maximum and minimum coordinates for all, in world coordinates. Then you have a box that you will wan
  12. That's bullshit. I have a perpetual license, but no Cineversity access at all.
  13. I do have a Python course running from the very basics through Object Manager manipulation up to (currently) points and poly functions: https://www.patreon.com/cairyn Of course it depends on your current knowledge of both Python and the API. If you have any special questions, I could help you out...
  14. Your calculation seems a bit weird... at 10K per year, I'd be below the poverty line and would be hard pressed to even pay rent, food, and health insurance, not to mention a car, an internet connection, and a TV set. I would definitely not be able to afford a computer, not to mention expensive software. It absolutely does matter how much you earn, and there are probably more than enough 3D designers who just scrape by. I can't even understand what you mean with "one dollar over price" - if all of your income except for one lousy dollar goes to the software manufacturers, you are th
  15. Ay, there's the rub. You expect something to happen in dependency of the direction, but the XPresso setup only has the ball's x-position as input - the direction is not an input at all, and never checked in the setup. So, the output depends only on the position of the ball, regardless of the range mappers, and thus the door angle disregards the ball's movement. What you actually have is a dynamic situation where the position of the door and the position of the ball interact. If you do not want to solve this with true dynamics, you will need to represent a more simplifie
  • Create New...