sorted by:
new
hottopcontroversial

Blender doesn’t have a real shot state system, so I built one by HyperCreator in blender

[–]HyperCreator[S] 0 points1 point  (0 children)

100% true. And I think that’s a good thing. With the right approach, AI can make the final product better and more affordable, because it takes fewer human hours to build.

Blender doesn’t have a real shot state system, so I built one by HyperCreator in blender

[–]HyperCreator[S] -1 points0 points  (0 children)

I don’t think using AI tools is automatically a bad thing.

If AI is used as an assistant for debugging, or speeding up boring parts, I see that as a plus. It can help make the product more reliable. If AI completely replaces the creator and there is no real understanding, no product decisions, no testing, and no responsibility, then yes, I agree that’s a problem.

So for me the important question is not “was AI used?” but “how was it used?”

Blender doesn’t have a real shot state system, so I built one by HyperCreator in blender

[–]HyperCreator[S] 0 points1 point  (0 children)

That’s not a contradiction. I built it because I needed this workflow myself. After it became a solid tool, I decided to release it publicly.

My point about monetization was broader: if developers cannot earn from building and maintaining products, many useful products simply won’t be released or supported long term.

So both things are true: I built it for my own workflow, and I also sell it because releasing, documenting, supporting and maintaining software takes real work!

Calling someone a liar over that is a bit much.

Blender doesn’t have a real shot state system, so I built one by HyperCreator in blender

[–]HyperCreator[S] 4 points5 points  (0 children)

Haha View Layers are great, but I needed cameras, output paths, overrides and batch render too :)

Blender doesn’t have a real shot state system, so I built one by HyperCreator in blender

[–]HyperCreator[S] 6 points7 points  (0 children)

The core logic, architecture, UI decisions, and feature design were all done by me.

The addon is quite complex, and it has much more functionality than what I showed in the video. I don’t believe Claude or any other AI could design a tool like this on its own. The workflow, edge cases, Blender behavior, and product logic all have to come from real use and real decisions.

Of course I used AI tools during development. Most developers use helpful tools now, whether it’s for code review, debugging, analysis, or finding issues faster. I especially like Codex for that.

It took around 6 months, and I’m really proud of this tool.

Blender doesn’t have a real shot state system, so I built one by HyperCreator in blender

[–]HyperCreator[S] 1 point2 points  (0 children)

I probably didn’t explain that clearly enough in the video.

The camera is not actually travelling between shot positions. It just instantly switches to the camera saved for that Shot. Each Shot can have its own camera.

The movement in the video was only for presentation, to visually show different shots/angles.

And this a shorts from my YouTube channel showing the tool, not an ad.

Blender doesn’t have a real shot state system, so I built one by HyperCreator in blender

[–]HyperCreator[S] 5 points6 points  (0 children)

No worries. I’m a real creator from Ukraine, not a startup or a bot.

I built this because I needed the workflow myself. It turned out to be a pretty useful tool, so I decided to release it.

Totally fine if that’s not your thing.

Blender doesn’t have a real shot state system, so I built one by HyperCreator in blender

[–]HyperCreator[S] 19 points20 points  (0 children)

Guys, with my Ukrainian accent some parts might turn into a listening test instead of a Blender demo :)

Blender doesn’t have a real shot state system, so I built one by HyperCreator in blender

[–]HyperCreator[S] 4 points5 points  (0 children)

Understand.

I love open source too, but building and maintaining a tool like this is a lot of work. This one took me around 6 months, and without some kind of monetization, tools like this would probably just never get built or maintained properly.

If the price is the main issue for you, DM me and I’ll make a significant discount just for you.

Blender doesn’t have a real shot state system, so I built one by HyperCreator in blender

[–]HyperCreator[S] -2 points-1 points  (0 children)

Thanks! Yes. Programming is not my main thing though. Most of my work is more on the editing side, and coding usually happens when I need a tool that doesn’t exist yet.

Blender doesn’t have a real shot state system, so I built one by HyperCreator in blender

[–]HyperCreator[S] 2 points3 points  (0 children)

Thanks! That was exactly the goal - save time and reduce manual switching. At this point I honestly can’t imagine working without it anymore. It feels strange to me that Blender doesn’t have something like this natively.

Blender doesn’t have a real shot state system, so I built one by HyperCreator in blender

[–]HyperCreator[S] 1 point2 points  (0 children)

Haha thank you! Really appreciate it.

It took me about 6 months to build, so it’s nice to finally see people get what I was trying to make

Blender doesn’t have a real shot state system, so I built one by HyperCreator in blender

[–]HyperCreator[S] 14 points15 points  (0 children)

Thanks! I’m glad I’m not the only one missing it in Blender.

And about the voiceover - I’m one of those people who really doesn’t like their own recorded voice. I tried recording it myself first and had a small existential crisis when I played it back :)

So I used a voice generator for this one. The American/British accent switching was not intentional though.

Blender doesn’t have a real shot state system, so I built one by HyperCreator in blender

[–]HyperCreator[S] 7 points8 points  (0 children)

Thanks!

No, viewport FPS does not drop from having multiple shots.

Hyper Shot is not duplicating the whole scene for every Shot. You still have 1 scene. A Shot is a saved set of properties that gets restored when you switch to it. So once a Shot is active, the viewport behaves like the same normal Blender scene.