使用DirectX 10进行高级3D游戏编程

需积分: 10 192 浏览量更新于2024-07-29 收藏 5.02MB PDF 举报

"Advanced 3D Game Programming with DirectX 10" 本书《Advanced 3D Game Programming with DirectX 10》是由Peter Walsh编写的，详细介绍了如何使用DirectX 10进行高级3D游戏编程。DirectX是微软公司开发的一个应用程序接口（API），主要用于Windows平台上的多媒体应用开发，尤其是游戏和图形密集型应用。该书涵盖了DirectX 10的核心技术，包括图形渲染、声音处理、输入设备管理等多个方面，旨在帮助开发者深入理解并利用DirectX 10创建高质量的3D游戏。书中可能包含以下几个关键知识点： 1. **DirectX 10基础**：讲解了DirectX 10的新特性，如统一的Shader Model 4.0，更高效的硬件资源管理和新的渲染管线。这包括对顶点和像素着色器的理解，以及如何利用它们实现复杂的光照、纹理和渲染效果。 2. **图形编程**：详细阐述了Direct3D 10的图形API，包括如何创建和管理设备上下文，构建几何模型，使用索引缓冲区和顶点缓冲区，以及应用视口和投影变换。此外，还可能涵盖多纹理贴图、深度缓冲、反走样等技术。 3. **着色器编程**：深入讨论了HLSL（High-Level Shader Language）语言，包括顶点着色器、像素着色器、几何着色器和计算着色器的编写，以及如何利用这些着色器实现高级视觉效果。 4. **资源管理**：介绍了Direct3D 10中的纹理、常量缓冲区、纹理数组和纹理立方体等资源的创建、加载和管理，以及内存优化策略。 5. **状态机和渲染状态**：解释了Direct3D 10中的状态机概念，如何设置和管理渲染状态，如混合模式、深度测试、裁剪和Alpha测试。 6. **输入设备处理**：涵盖了如何通过DirectInput或XInput API来处理键盘、鼠标和游戏控制器等输入设备，实现玩家交互。 7. **声音和多媒体**：可能涉及使用DirectSound或XAudio2进行音频处理，以及如何播放和管理音效。 8. **性能优化**：讨论了多线程编程在游戏开发中的应用，以及如何利用GPU并行处理能力优化渲染性能。 9. **错误处理和调试**：提供了关于如何诊断和解决DirectX 10程序中的错误和问题的技巧。 10. **实例分析**：通过实际的游戏开发案例，展示如何将上述技术综合应用到一个完整的3D游戏项目中。这本书对于希望掌握DirectX 10进行3D游戏开发的程序员来说是一本宝贵的资源，它不仅涵盖了技术细节，还强调了实践应用和问题解决。尽管DirectX 10现在已经被DirectX 11和更现代的版本所取代，但其中的基本原理和技术依然对理解和学习现代3D图形编程有着重要的参考价值。

Introduction

A wise man somewhere, somehow, at some point in history, may have said

the best way to start a book is with an anecdote. I would never question

the words of a wise man who may or may not have existed, so here we go.

When I was a freshman in high school, I took the required biology

class that most kids my age end up having to take. It involved experiments,

lab reports, dissecting of various animals, and the like. One of my lab part-

ners was a fellow named Chris V. We were both interested in computers

and quickly became friends, to the point where talking about biology in

class was second to techno-babble.

Onenight,inthemiddleofDecember,Chriscalledmeup.Thelab

report that was due the next day required results from the experiment we

had done together in class, and he had lost his copy of our experiment

results. He wanted to know if I could copy mine and bring them over to his

place so he could finish writing up the lab. Of course, this was in those hei-

nous pre-car days, so driving to his house required talking my parents into

it, finding his address, and various other hardships. While I was willing to

do him the favor, I wasn’t willing to do it for free. So I asked him what he

could do to reciprocate my kind gesture.

“Well,” he said, “I guess I can give you a copy of this game I just got.”

“Really? What’s it called?” I said.

“Doom.BytheWolf3Dguys.”

“It’s called Doom? What kind of name is that??”

After getting the results to his house and the game to mine, I fired up

the program on my creaky old 386 DX-20 clone, burning rubber with a

whopping 4 MB of RAM. As my space marine took his first tenuous steps

down the corridors infested with hellspawn, my life changed. I had done

some programming before in school (Logo and Basic), but after I finished

playing the first time, I had a clear picture in my head of what I wanted to

do with my life: I wanted to write games, something like Doom. I popped

onto a few local bulletin boards and asked two questions: What language

was the game written in, and what compiler was used?

Within a day or so, I purchased Watcom C 10.0 and got my first book

on C programming. My first C program was “Hello, World.” My second was

a slow, crash-happy, non-robust, wireframe spinning cube.

I tip my hat to John Carmack, John Romero, and the rest of the team

behind Doom; my love for creating games was fully realized via their

masterpiece. It’s because of them that I learned everything that I have

about this exceptionally interesting and dynamic area of computer

acquired programming. The knowledge that I have is what I hope to fill

these pages with, so other people can get into graphics and game

programming.

I’ve found that the best way to get a lot of useful information down in

a short amount of space is to use the tried-and-true FAQ (frequently asked

questions) format. I figured people needed answers to some questions

about this book as they stood in their local bookstore trying to decide

whether or not to buy it, so read on.

Who are you? What are you doing here?Who are you? What are you doing here?

I am a professional game programmer and have been for quite a few years.

I started out like most people these days, getting extremely interested in

how games worked after Doom came out. After teaching myself program-

ming, I moved on to study for a degree in computer game development at

Abertay University in Dundee, Scotland. After that I went on to work for a

short while with IC-CAVE, which is a think tank for the next generation of

gaming technology. Over the years I’ve worked on games like F1 Career

Challenge, Harry P otter and the Chamber of Secrets, SHOX,andMedal of

Honor: Rising Sun. Most recently I’ve worked on Crackdown for the Xbox

360. I’ve developed games for just about every platform you can think of.

I’ve also read so many programming books that I reckon I have person-

ally wiped out half of the Amazon rainforest. So hopefully all that material

will help me write this book in a way that avoids all the pitfalls that other

authors have fallen into. I really hope you learn a lot from this book. If you

have any questions along the way that you just can’t get to the bottom of,

please email me at peter_stpwalsh@yahoo.co.uk. Unfortunately, after

printing that email address in a previous book it was bombarded by junk

mail from spammers and became almost unusable. However, Hotmail has

gotten better lately, so hopefully your questions will get through to me!

Why was this book written?Why was this book written?

I’ve learned from many amazingly brilliant people, covered a lot of difficult

ground, and asked a lot of dumb questions. One thing that I’ve found is

that the game development industry is all about sharing. If everyone

shares, everyone knows more stuff, and the net knowledge of the industry

increases. This is a good thing because then we all get to play better

games. No one person could discover all the principles behind computer

graphics and game programming themselves, and no one can learn in a

Introduction

xvi

vacuum. People took the time to share what they learned with me, and

now I’m taking the time to share what I’ve learned with you.

Note: For the update to DirectX 10 all of the source has also been updated to

be Unicode compliant and use secure STL.

Who should read this book?Who should read this book?

This book was intended specifically for people who know how to program

already but have taken only rudimentary stabs at graphics/game program-

ming or never taken any stab at all, such as programmers in another field

or college students looking to embark on some side projects.

Who should not read this book?Who should not read this book?

This book was not designed for beginners. I’m not trying to sound arrogant

or anything; I’m sure a beginner will be able to trudge through this book if

he or she feels up to it. However, since I’m so constrained for space, often-

times I need to breeze past certain concepts (such as inheritance in C++).

If you’ve never programmed before, you’ll have an exceedingly difficult

time with this book.

What are the requirements for using the code?What are the requirements for using the code?

The code was written in C++, using Microsoft Visual C++ 2005 Express

Edition, which is available for download for free from Microsoft. The

projects and solutions are provided on the downloadable files site

(www.wordware.com/files/dx10). This book obviously focuses on DirectX

10, which at the time of writing will only run on Windows Vista or higher,

with a DirectX 10 class graphics card. If you don’t have these, you’ll need

to upgrade.

Why use Windows? Why not use Linux?Why use Windows? Why not use Linux?

I chose to use Win32 as the API environment because 90% of computer

users currently work on Windows. Win32 is not an easy API to understand,

especially after using DOS coding conventions. It isn’t terribly elegant

either, but I suppose it could be worse. I could choose other platforms to

work on, but doing so reduces my target audience by a factor of nine or

more.

Introduction

xvii

Why use Direct3D 10?Why use Direct3D 10?

For those of you who have never used it, OpenGL is another graphics API.

Silicon Graphics designed it in the early ’90s for use on their high-end

graphics workstations. It has been ported to countless platforms and oper-

ating systems. Outside of the games industry, in areas like simulation and

academic research, OpenGL is the de facto standard for doing computer

graphics. It is a simple, elegant, and fast API. Check out www.opengl.org

for more information.

Butitisn’tperfect.Firstofall,OpenGLhasalargeamountoffunction-

ality in it. Making the interface so simple requires that the implementation

take care of a lot of ugly details to make sure everything works correctly.

Because of the way drivers are implemented, each company that makes a

3D card has to support the entire OpenGL feature set in order to have a

fully compliant OpenGL driver. These drivers are extremely difficult to

implement correctly, and the performance on equal hardware can vary

wildly based on driver quality. DirectX has the added advantage of being

able to move quickly to accommodate new hardware features. DirectX is

controlled by Microsoft (which can be a good or bad thing, depending on

your view of it), while OpenGL extensions need to be deliberated by com-

mittees. And finally, you simply can’t get the latest shader support in

OpenGL that DirectX provides.

Why use C++? Why not C, .NET, or Java?Why use C++? Why not C, .NET, or Java?

I had a few other language choices that I was kicking around when plan-

ning this book. Although there are acolytes out there for Delphi, VB, and

even C#, the only languages I seriously considered were C++, Java, and

C. Java is designed by Sun Microsystems and is an inherently object-ori-

ented language, with some high-level language features like garbage

collection. C is about as low level as programming gets without dipping

into assembly. It has very few if any high-level constructs and doesn’t

abstract anything away from the programmer.

C++ is an interesting language because it essentially sits directly

between the functionality of the other two languages. C++ supports COM

better than C does (this is more thoroughly discussed in Chapter 1). Also,

class systems and operator overloading generally make code easier to read

(although, of course, any good thing can and will be abused). Java,

although very cool, is an interpreted language. Every year this seems to be

less important: JIT compilation gets faster and more grunt work is handed

off to the APIs. However, I felt C++ would be a better fit for the book.

Java is still a very young language and is still going through a lot of

change.

Introduction

xviii

Do I need a 3D accelerator?Do I need a 3D accelerator?

Yes. And it must be DirectX 10 class running with Windows Vista.

How hardcore is the C++ in this book?How hardcore is the C++ in this book?

Some people see C++ as a divine blade to smite the wicked. They take

control of template classes the likes of which you have never seen. They

overload the iostream operators for all of their classes. They see multiple

inheritance as a hellspawn of Satan himself. I see C++ as a tool. The more

esoteric features of the language (such as the iostream library) I don’t use

at all. Less esoteric features (like multiple inheritance) I use when it makes

sense. Having a coding style you stick to is invaluable. The code for this

book was written over an eleven-month period, plus another three for the

revision, but I can pick up the code I wrote at the beginning and still read

it because I commented it and used some good conventions. If I can under-

stand it, hopefully you can too.

What are the coding conventions used in the source?What are the coding conventions used in the source?

One of the greatest books I’ve ever read on programming was Code Com-

plete (Microsoft Press). It’s a handbook on how to program well (not just

how to program). Nuances like the length of variable names, design of

subroutines, and length of files are covered in detail in this book; I strongly

encourage anyone who wants to become a great programmer to pick it up.

You may notice that some of the conventions I use in this book are similar

to the conventions described in Code Complete; some of them are borrowed

from the great game programmers like John Carmack, and some of them

are borrowed from source in DirectX and Win32.

I’ve tried really hard to make the code in this book accessible to every-

one. I comment anything I think is unclear, I strive for good choices in

variable names, and I try to make my code look clean while still trying to

be fast. Of course, I can’t please everyone. Assuredly, there are some C++

coding standards I’m probably not following correctly. There are some

pieces of code that would get much faster with a little obfuscation.

If you’ve never used C++ before or are new to programming, this

book is going to be extremely hard to digest. A good discussion on pro-

gramming essentials and the C++ language is C++ Primer (Lippman et

al.; Addison-Wesley Publishing).

Introduction

xix

剩余551页未读，继续阅读

zhkza99c

粉丝: 20
资源: 6

使用DirectX 10进行高级3D游戏编程

Advanced 3D Game Programming with DirectX 10.0 source code part2

Advanced 3D Game Programming with DirectX 10.0 source code part1

Introduction to 3D Game Programming with DirectX 12 中文版 第四章至第十章

Advanced 3D Game Programming with DirectX 10

Advanced 3D Game Programming with DirectX 8.0

Advanced 3D Game Programming with DirectX 10.0

Advanced 3D Game Programming with DirectX.pdf

Advanced 3D Game Programming With Directx 9.0 With Code.rar

[Advanced 3D Game Programming with DirectX 9]

Advanced 3D Game Programming with DirectX 10.0.pdf

最新资源

Introduction to 3D Game Programming with DirectX 12 中文版第四章至第十章