The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I've been making up my mind for so long to break into 3D programming. I do not do 3D at my work. But just out of my curiosity, I've been skimming through D3D articles & trying to catch up with the terms and 3D buzz words. When I look at conventional D3D projects it seemed plausible. I could date to try out few little things.
I've been hearing news about MS strategy on core game development for windows platforms. They've killed XNA and made C++/CX the only way to do core 3D. (not to mind sharp/slimDx/Mono).
I knew C++/Cx is not the common man's C++. But I was guessing it'd would be something like the C++/CLI.
Now I downloaded a sample D3D game that's done with C++/CX, my quick reaction is it's not for the faint hearts. The learning curve trajectory looks out of the sky towards the moon. It's a multiple of the feeling I got when I tried to learn Asp.net MVC just by opening a sample project. (Please note I don't do web stuff at work as well, but kept in touch with ASP.net to some extent) Too much for the rusting brain
I'm happy C++ is still alive for conventional Windows applications. .
I'd thump my chest and try once more to go through at darned C++CX lets see
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy.
DirectX has always been a mass of confusion. It embraced COM to an absurd degree (I read an interview where one of the designers of DirectShow admitted that they'd gone overboard. If I remember, he said that he had just finished his post-graduate degree and was enamored with the idea of a pluggable-style architecture and that resulted in what you see. It's been simplified over the years, but it still disproportionately complicated for the problem it is solving. Then again, that could be Microsoft's model, since given a choice been simplicity and complexity, they pick the latter, but so do far too many engineers.)
For which I will be eternally grateful. This means that I can scrap a project folder with no less than 46 projects in it, including the graphics engine and my own UI.
If I'm going to have to start all over again, I will see to it that Mickeysoft will never play that trick on me again. Whatever I am going to use (most likely real C++, OpenGL and some nice open source libraries), its going to be something that is not under Mickeysoft's control.
Sorry, but that did not work well. I could not get a single project to compile. As much as I could read out of what they call documentation, the libraries are made for Windows 8 and recompiling them may work for Windows 7. Very strange, isn't that what we should be independent of as long as we use the same version of the .Net framework?
Apparently not, and that's just another good reason to forget Microsoft and the mess they have created.
If you keep to standard C++ and OpenGL, it is easy porting everything to Linux. Try OpenCL and/or CUDA while you're at it. Just so much fun playing with graphics cards. Just make sure you don't drive it at max all the time: that is a sure way to blow up the graphics cards.
Sounds like a plan. Going by what the bosses charge for an hour of my work, Microsoft owes me a brand new Lamborghini and can goto (!) hell until I find it in front of my door. That's not going to happen, but I can already see what's going to happen in a year or two when they have their next great idea. Why would anybody want to invest time and money in their junk as long as they stay predictably unpredictable?
The book seems to be good, just by looking at the summary. It covers some interesting and useful things. DirectX 10 and 11 were things I was looking forward to if they finally would have used them in XNA. But why do something useful when you can do something crazy?