Leaderboard

Hello, I am sharing my personal utility class that contains a lot of functions that help to compute some geometrical data on meshes, selections, mesh editing, splines, normals, polygons and more : https://code.vonc.fr/utils It's still in construction, there is more to come, the descriptions are not yet translated in english, there is not yet images for all, it's not all in Python 3 yet too, but I am working on it. 🙂 I am also making a C4D file that contains all theses functions, like a bit unit test file where you can play with each function. I am searching a way to make a better presentation of it because it make a quite huge page actually, I'd like to have your opinion on it. Here is also a specific chapter on bezier curves in a more tutorial way to understand them : https://code.vonc.fr/courbe-de-bezier And if you are interested, there is more stuff on my website, not necessary C4D but still 3D oriented. I think will post here when I will translate some bach of them, with images. I hope this stuff can help some !

Hey gang, It's January 2022, and I am in the market for a new desktop computer with which I can use Cinema4D. I especially want to be able to home render C4D frames as fast as possible. I have $2300 to spend. No more... a strict ceiling on $2300 US. I'm not a gamer at all, so gaming is not part of my criteria here. I just want a (Windows 11 x64) desktop that renders C4D projects as quickly as possible. I also use Adobe After Effects a good deal. What combination of processor...memory....videocard can you recommend for me, with a strict ceiling of $2300 ? Naturally, I want a setup that will not obsolesce anytime soon. I use a cabled modem Ethernet to work the Internet. Thanks, rasputin

Sure, sweep tool could be a bit "smarter", but sometimes user needs to adjust splines in some angles or add/remove points etc...

here is update... - first must scale project since working with 0,001cm resolution is not really good. Always try to work with real dimensions. - profile spline was not flat at all, spline points was in all three directions and scale of single parameter was 0 instead of 1. - path was recreated from your profile by an eye. If needed higher subdivision, you need add more points to path spline... Cookie Cutter Design_01.c4d

Belated Happy New Year everyone. May everyone enjoy health and a full return to a pre-pandemic normal life this year (finally). May your polygons always be 4 sided, your edge-flows well defined and your poles never exceed 4. Finally, may you boldly push your talents in 2022 farther than they have ever been pushed before with the confidence that your DCC application will never let you down. Dave

OK, can't believe no1 has done it yet, so I will take the hit for us all... My New Year's Resolution is 3840 x2160. CBR

Regardless of budget, if you buy AMD processors rather than Intel you are always getting better value for money, and often, better performance as well ! So that seems the first best advice to give you. I have been very happy with my little Ryzen, which stops just short of threadripper-land with 12 cores, or 24 threads (I was on a roughly 2K budget too). Multiple cores are very important - specially if you want to be doing other things at the same time as Cinema (browsing the web, socials, other applications), but you also need the highest clock speed you can afford for those cores because there are still processes in C4D that only use the one. Quick advice on motherboards - once you have selected your processor and determined the class of MB and chipset you need to support it, there will be a range of options using that chipset from 'basic' which is usually the best value for money through several more variations and up to the 'gaming' version, which will be exactly the same thing except covered with extra lights and attractive bits of plastic ! This is all expensive and for the most part totally unnecessary ! However, sometimes these turbo versions come with extra USB ports etc, so find the lowest version that gives you what you need in terms of peripherals and expansion capability. For example I went with the Gigabyte X570 chipset, but saved at least 100 pounds by getting the UD version without any bells or whistles. the only compromise I felt I made by doing so was that I only got one NVMe HDD slot, which I can live with, given that I only need those insane transfer speeds on my system drive, SATA being fine for general storage. Also, SATA drives are cheaper than NVMe ones, so more savings there... And don't skimp on system RAM either, or the speed of it. Get the fastest you can afford in the biggest single chip size, so that you save RAM slots you can populate later if needed. Increasingly Cinema and other apps consume vast amounts of it - occasionally I find my 64 GB isn't quite enough for really big scenes, but with half that RAM I would find I was running out rather more often. In fact I would go so far as to speculate that 64 GB is a decent amount these days for most machines. CBR

To the people of the future who have had similar problems as this one, i have a workaround, instead of using PSD files for the sequences use OpenEXR instead, and use extractor in ae to extract the channel datas!

I suspect if they could fix that they would have done so by now... it has been the case for quite some time... CBR

Hm? Actually I prefer not be drawn into (as Cairyn would say) "one of these threads". Also I'm not sure, which insights I'm supposed to share. I assume, I'm being asked as developer and not as a former Maxon employee. So I will keep it more general. From my point of view onboarding new developers is (or at least can be) a difficult task. It almost always takes quite a bit of resources (aka time of already experienced developers) for a significant time. Every developer is different. And like all humans every developer learns differently. Can bug fixing be a good learning path? Yes, I think so. If you have a tenacious and masochistic type of a developer, this can work out great. I do not mean this in any bad way. Maybe in other words, you need somebody with a lot of will to reach the goal. If you have someone with such characteristics, then the result can be awesome, because the knowledge collected on the go is immense. On the other hand there the "this baby has to run as quickly as possible" type of developers. For those a smaller or simpler starter project can offer a better learning curve, as they have better chances to reach the needed feeling of success to keep them going. Also bugs are pretty human in this regard. Every one is different (I hope, now I do not get drawn into a discussion, how theoretically many bugs are identical) and like with humans you can't really judge it by looking at its cover. So it can already take quite a lot of work from an experienced developer to judge, if a bug is suited to be worked on by a beginner (usually you want "isolated" bugs, where the fix has little potential to influence or break other stuff). And afterwards you need an experienced developer to check and verify the fix of the newbie. This can lead to a situation, where it costs more resources than would have been needed if the experienced developer worked on the bug in the first place. I think, comparing Blender and C4D in this regard is misleading and probably also a bit unfair. Open source in a way is way better suited for onboarding new developers. Of course a) the code base is open, so chances to get somebody, who already has some experience, are better. And b) there's a kind of playful flavor in the process, which you usually do not have in closed environments. I do not want to say either way is superior. It's different and the difficulties are different. I don't think, it's a good idea to transfer the paradigm of either to the other. And of course either side can also learn from the other, but chances are the result of such learning process or evolution will not be identical to the other side you started to learn from in the beginning. The constraints are too different to end up with an identical result. I could go on talking for hours about this, but as I said in the beginning, I'm not even sure, what I have been asked for. For example the topic, how many interesting ways there are to make even the best developer have merely no output at all. Although I tend to like the view from the other side a bit more, the many ways you can get productive output from bad developers (or as I would put it, there are no unproductive employees, only employees used in wrong ways). Or the topic of team mindedness of developers, something my breed is probably not really the best in (which on the other hand is most likely the reason, they got developers in the first place...). Just to be not completely off topic: I see nothing wrong in a service pack focusing on bug fixing. And I'm a bit irritated, about certain views for example about the number of bugs in "UI change" release. To me it's pretty obvious, even if there were no features to present, there is way more work going on than visible at the surface. Please, do not misunderstand this, I'm not interested in another discussion if R25 is a release worth its money. Or if the communication strategy is right or wrong. Or Maxon's business strategies. In my view Maxon tries nothing less but rebuilding a skyscraper from scratch without scratching the old facade during the process (better: with as little scratches as possible). Or trying a heart surgery on a living walking human without any support machinery. Not many companies have even dared to try this. For this alone they have my fullest respect. It's even worse for them. Their customers grew used to one of the most stable and backward compatible software products (not talking about DCCs but software in general) out there. And for such an endeavor this luxury turns into an immense burden. Whatever you do, somebody will always be pissed (even worse, most likely rightly so). And I doubt, many can imagine how different, how much more complicated and how much more time consuming this is compared to building something new from scratch. Maybe not even all developers at Maxon did foresee the complexity to its full extend (which is no critique). I mean, hell, I live in a country, where we are not even able to build an airport from scratch anymore. Something which has been done thousands of times all over the globe. Complexity is a bi... and forums can be a bad place to discuss complex topics. Most humans are not interested in understanding complexity. We usually prefer the simple, black/white answers. And, again an example from the country I live in, people can get pretty angry and even violent, if the answers to questions which frighten them are neither black or white (yep, talking pandemic here). I think, same patterns can be seen in the C4D discussions since a few years. Understandable. Inevitable. Certainly not constructive or helpful for anybody. Sorry for being carried away. Probably another reason, why I shouldn't be pulled into threads...