Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(2 edits) (-1)

When you call something someone worked on 'gore', you should probably expect a rude response.  Though, other than maybe where I called you a hater -- which seems to be factually accurate given your stated position -- there is really nothing rude in my reply.  Certainly less offensive than 'gore' or trying to cancel me.  I took the time to explain my nuanced position, even though I'm already bored of AI vs Anti-AI internet arguments, and in response you want to destroy me because I'm not doing exactly what you demand.  Not cool.

None of the usual anti-AI arguments even work for this.  I rendered the blog image at home, so you can't really make an argument about power usage or datacenters.  I'm still hiring just as many (actually more than last year at this rate) human-made commissions, so no one is out of work due to this -- even including a full sequence comm for this very update.  Given how many passes of compositing and manual paintovers I still had to do for this AI, it's not even like it was a zero skill or time saving thing for me so it's not even a shortcut.  Your argument boils down to 'ai bad.'

Tools and workflows always change.  Just like Disney going from hand drawn animated movies to computer rendered movies.  Or developers going from custom engines to Unity/Unreal.  This does not remove the human from the workflow.  I think ai haters imagine AI workflow as just one-shotting prompts and slopping it out and calling it a day.  And that's just not the reality for how it works when you have a specific character/setting/pose in mind.  But the anti-AI crowd don't invest time into learning AI because they hate it, so they don't ever have these preconceptions challenged.

I endeavor to keep up with current trends and keeping my own knowledge fresh and up to date.  I want to use the tools to deliver better and more content.  I am not replacing everything in my workflow with 'slop', but yeah, I'm going to take a nuanced and cautious approach of sometimes adopting tools into my workflow when they are useful and good.

The craziest thing to me is my position is not even a hot take.  I have a middle ground take on AI.  It's like room temperature take at worst.  I'm not compromising quality, I'm not cutting back on investment into the project.  I'm taking steps to learn these tools and workflows to deliver better quality and maybe hopefully more frequently.  But the internet leaves no room for nuance, I suppose.

Take that for what you will -- I have zero expectation it will change your mind, but at least I took the time to explain my position.  You can disagree with it and that's fine, but I'm giving you real answers even if they aren't the ones you want to hear.