Either way, if you (or someone you know) would like to get started with #graphics programming, the #AMD Game Engineering team is excited to share their top tips with you 🌟
Write a software rasterizer. Write a pathtracer. Learn GL and write a forward-shaded renderer. Write a deferred renderer. Go back and do the first one again now that you've learned some things.
There's a tendency to focus on Doing Things Right the first time, and that's not how learning anything works. Writing a bunch of incomplete, imperfect renderers in a wide variety of styles will teach you more than writing one well.
Thank you everybody for your fantastic contributions! We'll be taking a look through and will be in touch with those we'd like to add to the blog, to confirm you're okay with it 😀
"A review of the state of the art in real time #graphics shading languages and #compilers in both graphics and compute. What are some of the differences between HLSL, GLSL, MSL, and WGSL?"
All credits to @daridrea for sharing this. Thank you! 😘
Disclaimer: I've no experience in graphics programming, but I find this field very fascinating and want to "dip my toes" into it. Thank you for sharing
@gpuopen learned quite a bit through the renderhell books on my side: https://simonschreibt.de/gat/renderhell-book1/ but my main tip would be to just talk with peers. Learning from someone is just so much more efficient in an endless rabbithole of technicalities and niche techniques to learn from/with someone.
Add comment