On 8/13/2018 at 10:49 PM, GalacticCrew said:The question for me is, if I should continue developing it (water, smoke and fire effects are needed for the next projects), or if you should switch to another engine.
Depends on opportunity cost, difficulty of implementation and using it.
But from my limited graphics knowledge those three sound related, ie transparency (with billboarding for smoke/fire) shouldn't be too bad to add and use?
I heard somewhere old dev's used their existing game engine in about 3 games.
It's a great way to recoup investments, focus on game design etc, etc.
I would agree, after 3 times using the same tech, you know it very well, what's missing, where and how to improve.
Then (after the 3 games) I've also heard many just scrap the old tech and redo a new engine with a better design, ie for new hardware target etc.
I agree with @Hodgman limit your engine to your game and I would also add your knowledge and abilities, ie don't go over board with features you don't fully understand.
As programmers, I'm surprised why other programmers just pick a commercial engine to start with.. to me it's counter intuitive and against what software developers should be doing.. understanding problems and coding solutions.
Anyway, I still consider my self a 'gamedev' noob, but I've seen so called experts with less understanding!
It's easy to give "generic advice", but criticizing something with no experience isn't advice, it's foolish ideology, never take advice from noobs!
Also, a DIY engine (be it small or large) is IMO part of the process, which is what game dev is all about... enjoying the process!
Nice thread!
Mike