入门DirectX 11游戏编程指南

4星 · 超过85%的资源需积分: 13 187 浏览量更新于2024-07-26 收藏 3.12MB PDF 举报

" Beginning DirectX 11 Game Programming 是一本由 Allen Sherrod 和 Wendy Jones 合著的书籍，由 Course Technology PTR 出版，属于 Cengage Learning 集团的一部分。本书面向初学者，旨在教授如何使用 DirectX 11（DX11）进行游戏编程。" 在 DirectX 11 (DX11) 游戏编程中，有几个核心概念和技术是至关重要的： 1. **DirectX 11 概述**：DirectX 是一组应用程序接口（API），用于在微软的 Windows 操作系统上创建多媒体和游戏应用，尤其是图形渲染。DirectX 11 是 DirectX 的一个版本，带来了许多新特性和性能提升，比如更高效的多线程支持、更强大的硬件加速功能和新的图形管线。 2. **图形管线**：DirectX 11 引入了可扩展的图形单元，如顶点着色器、几何着色器、像素着色器和 hull/domain 着色器。这些着色器用于处理图形数据，实现复杂的图形效果。管线模型允许开发者在不同的阶段定制渲染过程。 3. **Direct3D**：DirectX 的一部分，专注于3D图形。在 DX11 中，Direct3D 提供了对现代GPU的强大控制，包括纹理、渲染目标、深度/模板缓冲和视口管理等。 4. **Shader Model 5.0**：DX11 支持 Shader Model 5.0，提供了更高级的编程语言（HLSL，High-Level Shader Language），让开发者可以编写更高效、更灵活的着色器代码，实现更多样化的视觉效果。 5. **多线程优化**：DX11 强调多线程编程，以利用现代多核处理器的潜力，提高游戏性能。开发者可以将计算任务分布到多个线程，减少渲染瓶颈。 6. **纹理和资源管理**：DX11 提供了更高效的纹理和资源管理，包括常量缓冲区、纹理数组和纹理立方体，以及对纹理压缩和资源状态转换的支持。 7. **计算着色器**：计算着色器是 DX11 的一个新特性，允许开发者使用 GPU 进行通用计算，不仅限于图形处理，为物理模拟、AI 和其他计算密集型任务提供加速。 8. **Mipmap 和视口控制**：Mipmap 用于优化纹理采样，提供不同级别的细节，而视口控制则允许调整渲染窗口的大小和位置。 9. **深度和模板测试**：这些技术用于实现3D场景中的遮挡和透明度效果，确保正确地渲染物体的前后关系。 10. **DirectX Math**：这是 DX11 提供的一个数学库，包含向量、矩阵运算，简化了3D图形编程中的数学操作。学习《 Beginning DirectX 11 Game Programming》这本书，读者将了解这些关键概念，并逐步学会如何使用 DX11 创建自己的游戏应用。书中的实例和练习将帮助读者掌握实际编程技巧，逐步成长为熟练的 DirectX 开发者。

hardware, and a powerful API that was being hyped by one of the most

influential software giants in the world.

The most apparent removal in Direct3D 10 was the fixed-function pipeline,

which is essentially a set of rendering states and algorithms built into the API

that allowed for the rendering of objects using common effects. The fixed-

function pipeline was removed in favor of programmable shaders within

graphics hardware. Graphics shaders, which will be discussed throughout this

book, are code written specifically to customize how the graphics hardware

processes geometry. Graphics shaders were first introduced in DirectX 8, but

since then graphics hardware and the Shader Models that they run have evolved

to a point where they have become the star of the API.

In Direct3D 9 we can render geometry, enable lighting by setting a few

properties and rendering states, have the API transform our geometry, and so

forth by calling a few Direct3D function calls. In Direct3D 10 we can do all of

that ourselves and much more in shaders. The key thing for beginners to keep in

mind if this is their first time learning graphics programming is that the fixed-

function pipeline was limited to whatever was built into the API, whereas

shaders allow us to create any effect, limited only by the frame-rate we deem

desirable in our games . Want lighting? Call a Direct3D function to enable it and

set its properties (up to eight lights). Want to render surfaces with more than

one image? Just enable it. If, however, you wish to perform pixel-based motion

blur and depth-of-field, you are out of luck using the fixed-function pipeline.

Often if the fixed-function pipeline does not explicitly support it and you are not

using shaders, you cannot create the effect you want. Although some coders

have found tricks and workarounds to getting some effects created without

shaders, it was often a very difficult and inefficient workaround. I remember

these times well and do not miss them.

Today, if we want to perform bump mapping, we can write a pixel shader that

takes the light direction, performs a calculation using it and the pixel-level

surface direction loaded from a special image known as a normal map, and

combine that with the shading of the final pixel’s color. In the days before

shaders, or even when shaders were limited in the features they provided (such

as the dark ages of register combiners for early versions of OpenGL), this was

impossible, and doing even simple effects like normal mapping back then was

What Is DirectX? 3

DirectX 11 versus OpenGL 4.0

OpenGL has long been considered a rival graphics API to Direct3D. OpenGL

supports platforms outside of Windows-based operating systems, such as Mac

computers, Linux OSs, Apple’s iPhone and iPad, Sony’s Playstation 3 (an

implementation at least), and a variety of mobile devices such as cell phones

and PDAs, along with other platforms. Although the native device creation of

OpenGL can differ from one platform to another, the rest of the API is

considered platform independent, not including the long history of hardware-

specific extensions and feature s from competing entities within the OpenGL

camp. DirectX, on the other hand, is available on the various Windows OSs and

the Xbox game consoles. To be considered DirectX 10 or 11 compatible,

hardware must adhere to a strict compatibility list, whereas prior to DirectX

10 this was not always the case. In the case of OpenGL this often led to vendor-

specific extensions that worked on limited hardware. Incompatibilities within

the hardware market caused rework when trying to achieve the same result on

all supported devices.

The whole Direct3D versus OpenGL debate can often seem like a religious one,

but the fact is that for many years OpenGL has lagged behind Direct3D.

Microsoft has done a great job evolving Direct3D and improving it throughout

the years, but OpenGL has only lagged behind, not keeping its promises as each

new version is released, and time and time again has suffered from the same

problems of yesteryear. When OpenGL 3.0 was first announced, it was thought

that OpenGL would finally move back into a position to rival Direct3D.

Unfortunately, the world of OpenGL has gone through its share of ups and

downs, both within the group behind it and with how the API stacked against

Direct3D, and Direct3D has continued to dominate.

OpenGL 4.0 catches up to many of the publicized features of DirectX 11, most

notably through the support of general-purpose computing using OpenCL and

tessellation, and is positioning itself to be a step closer to the promises that were

never delivered in the past, most notably with OpenGL 2.0 and OpenGL 3.0.

Although OpenGL is not out of the race yet, it unfortunately needs a lot of work

to not only truly rival DirectX but also to win back the hearts and minds of

many of us who turned to Direct3D once OpenGL’s faults became too

numerous. Even if the API catches up, the graphics API race is a lot like high

school where the popular kid wins the election.

What Is DirectX? 5

Why Is DirectX Needed?

Before the release of the Windows operating system, developers were writing

games for DOS. This single-threaded, non-GUI operating system provided

developers with a direct path between their application code and the hardware

it was running on. This had both its advantages and problems. For instance,

because there was a direct path between the game code and the hardware,

developers could pull every ounce of power out of the machine, giving them

complete control over how their game performed. The downside included the

need to either write directly to the hardware or use a variety of third-party

libraries for any hardware they wanted their game title to support, including

even common hardware such as video and sound cards.

Video cards were especially confusing because not all video cards followed the

same standard. Even though most video cards supported a series of common

resolutions, developers were forced to access video memory directly. This made

even drawing to the screen difficult. Developers were definitely looking for a

better and easier way.

When Windows 3.1 was released, it carried with it the same limitations that

DOS had. Since Windows ran on top of DOS, it severely limited the resources

available to games and took away the direct access developers had enjoyed for so

long. Most games written to support Windows at the time consisted mainly of

card and board games, while most games continued to support DOS only.

Microsoft released DX1 as a way of enticing developers to make games for

Windows to prove that the OS wasn’t slow and move people away from DOS-

based systems.

Microsoft’s release of Windows 95 didn’t eliminate any of these problems until

the release of DirectX 1, also known as the Windows Games SDK. It gave

developers a single library to write to, placing a common layer between their

game and the PC hardware; drawing graphics to the screen had just become a

whole lot easier. The first version of DirectX still didn ’t provide support for all

the hardware out there, but it was a great starting point in giving game

developers what they had been waiting for. Over the years, there have been

multiple releases of DirectX, each one improving and adding support for new

technologies such as network play, streaming audio, and new kinds of input

6 Chapter 1

The What, Why, and How of DirectX

剩余384页未读，继续阅读

MoonInCloud

粉丝: 3
资源: 46

入门DirectX 11游戏编程指南

[DirectX.11游戏编程入门].Beginning.DirectX.11.Game.Programming

[DirectX.11游戏编程入门].Beginning.DirectX.11.Game.Programming.(Source.Code)

[DirectX.11游戏编程入门].Beginning.DirectX.11.Game.Programming.(美)Wendy.Jones.文字版

for {set ii 1} {$ii<=25} {incr ii} { puts "The $ii th Time history analysis is Beginning..............." if {[file exists outputBWPZ[expr $ii]]==0} { file mkdir outputBWPZ[expr $ii];请帮我解释并优化这段代码

移动应用和游戏的开发的参考文献

beginning ios 14 programming with swift

wxWidgets 书籍

最新资源