Jump to content


Regular Member
  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by DasFrodo

  1. Without having a look at the scene file I suspect it's either the samplerate of the lights (if you have any) or it's the emissive material in combination with GI that gives you these dots everywhere.


    In the second case, you have two options:

    • Switch primary and secondary GI solution to QMC (increases rendertimes dramatically but get's rid of all artifacts)
    • Massively increase samplerate, quality and density of your GI solutions (increases renderimes as well but probably not as bad as QMC)

  2. On 12/20/2019 at 3:41 PM, Hrvoje said:

    Best bang for the buck configuration at this point would be roughly:


    Intel i9-9900KS

    RTX 2070 or 2080 Super (if you are asking if you need pro card or not then you don't need it 🙂 )

    64Gb ram


    Don't worry that much about motherboard manufacturer, it is pretty much all the same unless you really need some fancy extra stuff. Same for ssd drivers. What is important is good PSU. Make sure it is certified and from known brand. Another thing is cooling of cpu - Noctua is best option there for air, for water there are couple available such as Corsair.



    Wouldn't a 3700X be better? AMD is way cheaper right now and as far as I know even the best Intel Prosumer Chips can't compete with AMD performance right now, even though they're like 30-40% more expensive.


    I've been using a 2700x for a year now and for the price that thing is a beast. 8 Cores 16 Threads @ 4,00GHz while under full load. At the time it was a bit over 300€ but it fell in price significantly a couple of months afterwards.

  3. You could attach a sphere with a certain radius to the camera, make it invisible and give it collision so it basically "pushes" the spheres out of the way when it moves through them. The sphere doesn't have to be big, it just has to stop the spheres from entering the exact camera coordinates.

  4. 10 minutes ago, Adrien said:

    Yes that was exactly my point. I have no idea of how big MAXON is and what problems they have to deal with but as an end customer I can definitely judge their slow pace of innovation compared to other DCC’s and the lack of price competitiveness vs Houdini, Zbrush, or even 3dcoat..and needless to mention blender. 
    They communicated a lot on their new R&D department, they now merge with Redgiant after acquiring RS...but I have yet to see several areas of the program to be overhauled to be at least on par with competition. 


    I'm pretty sure that's exactly what is going to happen in the next couple of releases. There's been more movement around C4D in the last 12 months than in the last 5-10 years it feels like.

    But yes, we'll have to see. Fact is, MAXON is losing the race hard right now and usability and stability can't carry the software forever if many, many great features are missing.


    I did not mean to imply that you can't judge that it's going slow, or anything else. My entire point was to illustrate that judging internal ongoings, especially with software development, is pretty much pointless especially because you and me both have no idea how complex and well built C4D is in the first place.

  5. 10 hours ago, hikarubr said:

    I totally disagree with you. It's fair game to compare MAXON super slow speed of development with pretty much everyone else in the 3D Industry. Every Maya or Blender version has the amount of features of 3 to 4 Cinema 4D versions.

    Also, MAXON has a history of making absurdly crazy decisions about development, like letting BodyPaint 3D basically die, even though it was for a while the industry standard for 3D texturing. 


    But we also get well thought out, flexible and stable tools for the most part. For other softwares all I hear is complaints about tools that don't feel right, stability issues, performance issues, etc.

    Yeah C4D has issues as well, lack of important features that other packages have, bad viewport performance, bad viewport quality, the list goes on.

    But honestly I'd rather have a software that crashes once a month or less than a software that crashes once a day. Stability is really important for me, and so is ease of use which is why I have stuck with C4D for so long.

    As for Bodypaint: I've never used it and at the time it was not relevant for me at all, so I can't comment on that. There's tons of stupid decisions like that throughout the industry though. Just look at Autodesks Mudbox.

  6. 18 minutes ago, MauricioPC said:

    We can agree on that! 🙂


    I just wish RedShift was part of Cinema, not an extra payment.


    Same man. I was really excited when they bought Redshift and I pretty much expected it to be Standard C4D render by R21 but oh well.

  7. 2 hours ago, MauricioPC said:


    He doesn't have to know, he's a customer. What he needs is a better tool and he can demand that without needing to be a specialist in engineering or software development.


    I never said he doesn't. All I'm saying is that stuff like "this should be done by now. why is it taking so long maybe they shouldn't buy more stuff when they haven't even finished integrating redshift." just isn't how software development works.

  8. 40 minutes ago, Adrien said:

    I was actually hoping to see MAXON follow Autodesk’s steps after their acquisition of Solid Angle and the quick integration of Arnold as their  new default tender engine.
    I’m not a programmer and I have no idea of how long this type of integration takes. Maybe AD botched the integration, who knows...I’m a simple user and just noticed that competitors deliver more stuff and often faster. Look at where Zbrush was just 3 years ago...

    C4D is still great, MAXON’s  communication is improving, but the program is falling short of several features. Meanwhile,  the  integration of RS is not completed yet and now this acquisition of Redgiant...Seems like  they might be spinning too many plates at once. 


    No offense but you need to stop assuming stuff you don't know anything about. That is NOT how software development works at all. You can't just throw people at a software and the development speed scales linearly. People need to be integrated into the workflow, need to learn the codebase and so much more, so you get the quality and stability of features you expect from MAXON toolsets, otherwise you will get Maya / 3DS Max level of stability.


    The Red Giant team is probably not touching areas  that are related to the Redshift integration at all. It's just the same as every single video game community. People scream "Oh my god why do they integrate more cosmetics instead of fixing their horrible netcode". That's not how it works.


    I'm not praising MAXON here, they sure did a couple of very questionable things in the last couple of months but expecting a complete and tightly woven Redshift integration in half a year is ridiculous.

  9. 3 hours ago, EAlexander said:

    Thanks - o big secrets over here.  I use corona (which is awesome) and has a very nice denoiser.  Most of these shots are rendered in about 6-7 minutes on a 10 core windows machine - so no magic there.  I use area lights for everything and try to use lights more then HDRI whenever possible.  Just gives me more control.  When I have a few moments I'll post a scene file you can dig around in (though you'll need Corona).  Thanks for looking and always happy to answer any questions.



    That'd be super great! Lighting is the one thing I still struggle with a lot, granted I haven't invested too much time into actually perfecting it.

    Simple question, do you work on these renders afterwards in Photoshop or something similar? Or do you use the renders as they are?


    I feel like Corona NAILS those rough surfaces like no other engine, looks silky smooth.

Latest Topics

Latest Comments

  • Create New...