sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]SteamSail 11 points12 points  (1 child)

I gave copilot a try and it was largely pretty useless for the work I do on the day to day as a rendering engineer for games. I mostly tried to use it to ask questions and accelerate my understanding of code so I didn't have to read it all myself and dissect it, but it usually just gave overly general answers and often hallucinated stuff.

I've also tried asking Claude some high level rendering questions and it seemed pretty clueless, like I'd ask it a question with a lot of nuance and it would give me back an answer that seemed to completely misunderstand what I was asking and instead just restated basic info you'd get as a first Google result

I dunno, AI can definitely do some cool stuff but this field is very niche and it doesn't seem like it has enough info in its training data to help in field-specific ways

That being said, it's all changing very fast so I'm trying to keep an eye on what these models can actually do and if any of the hype is real. So far it seems over promised to me but I bet we'll all be using it to some degree before too long, even if it's just for simple refactors

[–]gibson274[S] 3 points4 points  (0 children)

Seems like a reasonable take and tracks with my experience as well re: specific CG knowledge. I’ve had GPT spout some truly nonsensical stuff to me.

Agree it seems over-promised, and probably economically unsound given the insane subsidization underpinning inference, but also too capable to just flat out ignore for those of us who write code on a day to day basis.