9 replies to this topic

[Inuyashakagome16]

I started reading the book "Beginning DirectX 11 Game Programming" (http://www.ultimategameprogramming.com/) recently and I've starting to understand the many function of DX11. However, it just seems like many of the keywords and functions through out DX11 (and DX in general) are very complex. My question is, does it become easier to remember all of these keywords and functions? Because yes I am reading many of the chapters over and over, but It just seems like not all of it is sticking right away. Should I be using a different book/tutorial for learning DX11? I've looked around for a bit for a decent book / tutorial for DX11 but this book seems to be recommended quite a bit. Also with http://www.directxtutorial.com and http://www.rastertek.com/tutindex.html

I guess i'm just worried I'll learn only half of DX11 and find myself lost later on because I didn't use the correct(?) book to learn.

[Radikalizm]

Don't learn an API by trying to cram everything, you don't have to be able to recite every function and every class available, that's just madness.
Also, don't worry about using the 'correct book', or the 'correct tutorial', because these should only be reference materials and not absolute guides to learning and understanding an API.

Learn by doing.
Read up on some tutorials and try to recreate what they achieve by yourself, while keeping an API reference close so you can look up which parts of the API you should use and how they should be used. When you use these parts of the API a couple of times you'll have no problem remembering what they do and how they should be used, maybe you won't know the exact details of which parameters a certain function expects, but that's absolutely no problem as that's what those books and online references are for.

If you're serious about programming you'll encounter tons of APIs in your career, and there's no way you're going to be able to remember or learn every single detail of each API you're ever going to work with, so get comfortable with using the available documentation as reference material.

[Dynamo_Maestro]

Whenever you 'feel' like this, just remember back to the first time you programmed or your first experience with OOP and all the things that were confusion, overtime things made sense and you understood stuff, the same will happen with DirectX, however do note the learning curve with any lower level library is steep but once you have gotten use to it, it can become a lot of fun and you will accept the challenges with more confidence.

That book is ok for beginners I guess, but from personal experience anything with a skull hand at the front is terrible, and I am pretty sure that book doesnt cover major areas that probably should be covered in a beginners book.

Have a look at Introduction to DirectX11 - Frank Luna

Edited by Dynamo_Maestro, 14 December 2012 - 11:26 AM.

[J. Evola's Apprentice]

If you can't remember method names, use IDE with autocompletion.

[Inuyashakagome16]

Don't learn an API by trying to cram everything, you don't have to be able to recite every function and every class available, that's just madness. Also, don't worry about using the 'correct book', or the 'correct tutorial', because these should only be reference materials and not absolute guides to learning and understanding an API. Learn by doing. Read up on some tutorials and try to recreate what they achieve by yourself, while keeping an API reference close so you can look up which parts of the API you should use and how they should be used. When you use these parts of the API a couple of times you'll have no problem remembering what they do and how they should be used, maybe you won't know the exact details of which parameters a certain function expects, but that's absolutely no problem as that's what those books and online references are for. If you're serious about programming you'll encounter tons of APIs in your career, and there's no way you're going to be able to remember or learn every single detail of each API you're ever going to work with, so get comfortable with using the available documentation as reference material.

I'll probably try and go with that. Because I just don't want to write a bunch of code and not really understand what's going on. Considering DirectX is rather complex.

Whenever you 'feel' like this, just remember back to the first time you programmed or your first experience with OOP and all the things that were confusion, overtime things made sense and you understood stuff, the same will happen with DirectX, however do note the learning curve with any lower level library is steep but once you have gotten use to it, it can become a lot of fun and you will accept the challenges with more confidence. That book is ok for beginners I guess, but from personal experience anything with a skull hand at the front is terrible, and I am pretty sure that book doesnt cover major areas that probably should be covered in a beginners book. Have a look at Introduction to DirectX11 - Frank Luna

I'll check that book out! And yeah that's true that's how it always was for me. It took time but i started to remember a lot about the syntax and meanings of everything.

[MAD UNICORN GAMES]

It isn't always about remembering every keyword or function provided by DirectX. Yes, through constant use you will be able to recognize when you can use a function available by DirectX's API. The purpose of the online reference is to alleviate the need for you to remember everything. My advice is to read through your book so that you are familiar with the API but not to stress memorization. Work the examples too. Programming graphical interfaces and 3D software is supposed to be fun. Do not turn it into a college course unless you are being graded and have paid tuition prices. Additionally, let your creativity guide your study.

[Karsten_]

Not to mention that after you have spent some time with the API, you will probably have abstracted enough of it into classes or helper functions to be able to forget about the nitty gritty implementation details anyway.

[TheChubu]

Remember that there is autocompletion on many IDEs. That can help a lot.

[Inuyashakagome16]

(In response to the above replies)
That is very true. With enough practice i'm sure i'll remember all of it.
Maybe I just worded this wrong.
I got to a point in the book where it was "Lets begin on drawing a triangle." But with all that's being introduced in the chapter, I felt like there was SO much that I wouldn't remember what I needed to just draw a triangle. Mind you, I was able to draw the triangle. (Horray) But if you asked me how the information moved through the project from definition to display I wouldn't be able to tell you. I'll keep moving through the book and learning what I can, I just feel like I won't remember the process. Kind of like.. Looking at examples on how to draw a triangle on paper but not remembering the 2nd step of the process. I understand with time I'll start to remember it. </end rant>

[jdturner11]

Programming pragma applies to API. Learn the fundamentals, not the code, there will always be a reference for that.