Purchase this item to leave a review!

• Crespi Studio

  6 months ago

  I’ve only been able to test it for one day, but my first impression is very positive. It feels like a stable and efficient add-on that does exactly what it promises very well. After a little practice, it also becomes fairly easy to use

• Chris Sargent

  over 1 year ago

  I'm trying to focus on learning Blender but keep getting distracted by finding different ways to destroy objects. This addon is very intuitive and does a great simulation on pretty much default settings. The Smoke/Dust effect is very well handled (easier to use than RBDLab IMO)

• Yamato3D

  almost 2 years ago

  Very nice solution - I have purchased KaSuite, where can I get KaFire sample scenes?

• Jeroen

  almost 2 years ago

  This addon is also great to let trucks smash through walls. It works very intuitive and the results are spectacular.
  When I asked the developer if this was possible, one day later he made a video of exactly that: https://x.com/loranozor/status/1770439630938079719?s=20

  Awesome support and an awesome addon!

• Zentapir

  over 2 years ago

  works fine :-)

• Sow Ibra

  almost 3 years ago

  very impressive addon. love it

• Dan Hodgkinson

  over 3 years ago

  This add-on makes destruction in blender so much easier! Well worth it! Looking forward to playing with this add on to create my videos and images!

• adriventkze

  over 1 year ago

  It works fine when you have a fresh scene and are doing simple things, but once you get an error, you're basically done. Zero guidance on how to fix it or why it's happening. Virtually no error handling. I've made something I'm happy with, I click 'bake to keyframes', and get back some python error 'NoneType object has no attribute name'. The exact same setup works fine when I start a new scene and bake to keyframes works. It's as if it worked when you know exactly what you're going for from the very start, but if you do something in between (like play around with different blaster sizes or sliders for forces), a lot of things stop working. Not always, but *very* often. It's exactly the same scenario when selecting some of the fractured objects and then adding the 'breakable' constriant. Just python errors all over the place and you basically have to start the scene again. And no, none of your tutorials address anything like this. Do some FAQ. Do some troubleshooting. Do some more complex tutorials that are not just a basic scene with two rectangles and one plane where everything works perfectly on the first try. Insanely frustrating.

• 

  picto filmo

  over 1 year ago

  hi adriventkze, we are very sad for your frustration. To make the addon more stable, could you send us blender files with errors and a little explaination of what you did and what you wanted. Sorry for the disappointment. Picto Filmo
• Rodrigo Gasparini

  about 2 months ago

  I bought Kaboom mainly for its destruction, debris, and especially smoke tools. Unfortunately, my experience with it so far has been quite frustrating.
  I encountered several bugs and inconsistent behaviors throughout the workflow. I had issues with fracturing, debris, rigid bodies, and smoke, and I often had to rely on trial and error just to figure out whether the problem was my setup, a limitation of the addon, or simply a bug.
  The smoke system was probably the biggest disappointment for me, especially because it was one of the main reasons I bought the addon. In several tests, the smoke was emitted at unexpected times or positions, particularly when the fractured pieces were activated, instead of behaving predictably and appearing only at the actual impact. Even when following the suggested workflow, it was difficult to get consistent control over the result.
  Another major issue is the lack of learning material. There are very few up-to-date tutorials online, and almost no user-created content showing real projects made with Kaboom. That becomes a serious problem when something does not behave as expected, because it is difficult to find other users who have experienced the same issue or found a workaround.
  The documentation could also be much more detailed. The addon has many parameters and features, but there is not enough explanation of what each one actually does, how they interact with each other, and what kinds of values are appropriate for different object scales or situations.
  It would be very helpful to have proper explanations and practical examples for things such as fracture settings, Krumble, Blast, debris, smoke, mass, acceleration triggers, collision emission, baking, and so on. Right now, there is too much emphasis on what buttons to press and not enough explanation of why you would use each setting, what result to expect, and what can go wrong.
  The overall concept of Kaboom is very good, and when it works, it can definitely speed up tasks that would otherwise take much longer to build manually in Blender. However, at the moment I feel that the user has to spend far too much time troubleshooting and trying to understand behaviors that should be better documented.
  I would really like to see future updates focused on stability, more comprehensive documentation, updated official tutorials, and complete real-world workflow examples. Kaboom has a lot of potential, but in its current state the experience can be very frustrating, especially for someone buying it expecting a relatively straightforward solution for destruction, debris, and smoke.

• 

  picto filmo

  about 2 months ago

  Hello Rodrigo Gasparini, I'm sorry you ran into issues using Kaboom. I don't understand why you didn't try reaching out to us to explain your problems so we could help you and, at the same time, contribute to the addon's stability. But all is not lost, you can still send us a screencast or a Blender file so we can understand the issues. Sorry again for the frustration, best regards, Picto Filmo
• RyanZheng

  10 months ago

  It’s completely unusable, and the developer still isn’t responding.

• 

  picto filmo

  6 months ago

  Hi RyanZheng,
  we are sometimes too busy to be available to respond. However, we always do reply. In fact, by checking the message history, I found our conversation. So I had indeed responded. But I'm sorry if you weren't satisfied with the answer,
  regards,
  Picto Filmo

• Displaying 10 ratings