Jump to content

Visionnext

Regular Member
  • Content Count

    389
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Visionnext

  1. You get a warning as well in Firefox
  2. Improved cloth and dynamics simulation. Liquid simulation would be nice as well. Better file import/export (e.g. FBX)
  3. Yes, but it is based on FBX as well, thus - no HD morphs - no morphs that are joint movement controlled This may not be necessary for animations, but probably for stills and close-ups. Otherwise it seems to work fine...
  4. Yes, unfortunately. @Rectro already assumed something like that. So it's not really an alternative to Vray for me.
  5. Unfortunately some great tutorials by Vertex Pusher (aka @HSrdelic) are no longer available. I learned a lot from them. There have been improvements in between with the character templates, but he really covered the basics well.
  6. Sorry, just didn't realize that it doesn't work on Mac although it is a Daz plugin. Seems that Mac doesn't get the love, they received in the past by independent developers. Apple has to push the Mac again...
  7. There is a plugin for Daz Studio, Headshop Pro 11 https://www.daz3d.com/headshop-11-win I's not free and it seems to have some bugs that will be solved with updates, but some people get some good results with it.
  8. First of all, I want some constructive discussion and not a war :) At the moment I'm using Vray 3.6, but with the transfer of Vray for C4D to Chaosgroup, I think about alternatives. I render characters (skin, hair) and mainly stills. So far I followed @Rectro tips & tricks and used the alSurface Shader in Vray for skin, which delivers quite good results out of the box. So, criteria for me are - Skin & Hair - Node based material - Integration in C4D - Maturity & future-proof - Licensing model (perpetual versus rental) I love to her about your longtime experience and your pros and cons about the render engines you use. I plan to get a new gear in 2019 and probably change the render engine latest with R21. Thanks in advance and a Happy New Year to all of you and your families.
  9. I started a document with a detailed workflow for transferring G3 to C4D, which includes the usage of Vray 3.6. Assigning materials should be done with a script, but I need to develop a reliable and flexible approach. Another long-term approach includes the transfer based on FBX, but this involves Daz Scripts and C4D Scripts/Plugins and is a more complex topic. I would definitely need more time for that, but I don't have it now. Let's see, what 2019 will bring.
  10. Ok, here is my workflow for Genesis 3/8. First I use the following export settings in Daz Studio Then I use the following C4D import settings I would advice to check Invert Transparency to get the material right by default. Nevertheless you will need to adjust them to get the right quality in Cinema 4D. I have to adjust them anyway, as I use Vray as render engine. I made a set of textures for this purpose and replace them every time after I import the OBJ. his can be automated by a script, if repeated often.
  11. You may need a Vray Blend Material. This allows to stack different vray materials.
  12. One route that works most of the time is to work with the Riptide Pro Plugin. Load the OBJ and the Vertex animation (*.mdd). You will need the mdd export for Daz Studio as well. FBX has a lot of issues, as you do not get the joint controlled morphs (JCM) and the default position of the joints over to Cinema 4D.
  13. Started with an Amiga 500 myself and aquired a 2MB memory extension plus a 20MB Harddisk. Sold everything for a 386 PC, as I needed this machine for my diploma thesis in 1990. Returned to CG with Poser again in 2003 and to Cinema 4D with R10.5 So, I assume myself as old as well :)
  14. I'm interested in a perpetual license as well, as Vray went over to a subscription model. I looked at Arnold, but I'm familiar with Vray and it may make no sense to change from one subscription to another. I search for a 3rd party render that works nicely with skin and hair and supports CPU.
  15. I get a different feeling from plugin providers. They always said in the last 3 years that a new version of their plugin is required. Maybe this is just marketing though.
  16. Maybe I didn't express myself correctly. I just mean that it should not be necessary to recompile or change the plugin every time a new release comes out. If they keep old functions/interfaces for a while in the SDK, this should be possible. With the last versions the SDK seemed to have always changed, as you always needed a new version of the plugins that I use.
  17. I'm a hobbyist as well and started with Poser in 2004. I changed to R10.5 a long time ago and have an MSA since then. Keeping the MSA alive is something I decided to do, because I simply like C4D, although in the last years it seemed to me that C4D had some hard time to keep up with the best. Bodypaint, Clothilde and other features are no longer on top compared to other software. C4D should provide a stable and efficient SDK to support plugins that can do a better job and help them to run on newer versions. I'm still on R18, as I cannot afford to get upgrades for all plugins every time a new C4D version is released. Nevertheless I like C4D as I learned to handle it. I don't want to change horses, but I expect some major feature improvements with the new core, a decent price tag and a perpetual license. I use Vray as well and think about leaving it, but I have to find a reliable alternative first. C4D stays on my tool list so far.
  18. The thing that keeps me with MAXON and the MSA is the perpetual license and the hope that with R21 we finally get the things I've waited for a long time (SDK for node based material, improved Bodypaint, better asset management, improved import/export options). If MAXON no longer provides a perpetual kicense, I will probably change to Maya, as I'm focused on characters lately. I am not a professional, but did some work for friends, which they used in their companies. If I cannot afford the MSA any longer, I can still stay with my perpetual license. A real problem in the past have been the plugins that have to be updated with every MAXON release. I'd love to get a more stable SDK or at least some backward compatibility, by providing a backward compatibility layer. I'm still using R18 today because of some plugins that are more important than the new features. R21 may be the next version, I go for.
  19. Would be nice to have someone, who can adjust the plugin to the newest SDK and recompile it.
  20. I would love to see your Tyrion rendered in Corona. By the way, thanks for the breakdown on YouTube!
  21. Yes, but according to Stefan Laub, there is no functional difference between 3.6 and 3.7. Just a difference regarding licensing (keyfile versus licensing server). No need to change to 3.7 for that, if you already use 3.6 with a keyfile. This will certainly change with C4D R21. You can only install one Vray plugin in a C4D version at one time.
  22. I'd love to visit New Zeeland one day, but it's really not next to the middle of Europe :( Have fun though :)
  23. That's how I understood it. Nevertheless the Vray 3.6 license is a perpetual license. For R20 users, especially on Mac, the use of 3.7 might be necessary. As I'm still using R18, I will continue with Vray 3.6. I may switch to a newer version with R20, but this will be limited to January 15th, 2020, unless I pay the yearly/monthly fee from then on.
  24. Sounds interesting! Let us know about your results. A node editor would definitely be nice. As I also focus on skin render (not as good as you are so far) I'm really interested in your results. Displacement is another important topic. To apply different maps to different selections would be nice, but I can live with UDIM support as well. Thanks for your helpful tips and trainings Walter

YOUTUBE CHANNEL:

ABOUT US:

C4D Cafe is the largest CINEMA 4D community. We provide facilities for discussion, showcasing and learning our favorite software :)
×
×
  • Create New...