Help with D3D App class
Author
Hello, I am starting to dive into DX coming from OpenGL... I have noticed some people are wrapping DX stuff into classes and making their life easier of course, but why not use the DX SDK class that I see sometimes? (name of the class eludes me) Any thoughts or reasons why to or not use it for game engine development. Thanks
I don't use it because I think I'll learn more if I make my own (I'm not a very good programmer). Also, I'm comfortable with my own naming conventions and going through and changing everything would be a pain. Other than that I don't really know. It just came naturally to me to make my own wrapper classes.
The D3D app class i know from the DX8 SDK contains quite a lot code and not everything is as clear commented as i'd wish it was.
I still used it as base for my general render class since it checks quite a lot of caps and makes it possible to run with my wanted settings almost everywhere.
You still might build your own wrapper class but take a close look on the framework Microsoft built. There's a lot of things that may not make sense on the first glance but can be quite crucial for a successful startup.
One of the things i added on top: Auto-switch to fullscreen or back if the target card wouldn't support the wanted mode in a window (yes, crap like that is out there).
I still used it as base for my general render class since it checks quite a lot of caps and makes it possible to run with my wanted settings almost everywhere.
You still might build your own wrapper class but take a close look on the framework Microsoft built. There's a lot of things that may not make sense on the first glance but can be quite crucial for a successful startup.
One of the things i added on top: Auto-switch to fullscreen or back if the target card wouldn't support the wanted mode in a window (yes, crap like that is out there).
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
