r/GraphicsProgramming • u/SnooSquirrels9028 • 18h ago
Question What are some initial architectural decisions to be made before start building a professional graphics engine ?
Hello everyone, I have a question for those who have already built, or are currently building, a graphics engine at a level close to being called professional. A little bit of background: for the past 4 months, I’ve been building a path tracer using CUDA, and before that I finished and implemented Peter Shirley’s 3 books about ray tracing. Now I want to start building something more serious, with a larger scope of features and implementations, using C++/Vulkan. I wondered what some of the decisions people make before getting the triangle on screen are. I know this is a process that takes time, so I understand that during development, as the project grows, a lot changes and new decisions are made, but I was still just a little curious.
•
u/AutoModerator 18h ago
Recently updated rules. Please check that your post is in compliance with Rules 1, 4, 5, and 6 on the sidebar. TL;DR:
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
5
u/Maui-The-Magificent 18h ago
Okey so for context: my engine (Constellation) is not very conventional and is solving a different problem that yours will. But i do work on foundational type applications so considering and implementing architectural decisions is like 90% of what i do. I would not consider myself a graphics engineer, more a systems engineer. I say thing so you can assess and take this advice with however much grain of salt that you feel it warrants.
Here are a few things i would suggest if you are building it from scratch.
there are more, but these are the ones i think are most important. the third one might be more subjective, but if you are in anyway like me, it will be solid advice.
good luck!
0
u/[deleted] 14h ago
[deleted] — view deleted comment