<< 1 >>
Rating: 
Summary: Not for C# programmers...
Review: Absolutely No C# or managed code. The examples are in C++ and do not compile with Visual Studio .NET 2003 due to Upper/Lower Case differences in the Header files.Due to the appalliing lack of information available on DirectX V9 managed I figured that this would provide some insight but it really deals with Assembly language HLSL and even at that all oriented for C++ with no C# examples. If you are buying this to learn HLSL specifically then this could be the book for you. If you bought it like I did hoping that it would help you with DirectX 9.0 forget it...
Rating: 
Summary: References should be free
Review: After receiving this book i can only say it is disappointing. First, half of it is useless as it covers the programming of the shaders in assembler, while in the following chapters it introduces the High Level Shading Language which replaces it completely.
Second, it doesn't really have much information, just a language reference and a collection of very basic examples (i mean REALLY basic).
In overall, it is not more than "The CG Tutorial Book" from NVIDIA but reading Microsoft instead, and reading HLSL instead of CG. The difference is that "The CG Tutorial Book" is free to download in PDF. It seems Microsoft doesn with books the same than with software.
Rating: 
Summary: Shaders and shader programming
Review: As of this writing, there doesn't seem to be a real reference manual for HLSL and the shader assembly language. This book makes a good effort at filling that role, however.
The graphics programmer is likely to find this very useful. It integrates C application code with shader examples. It also discusses on-the fly compilation, use of resources for shader source code, the relationships between vertex and pixel shaders, texture samplers, and 'techniques' for pulling all the pieces together. Performance programming gets some discussion, but isn't a central topic. Appendices specify the shader language in dryly formal terms, but the descriptive chapters make most language features very clear.
The shader programming model is decidedly non-standard. A rendering program does not work at all like a C program. Yes, a C/C++ programmer will be able to follow a shader's internals easily enough. The problem, though, is that a C program is in charge of what data gets handled when. Everything in a rendering program is silently a callback, however. It's invoked by some execution engine that sequences the input and output data, and even synchronizes multiple (and almost invisible) threads of execution. The hardware rendering program also interacts strongly with the application running in the main processor, partly through "semantics", reflective "annotations", and various parameter-setting mechanisms. There is a huge amount of mechanism at work, and it gives the real meaning to the interacting programs on the host and graphics engine. That mechanism is described in a black-box way, what it does rather than how it works. I think I've reverse engineered the workings, enough for my purposes, but this book did not address my needs directly.
Still, it's the best I've found. Real graphics programs, like games and scientific visualization, are much more than lines and circles. This book, with its examples, will surely help the beginner acquire a working knowledge.
//wiredweird
Rating:
Summary: Shaders and shader programming
Review: As of this writing, there doesn't seem to be a real reference manual for HLSL and the shader assembly language. This book makes a good effort at filling that role, however. The graphics programmer is likely to find this very useful. It integrates C application code with shader examples. It also discusses on-the fly compilation, use of resources for shader source code, the relationships between vertex and pixel shaders, texture samplers, and 'techniques' for pulling all the pieces together. Performance programming gets some discussion, but isn't a central topic. Appendices specify the shader language in dryly formal terms, but the descriptive chapters make most language features very clear. The shader programming model is decidedly non-standard. A rendering program does not work at all like a C program. Yes, a C/C++ programmer will be able to follow a shader's internals easily enough. The problem, though, is that a C program is in charge of what data gets handled when. Everything in a rendering program is silently a callback, however. It's invoked by some execution engine that sequences the input and output data, and even synchronizes multiple (and almost invisible) threads of execution. The hardware rendering program also interacts strongly with the application running in the main processor, partly through "semantics", reflective "annotations", and various parameter-setting mechanisms. There is a huge amount of mechanism at work, and it gives the real meaning to the interacting programs on the host and graphics engine. That mechanism is described in a black-box way, what it does rather than how it works. I think I've reverse engineered the workings, enough for my purposes, but this book did not address my needs directly. Still, it's the best I've found. Real graphics programs, like games and scientific visualization, are much more than lines and circles. This book, with its examples, will surely help the beginner acquire a working knowledge.
Rating:
Summary: Read DirectX9 SDK documents first.
Review: I suggest to read DirectX9 SDK document fist that comes with DirectX9 SDK. Think about this book later. This book ends explanation as stream of comments of the simple sample shaders that come with SDK. I'd say this book is "out of focus". There are bunch of important things that should be explained - are not in this book. Such explanations are in SDK document.
However, if you want to be away from computer and learn about shaders in relaxed in your bed or at a cafe, or if you are an naturalist who do not want to waste printer inks and papers to print out SDK document, in terms of such points, this book may worth to you.
Rating: 
Summary: Does what the title says
Review: If you want what any professional game programmer would expect from this book, buy it - it does exactly that. It isn't a CG specific book and isn't aimed at C# programmers, but you wouldn't expect it to be. It's reasonable documentation and tutorial material for writing shaders.
Rating: 
Summary: No Microsoft .NET
Review: My book has "Microsoft .NET" on the cover, down left corner. It's the reason I bought the book. It has NOTHING to do with .NET. I don't understand why Microsoft puts it there? It's like BMW putting "V8" on the back of their 4-cylinder 300-series just because they have V8:s.
Rating:
Summary: No Microsoft .NET
Review: My book has "Microsoft .NET" on the cover, down left corner. It's the reason I bought the book. It has NOTHING to do with .NET. I don't understand why Microsoft puts it there? It's like BMW putting "V8" on the back of their 4-cylinder 300-series just because they have V8:s.
Rating:
Summary: misunderstood book
Review: This is not a book for learning DirectX. Please read the title and book description before purchasing to understand what you're getting. This is a book specifically about the DX9 PROGRAMMABLE GRAPHICS PIPELINE. If you're interested in programming pixel shaders and vertex shaders and using MS's HLSL, then consider this book. It's not a C# book (nor should it be), it's a reference material for the programmable pipeline. As far as free stuff goes, well, the DirectX SDK is free, so give me a break. Everyone just has to have everything free... people should write books for you for free too? Maybe you'd like to paint my house for free? Don't tell me you're like MS too?
<< 1 >>
| 
