DirectX10高级编程：游戏开发实战指南

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

"DirectX10 高级编程 - Peter Walsh" DirectX10是微软开发的一个图形应用程序接口（API），专为游戏开发者和图形程序员设计，用于利用现代图形处理单元（GPU）的强大功能，实现高级3D图形渲染。本书《Advanced 3D Game Programming with DirectX 10.0》由Peter Walsh撰写，是一本针对DirectX10的高性能编程指南，旨在帮助游戏开发者充分挖掘DirectX10的潜力。在DirectX10中，引入了若干关键特性，例如： 1. **统一的渲染管道**：与DirectX9相比，DirectX10的渲染管道进行了重新设计，所有顶点和像素着色器都运行在相同的硬件上，提供了更高效的并行处理能力。 2. **硬件支持的Shader Model 4.0**：Shader Model 4.0允许开发者编写更复杂的着色器程序，包括顶点、几何、像素和计算着色器，极大地增强了图形效果和物理模拟的精度。 3. **资源绑定模型**：DirectX10采用更灵活的资源绑定模型，允许开发者在多个阶段同时绑定多个资源，提高了效率并简化了代码管理。 4. **纹理采样器状态对象**：纹理采样器不再作为着色器的一部分，而是成为独立的状态对象，可以被多个着色器共享，降低了内存占用并提高了性能。 5. **多线程渲染**：DirectX10支持在多个线程间分配渲染任务，利用多核CPU的优势，优化了游戏性能。 6. **Geometry Shader**：新增的几何着色器阶段允许对输入的原始几何数据进行动态修改，如细分、合并或剔除，提供了更多的几何处理可能性。 7. **Surface and Texture Management**：改进的表面和纹理管理机制使得资源管理更加高效，减少了内存碎片，提升了整体性能。 8. **Display and Multi-Monitor Support**：DirectX10提供了增强的显示器和多显示器支持，能够更好地处理宽屏和多显示器环境下的游戏显示。 9. **Query Objects**：查询对象允许程序在不阻塞主线程的情况下检查渲染状态，从而实现更精细的控制和优化。 10. **Tessellation**：细分技术是Shader Model 4.0的一大亮点，能够在GPU上进行高效的细节级别（LOD）计算，生成更精细的几何细节，同时保持高性能。通过学习《Advanced 3D Game Programming with DirectX 10.0》，开发者可以掌握这些技术，并应用于游戏开发，创造出更真实、更沉浸式的游戏体验。这本书涵盖了许多实际案例和代码示例，帮助读者逐步理解和应用DirectX10的各种特性，是游戏开发者进阶的宝贵资源。

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页未读，继续阅读

whl7711

粉丝: 0
资源: 11

DirectX10高级编程：游戏开发实战指南

DirectX 10 3D游戏编程入门

DirectX 10 shader编程指南：从DirectX 8/9到高级技术

DirectX 10 游戏编程入门：基于Go语言的高级示例

DirectX 10 游戏编程基础教程

DirectX 10 游戏编程入门指南

DirectX 9游戏编程高级教程

3D游戏编程入门：DirectX 10与Go语言高级编程技巧

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

DirectX 10纹理采样与Go语言高级编程

使用D3DX10显示文本：DirectX 10游戏编程基础

最新资源