How does the user interact with the game if there is no user interface? Command line arguments?

@AllanSavolainen Yes I pass in arguments. Although after I load the rendered world into I display certain parameters which can be tuned from the rendered world, can be changed from cmd as well.

Only someone who hates games would be dumb enough to suggest that games cannot have things to say, like any art form.

Vulkan is a serial killer for sure

@@gnatinator physics will definitely not kill you, you just integrate a physics engine like Physx or jolt, rendering is more complex and can't say much about platform support especially consoles

Missed the point. Nobody is making their own renderer/physics engine - that’s what libraries are for.

It also works in a way to let the player re-focus, less effects and flashes will help you re-adjust to the beat and get back into the flow to snowball from there

I feel like a lot of it has been rooted in ego and many points contradict themselves. Don't use X game engine because of bloat and unnecessary features, but don't forget to import all of those library's your going to need to get a level editor working and not use 90% of it. Your not trying to build the next best game engine but its definitely going to be more performant. There's no monopoly on the market but tread as if there was one. Personally I feel the best argument ever put across for this is. Take the steps necessary to achieve whatever you set out to achieve. If you want to make a game, use an engine like unity, godot etc. If you want to build an engine, build an engine. Don't just build an engine for the sake of it. If the game demands its own engine then go for it.

The Witness, The Talos Principle, Minecraft, No Man's Sky, Space Engineers, Elite:Dangerous, Total War series, Dreams, Teardown. These all use custom engines.

@@Capewearer This is a talk given at the independent games summit. I'm not sure the Total War series (EA/Activision/Sega) or Dreams (Sony) are development models that indies should be looking to emulate.

If you have a game like Noita, yeah, you pretty much save time by writing an engine from scratch. Otherwise, there's no need, just go with UE and Cpp.

Definitely depends on what you are trying to sell and what your team is, if it's an art-heavy narrative experience where there's more than 1 artist, an engine would help. If you are building new tech that needs to run fast with no gotchas, a custom engine is a place to start. Ideally a custom engine can be abstracted from the rendering and input into a new framework, even if it needs to be plugged into Unity at the last minute for cross compatibility

I've had issues with that as well because I wrote my engine for Vulkan. I have used WebGL but I'm not willing to port to that just for jams.

And now those engines are pushing for tech that sacrifices real optimisations for blurry smears to hide the frame gen and low framerate Because they have no idea what game you're making. How could they ever optimise for you?

Most junior devs can't code and create whole games via blueprints - that's why most AAA Unreal games are slops that run like sh*t.