Vibe coding an engine is way harder than vibe coding something onto an existing engine. It’s something I have worked on for fun in my free time.
I have the ability to make the engine I’m making on my own, but trying out AI for the experience. It really sucks in ways that make it good for what an engine needs. A good engine needs to plan pretty far ahead and plan well at high architecture level. AI is actually awful at that despite it being okay at making plans at implementing said plan.
Could you give an example of something excellent and either innovative or influential that did not sell well? It’s a question I have sought to answer myself. Especially if you can find one that doesn’t take development costs into account.
So I’m looking for an “objectively” (figuratively) excellent game, that has not sold many copies at all. A game on steam that should be popular but isn’t. Do you have any examples?
It isn’t like that, and it is true. Lots of games in a specific engine share common traits. From physics, to rendering, to more specific engine stuff (think of using the full suite of lumen/nanite/ue5 rendering whatever).
Even the character actor can sometimes feel similar. Visuals are by far the most indicative thing of an engine. Don’t forget about unreal’s awful shader stutters.
calling that ridiculous is extremely strange. Feel free to prove it false I guess?
> It wasn't a pedophilia scandal, as around 80% of victims were post-pubescent male teenagers. It was a homosexual ephebophilia scandal. Still terrible, but it does shift understanding of the nature and source of the problem significantly.
I feel like this pseudo-defence hidden in the middle of your few paragraphs tells the reader what they really ought to know. Making that distinction is enough to question your nature to be allowed around vulnerable people.
I don’t understand the point of denying reality when it unfolds in front of you. Plenty of evidence for these things. Denial of obvious truth is an American epidemic and cultural export
The kind of mistakes it makes are usually strange and inhuman though. Like getting hard parts correct while also getting something fundamental about the same problem wrong. And not in the “easy to miss or type wrong” way.
I wish I had an example for you saved, but happens to me pretty frequently. Not only that but it also usually does testing incorrectly at a fundamental level, or builds tests around incorrect assumptions.
I would assume it’s something based around whatever deacceleration animation it is calculating? So in the inverse of what you would see in games that don’t support uncapped framerates. It would at least explain why the refresh rate has an inverted relationship
I agree with everything except for it being anti-thetical to good practice. I have noticed a lot of experienced devs agree with that sentiment.
It has been a pretty common trend for the last few years of people breaking out of the “OOP style programming” and practices they were taught at university. I am not saying avoiding things like over abstraction is new, but I do think there is a newer generation of programmers who have been taught and warned about drawbacks from practices like that.
Similarly, my anecdotal experience tells me more newer game devs are aware of basic memory practices being better than overly complex OOP code. Think flat arrays and simple cache alignment over something abstract and over engineered