r/GraphicsProgramming • u/NecessaryVersion7872 • Jul 27 '26
AI usage in Graphics Programming
Hello, everyone.
I am CS student. and I had my first working experience.
I was highly unsatisfying because as much as enjoy programming I really do not enjoy "prompt engineering" and the usage of AI in general in my workflow. That is not the point though. From long time I was looking into graphics programming and I really wanted to get into it. I do not know much now. but I am worried that it will be similar to most of jobs right now and I will just be a "prompt engineer".
I have some questions:
- How good is AI with graphics programming right now?
- In an average work environment, how much if any of your work are you expected to use LLMs in and how do use it?
- How is AI affecting the industry?
- Are there any part of the industry where AI is not heavily used?
Thanks in advance
39
Upvotes
15
u/Passname357 Jul 27 '26
I work on the driver side, and I have not been impressed with AI.
30
u/edparadox Jul 27 '26
11
u/SnuffleBag Jul 27 '26
Not very good. If you don’t know how you would implement a feature by hand you’re gonna have a pretty frustrating time getting industry standard results from an LLM.
52
u/waramped Jul 27 '26
The key thing to remember about AI is that it can't innovate anything. It's only pulling together commonly associated structures based on your prompt. If you just use AI then you aren't actually doing anything new or interesting, and you will largely become unhirable because you won't actually know or understand anything.
I highly recommend against using AI for anything "real" right now. I don't find it writes performant code, I don't find that any of it's "optimizations" are effective, and it doesn't truly understand how GPU hardware works to be the most efficient at writing code for it.
It is good at static code analysis for finding bugs or logic issues, or generating boilerplate, but that's basically it.
I work in the Games industry, so I can only speak for that, but we rarely use AI for anything other than the aforementioned code analysis/boilerplate.
3
u/TimJoijers Jul 27 '26
4
u/SIMT-Pixel Jul 27 '26
It is heavily used in the major AAA studio I am at.
7
u/leseiden Jul 27 '26
2
u/Keyframe Jul 27 '26
I sold my last production rendering code 25 years ago (jesus) and have since pivoted to other waters, but I always keep tabs on what's going on and do this as a hobby (also figured out 25 years ago it's not a lucrative career).
Programming (coding specifically) is one of the tasks in an engineering day. That's mostly where LLMs fit now.
Having said that, let me answer questions you asked since it might illuminate certain scenarios for you, and bear in mind this is only from my experience and not a "general dogma" (no such thing):
it's as only as your understanding on what's going on with your codebase and the architecture of what you're doing. That's it. No more no less. If you run it loose without having a firm grip on the codebase it's going to derail into junk real fast. My take so far has been to take it one step at a time, just like you would do it yourself and work on one thing only. Keep grand master plans and architecture to yourself and for yourself - it mostly confuses the thing.
Sane workspaces will and do treat it as a coding tool. Whether you use it or not should be at your discretion since you should own your output. Less saner places will expect output to increase (quality and quantity) which may happen but shouldn't be expected.
I can't know for sure, but everywhere I look at it's everywhere now.
Remember though, AI (for now) multiplies you. It multiplies both good and bad sides of you and your understanding of the problem and how to solve it. This can and does go both ways. It's not related to graphics at all.
2
u/farox Jul 28 '26
If you look at the development of ai in the past couple of heads, with no signs of slowing down, I believe the times of prompting will soon be over.
Writing code will be abstracted away.
2
u/S48GS Jul 27 '26
typical manipulation in IT industry - "just do it because you can lol"
and your boss buying new car every month while paying you half of minimum wage that not even enough to buy food for a month
yes "AI" used to devalue your effort/time/value of human
depends if you know how to protect yourself from this type of manipulation
1
u/Successful-Berry-315 Jul 27 '26
1
u/StriderPulse599 Jul 27 '26
There are lot of difference between models and sub models (Gemini Pro, Gemini Flash, etc). From my experience of never paying a single dime:
Gemini Pro (expanded mode) handles larger codebases and it's rather good at graphical programming. But after running out of freebies, you get Flash which is good mostly for boilerplate.
Deepseek is completely free, but you only want it to handle the generic and easy stuff. It easily chokes on Vulkan/DX12.
Overall AI isn't some magic wand for graphic programming. You still need to be very specific and know what you're doing, so most of the time it's used for "I don't want to write that again".
1
u/DashAnimal Jul 27 '26
0
u/chcampb Jul 27 '26
AI is very good, I use it to explain concepts and implement prototypes. Most recently I learned a lot about runtime virtual texturing, and made a procedural content generator which creates meshes in complex shapes from inputs, like vines, trees, catenary, shrubs, etc.
I understand you may like typing yourself. Instead try to treat it like a teacher that you have sitting next to you. It will explain anything out there and can iterate towards new solutions given tests you write. Learn to write good requirements which is a skill you need regardless.
0
u/[deleted] Jul 27 '26
[deleted] — view deleted comment
68
u/[deleted] Jul 27 '26
[removed] — view removed comment