Sign in to follow this  
chema

OpenGL Looking for a good and complete book about D3D9

Recommended Posts

Hello, I am looking for a intermediate-advanced book focused at Direct3D that cover all the major topics including shading languages. I have some 3d math background and experience with OpenGL. I am new to this forum but I expect to visit it frequently and contribute to it. Thanks in advance

Share this post


Link to post
Share on other sites
Quote:
Original post by chema
I am looking for a intermediate-advanced book focused at Direct3D that cover all the major topics including shading languages. I have some 3d math background and experience with OpenGL.

Most of the intermediate-advanced books cover only shader programming - very few advanced books cover the FFP these days. The "GPU Gems" and "ShaderX" series come fairly well regarded.

I would imagine it's below your level, but Introduction to 3D Game Programming with DirectX 9 by Frank D. Luna has been mentioned as a good one by a few people.

If you've got the background that you say you have, I would actually recommend AGAINST buying a "general" book on the D3D API :-

1. The API is a bit of a moving target due to the 2 month SDK releases. Books on the general API and it's framework don't last as long as they used to.

2. D3D9 is at the very least changing inside of a year (to the Windows Vista version) and there is also D3D10 just around the corner.

3. The samples, tutorials, documentation and web forums will cover pretty much everything you need to know about the API

4. The more general shader/graphics related books will be a *much* better long term investment [smile]

Quote:
Original post by chema
I am new to this forum but I expect to visit it frequently and contribute to it.

Welcome to the party [grin]

hth
Jack

Share this post


Link to post
Share on other sites
Quote:

I am looking for a intermediate-advanced book focused at Direct3D that cover all the major topics including shading languages. I have some 3d math background and experience with OpenGL.

Just to extend on jollyjeffers's kind reply. I'd say what has helped me the most was to delve into the rendering pipeline and pull it apart. With that knowledge you will learn shaders very quickly and you can more or less judge what you need and when you need it. With that and the DirectX SDK documentation is just invaluable. Just read the SDK docs and ask alot of questions. The kind people on this forum are proffesional and the speed at which they reply is just awesome. Also make sure that you read the Forum FAQ.

Quote:

I am new to this forum but I expect to visit it frequently and contribute to it.

Welcome buddy, It's nice to see some more people joining and get interested and enthusiastic about Game/Graphics development. :) Just remember that having a good time is the most important part of development and the fun you have while talking to the proffesionals and other people on this forum

I hope this helps.
Take care.

Share this post


Link to post
Share on other sites
i read Introduction to 3D Game Programming with DirectX 9, its great, i cant tell u how much its advanced, but u should check table of contents on amazon and see if u know theat stuf allready

Share this post


Link to post
Share on other sites
A lot of D3D8 seems to be easily convertible to D3D9.

I found Realtime Rendering Tricks and Techniques in DirectX to be a very balanced introduction, with minimal conversion to D3D9 problems.

The book teaches you a well-rounded approach to shader assembly. If a high-level shader language is what you're looking for, this book can still be used to perform assembly optimizations on compiled high-level shader code.

Share this post


Link to post
Share on other sites
Hello again,

Thank you for your advices. I will take into account every one of them. Now mr. Amazon is awaiting for me...

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Forum Statistics

    • Total Topics
      627754
    • Total Posts
      2978944
  • Similar Content

    • By DelicateTreeFrog
      Hello! As an exercise for delving into modern OpenGL, I'm creating a simple .obj renderer. I want to support things like varying degrees of specularity, geometry opacity, things like that, on a per-material basis. Different materials can also have different textures. Basic .obj necessities. I've done this in old school OpenGL, but modern OpenGL has its own thing going on, and I'd like to conform as closely to the standards as possible so as to keep the program running correctly, and I'm hoping to avoid picking up bad habits this early on.
      Reading around on the OpenGL Wiki, one tip in particular really stands out to me on this page:
      For something like a renderer for .obj files, this sort of thing seems almost ideal, but according to the wiki, it's a bad idea. Interesting to note!
      So, here's what the plan is so far as far as loading goes:
      Set up a type for materials so that materials can be created and destroyed. They will contain things like diffuse color, diffuse texture, geometry opacity, and so on, for each material in the .mtl file. Since .obj files are conveniently split up by material, I can load different groups of vertices/normals/UVs and triangles into different blocks of data for different models. When it comes to the rendering, I get a bit lost. I can either:
      Between drawing triangle groups, call glUseProgram to use a different shader for that particular geometry (so a unique shader just for the material that is shared by this triangle group). or
      Between drawing triangle groups, call glUniform a few times to adjust different parameters within the "master shader", such as specularity, diffuse color, and geometry opacity. In both cases, I still have to call glBindTexture between drawing triangle groups in order to bind the diffuse texture used by the material, so there doesn't seem to be a way around having the CPU do *something* during the rendering process instead of letting the GPU do everything all at once.
      The second option here seems less cluttered, however. There are less shaders to keep up with while one "master shader" handles it all. I don't have to duplicate any code or compile multiple shaders. Arguably, I could always have the shader program for each material be embedded in the material itself, and be auto-generated upon loading the material from the .mtl file. But this still leads to constantly calling glUseProgram, much more than is probably necessary in order to properly render the .obj. There seem to be a number of differing opinions on if it's okay to use hundreds of shaders or if it's best to just use tens of shaders.
      So, ultimately, what is the "right" way to do this? Does using a "master shader" (or a few variants of one) bog down the system compared to using hundreds of shader programs each dedicated to their own corresponding materials? Keeping in mind that the "master shaders" would have to track these additional uniforms and potentially have numerous branches of ifs, it may be possible that the ifs will lead to additional and unnecessary processing. But would that more expensive than constantly calling glUseProgram to switch shaders, or storing the shaders to begin with?
      With all these angles to consider, it's difficult to come to a conclusion. Both possible methods work, and both seem rather convenient for their own reasons, but which is the most performant? Please help this beginner/dummy understand. Thank you!
    • By JJCDeveloper
      I want to make professional java 3d game with server program and database,packet handling for multiplayer and client-server communicating,maps rendering,models,and stuffs Which aspect of java can I learn and where can I learn java Lwjgl OpenGL rendering Like minecraft and world of tanks
    • By AyeRonTarpas
      A friend of mine and I are making a 2D game engine as a learning experience and to hopefully build upon the experience in the long run.

      -What I'm using:
          C++;. Since im learning this language while in college and its one of the popular language to make games with why not.     Visual Studios; Im using a windows so yea.     SDL or GLFW; was thinking about SDL since i do some research on it where it is catching my interest but i hear SDL is a huge package compared to GLFW, so i may do GLFW to start with as learning since i may get overwhelmed with SDL.  
      -Questions
      Knowing what we want in the engine what should our main focus be in terms of learning. File managements, with headers, functions ect. How can i properly manage files with out confusing myself and my friend when sharing code. Alternative to Visual studios: My friend has a mac and cant properly use Vis studios, is there another alternative to it?  
    • By ferreiradaselva
      Both functions are available since 3.0, and I'm currently using `glMapBuffer()`, which works fine.
      But, I was wondering if anyone has experienced advantage in using `glMapBufferRange()`, which allows to specify the range of the mapped buffer. Could this be only a safety measure or does it improve performance?
      Note: I'm not asking about glBufferSubData()/glBufferData. Those two are irrelevant in this case.
    • By xhcao
      Before using void glBindImageTexture(    GLuint unit, GLuint texture, GLint level, GLboolean layered, GLint layer, GLenum access, GLenum format), does need to make sure that texture is completeness. 
  • Popular Now