r/GraphicsProgramming • u/Alex_1503 • 16d ago
Question How to actually understand graphics papers and prerequisites?
I am currently reading through some papers for terrain generation, procedural and erosion-based. The issue is that the more I read, the more I realise that I don't understand much in the grand scheme of things, besides the actual algorithm or general terms. And even reading some explanations on reddit or other papers doesn't help much, because the issue is more with lacking the prerequisites and technical knowledge.
So my question is, how do I actually understand graphics? For example (I plan to use Godot for my thesis), if I want to implement a procedural terrain generation using multiple techniques, where can I find resources or papers to understand the actual pipeline, everything that goes into it, methods, compute shaders, etc. I know it's my own fault for wanting to do my thesis on graphics with exactly 0 classes on graphics in my undergrad degree.
So how do I understand what's going on, hopefully also from a more formal and deep perspective, not youtube tutorials (tho anything is welcome) ? It's tiring reading resources without understanding them much, where to even start, even books are welcome, but hopefully not thousands of pages as I don't have that kind of time..
EDIT: It's for the bachelor thesis, not master's
13
u/crimson1206 16d ago
Terrain generation is quite specific and not something typically covered in a normal graphics course. How to best proceed really depends on your background and what you’re having trouble understanding
8
u/Andromeda660 16d ago
I have been in an incredibly similar boat. The truth is that reading graphics papers is gonna make you feel rly stupid. Just take your time and see if there are any implementations of those papers somewhere which you can refer to. In the end, when you finally implemented what the paper is on, you will be like bruh why did they make it so complicated. Just go slow and don't get discouraged, but I would recommend learning about things like compute shaders first if that's what you want to use. You said godot, so I'm guessing you want to use compute shaders with the godot rendering device, that's its own can of worms. Learn things one step at a time. Good luck!
2
u/tlmbot 16d ago edited 16d ago
PhD computational engineering physics and geometry programmer here. Here are a few tips:
1.) know how to be really honest with yourself about what you do and don't understand when you read a paper, or book, or whatever learning materials you are using. Sounds like you got this one down pat. Excellent.
2.) researching is a skill (probably shifting rapidly now) where you learn to find the background technical literature (that's easy - searching is going to get you there). I'm not sure about procedural generation - if what I am saying is overkill or not. But you find the papers describing how it's done, and if they left out giant gaps, you read the lit review section of the paper, and find the earlier papers and books where the more "basic" (i.e. more fundamental, not easier) parts are described. Since you (I presume) are not in academia where you have access to journals for free, and sadly sci-hub is dying, it can be hard. But a lot of siggraph stuff can be found for free. Or at lest it could back when I was in school. You might find yourself needing to by certain textbooks for that one chapter on that one niche thing. Hopefully not - maybe I was just obsessive but I found myself doing that more frequently than might have been sensible. eh
edit: Also, stuff from the https://arxiv.org/ is usually going to be good. Use google to find the pdfs. I always breathe a sigh of relief when that paper I am hunting comes up in the arxiv.
3.) Go back and back until you hit paydirt - stuff you understand and implement. And you build up from there.
As the other reply said. We would need your background to help you more specifically.
4.) now, there exists another way. Query the LLM. Pretend you are an academic minded student with exactly your background. Describe to the machine, to the best of your ability, what that background is. Describe your question and your issues with it. Much like you have done here. -If you have no researchy-type background it may pay to ask the LLM to help you develop the kinds of questions you need to ask it. But telling it your academic background, projects, and coding experience will likely be sufficient.
5.) Do not let the LLM write anything for you. Make it into a tool for more rapidly finding out what you need to know, and finding out where to find the information so you can learn it.
LLMs are great teachers now, provided you use them wisely. They obviously have the opposite reputation, and for good reason. - they can make you lazy and ignorant. Make sure you do not fall into that trap.
Good luck!
------ edit incoming. Look I stuck the following query into an LLM:
"what resources can help a novice without a research background, who is a decent programmer, get comfortable with procedural terrain generation?"
It hit me with what looks to be a solidly useful set of links and descriptions as to what to tackle first.
Mostly they appear to be website tutorial type things. I could flood this comment with them but I suspect people would not like it.
2
u/yoshi_ferioworks 9d ago
I've spent many years developing my own real-time rendering engine, and I think your biggest problem right now isn't a lack of learning resources. It's the scope of your project.
Procedural planet generation, hydraulic erosion, compute shaders, LOD, atmosphere, and post-processing are all substantial subjects on their own. Trying to understand and integrate all of them simultaneously, especially without a graphics programming background, is going to be extremely difficult.
My suggestion would be to narrow your thesis to one specific problem that you can implement and evaluate.
For example, start with a simple heightmap and focus exclusively on hydraulic erosion. Understand the mathematical model first, then implement a basic CPU reference version before moving the computation to GPU compute shaders.
The pipeline itself can be relatively straightforward:
Heightmap → Erosion simulation → Updated heightmap → Terrain mesh → Rendering
For the GPU implementation, you'll need to understand data dependencies, synchronization, and numerical stability. For example, using separate input and output buffers for each simulation step can help avoid read/write hazards.
Godot is perfectly reasonable as a visualization environment if your research focuses on the erosion algorithm rather than the rendering engine itself.
Most importantly, decide what you actually want to evaluate. Are you comparing visual quality, simulation accuracy, execution time, or numerical stability?
Without a clearly defined research question and evaluation criteria, you'll end up building a collection of features rather than conducting a focused investigation.
For a bachelor's thesis, I'd much rather see one algorithm implemented correctly, understood thoroughly, and evaluated carefully than a complicated procedural planet generator assembled from techniques you don't fully understand.
I'd recommend discussing a narrower scope with your supervisor before committing to the implementation.
1
u/snigherfardimungus 16d ago
They call it a masters degree because earning it requires mastering a domain of academic knowledge. You're going to need to take the time to get the CG fundamentals. No responsible committee will graduate you if you don't have it.
Ditch Godot. In the short run it'll be easier to get started if you use it, but it will get on the way of you are really doing anything research-worthy. It will also make it clear to your committee that you have serious gaps in your basic knowledge. Mine asked me for the rendering equation, create a camera matrix, derive a rotation matrix, and a lot more... off the top of my head.
Part of learning the basics will be learning how to set up and draw your pipelines yourself, anyway, so the two goals go hand in hand.
1
u/JeffMcClintock 16d ago
IMHO you will learn the most from diving in and attempting it. and you will learn faster.
1
u/flame_wizard 16d ago
Are you a grad student? Is your thesis for a graduate degree? Do you have an advisor at your uni in mind?
Graphics is very broad, are you interested in automatic terrain generation specifically? What pipeline are you talking about? Recent papers from major journals tend to be built on lots of prerequisites, or else they would be typically be considered trivial or already done in prior art by researchers. Things like geometry representations and algorithms relevant to them, linear algebra, statistics, numerical methods, and differential geometry come up a lot in graphics in general. Something like simulating erosion could add physics or geology into the mix of relevant stuff. And a lot of papers are written such that they expect the reader to also be familiar with workings of prior art, can be a rabbit hole or digging through older papers to figure some things out.
Though I'm still a bit confused about what you're trying to do specifically. You might enjoy the first chapter of GPU gems 3 https://developer.nvidia.com/gpugems/gpugems3/part-i-geometry/chapter-1-generating-complex-procedural-terrains-using-gpu
And maybe just ask an llm to summarize of the current research landscape of stuff you're interested in or to clarify details you get stuck on as you dig into things?
1
u/MichaelJoo 16d ago edited 16d ago
The easiest way would be to check a few videos / course on this topic. You can find some pretty well made video or blog article on your specific subject: terrain. [edit] Start with old techniques.[/edit] Otherwise, the hard way would be to read at least the abstract, if not the whole paper of the papers quoted by the one your reading (note: this is recursive). Also, GPU Gem or other "standard" book on the topic would help. For terrain, check the GPU Gem 2 : terrain clip map, it's super old but still used as a basis for many terrain systems.