• fahad

  over 2 years ago

  I have been using K-cycles for about a month, I would just want to say that this is the best add-on I have found (100/100) Thanks a lot. Saved a lot of time + great results. I just have a question about the new update( the mist) is it possible to have a short tutorial on YouTube of how to use it to add the mist?

• 

  Eric Klein

  over 2 years ago

  Do plan to do video tutorial on the new K-Cycles features Mist and Animation Denoising.
• Gil Elnekave

  over 2 years ago

  Awesome value, in some scenes just keeps on crashing though, couldn't isolate the issue.

• 

  Eric Klein

  over 2 years ago

  Most of this crashes can be caused by not enough GPU memory, configuration or blender core bug it is rarely a K-Cycles issue. K-Cycles can adjust the GPU memory by changing the GPU Boost mode and with configuration issues doing a clean install helps. The install guide has troubleshooting section with solutions for most common issues.
  I also have customer support for problem scenes and will investigate to find a resolution.
• HorvatH

  over 2 years ago

  After a quick test, great first impression! Thanks

• Wilbur Post

  over 2 years ago

  Seamless and easy to use--and it's a bargain. Thank you!

• Digital Designs

  over 2 years ago

  Love the lens flare and added options and speed.. A must for anyone using 30s series GPUS.

• moustady

  over 2 years ago

  Surprisingly good

• Piotr Podermański

  over 2 years ago

  Ok, this is brilliant. I was able to lower rendering time for an animation from 15 minutes to 2.5 minute per frame, mostly thanks to the build in denoiser, which worked great on preserving movement details. Renders most scenes 2x faster, but with Ultra Denoiser it allows to squeeze out even more speed.
  Camera FX is also a great plus, especially "bloom" which is often hard to match in post. Having bloom and other effects right in the viewport is a thing I often missed in Blender, be it just for preview, or even, often, for the final render.

• Noa

  over 2 years ago

  Viewport performance is excellent, and I'm happy with the changes to the render panel to make setting up a render more user friendly.

  My main issue with K-Cycles is the user experience when it comes to actually rendering out a scene. I'm sure for professional artists this is may not be as much of a concern, but for the average hobbyist who goes through a trial and error process on low to upper-mid range consumer level hardware, the lack of render previews is a major, major downside. K-Cycles does not update the render preview as frequently as the core version of Cycles (which updates every sample).

  K-Cycles displays a render preview every X number of samples (64, 320, 640...). This is not related to the number of samples the user defines. What this means is you won't see ANY of your render until it's finished (if using 64 or fewer samples), or you will only see the 64 samples preview if using less than 320 samples, etc.

  This effectively neuters one of the defining advantages of progressive refining - the ability to set an arbitrarily high sample count and ending the render early once it's at a satisfactory level, then optionally using that as your baseline sample count for future renders in the same scene.

  On a personal level, I would rate this product at a 3/5. It's a solid improvement to the CyclesX experience when working in the viewport, but I find myself doing my initial renders in the core version of CyclesX due to the reasons mentioned above. When rendering heavier scenes in K-Cycles I often find myself wondering if Blender has crashed, simply due to how long it has been since the render preview has updated.

  However, this is ultimately nothing more than a nitpick for many users, and I have spoken to Eric who seems potentially open to improving this aspect of K-Cycles in future versions. For that reason, to be fair to the creator, I'm officially rating at a 4/5.

  It's priced fairly, and it does what it advertises. I would happily rate 5/5 if customers could manually define our own update preview intervals, or if this optimization could be optionally disabled entirely and the core CyclesX method of update previews be used instead.

• 

  Eric Klein

  over 2 years ago

  I have change render preview updates, so it is time based. First update comes quickly and updates at the beginning come more often to allow easy cancellation. This should resolve your criticism about K-Cycles render preview updates. Thanks for your comments.
• BlenderMagic

  over 2 years ago

  E-CYCLES YES!

• SPLEEN VISION

  over 2 years ago

  outstanding performance! by far the best purchase i made.
  example: an car animation that took about 3min/frame with cycles in 2.93.
  normally i would send that to a renderfarm (500frames). i am now at about 45seconds (!!) because i can take few samples with the k cycles denoiser and still get a FAR more detailed result than before.
  mister, im a new lifetime costumer!

• Displaying ratings 31-40 of 89 in total

Purchase this item to leave a review!