blocks|key|693815|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|-4|4|5|6|B|7|@]|8|@]|9|$]]]|A|$]]

<blockquote>
The 2D pipeline involves ... [coordinate transformation terms]
Can someone give me the detail differentiation among these?
</blockquote>
This is something I very recently learned while trying to understand how software handles 3D graphics behind the scenes. I've never encountered these terms in reference to 2D graphics before, but the ideas still apply. 2D graphics are just 3D graphics without a few fancy tricks.
<h1>Very Generally</h1>
Most of these different coordinate spaces don't technically exist. They come about by considering the objects you wish to draw from some reference point. When you change that reference point, you change the coordinate space. Math gets involved, but I won't do any here.
<h1>The Drawing Device and Device Coordinates</h1>
<blockquote>
... converting normalized coordinate to device coordinate.
Isn't viewing coordinate and device coordinate the same things?
</blockquote>
Short answer, no, but they can be in certain 2D cases. In 3D, pretty much never.
There seems to be a confusion not just between view and device coordinates, but also with the distinction between normalized and device coordinates. Lets start with normalized and device, and we'll get to view later.
In 3D systems (and 2D systems setup to work like them) you are presented with a &quot;drawing device&quot; consisting of two parts: drawing tools (usually functions accessed from application code) and a drawing area. Ignoring the tools, the important thing is that the drawing area has a coordinate system independent of pixels which adds a lot of flexibility and generality to the device.
Any time something is setup to work numerically in a range from 0 to 1 it is &quot;normal&quot;, and often the range 0 to -1 is included too. With a drawing device the coordinates for both the X and Y directions of your drawing area range from -1 to 1, with -1 meaning &quot;all the way left&quot; for X and &quot;all the way down&quot; for Y, and 1 meaning &quot;all the way right&quot; or &quot;all the way up&quot; for X and Y respectively.
You can easily add a Z direction too (also ranging from -1 to 1) for &quot;3D&quot; drawing, but all this does is give you a layered 2D image. There is no perspective (or &quot;depth&quot;) in your final drawing which is great for 2D games and graphics. The reason for this is that the drawing device will simply divide the space up into pixel size steps along X and Y then draw each pixel back to front (-Z to +Z). If you want real 3D though, you'll need some extra mathematical steps.
It is possible (and common) for the device to understand and work with coordinates outside the -1 to 1 range. However, if we want an object to appear on screen than it must be &quot;normalized&quot; so that any coordinates it refers to are within -1 to 1. After this is done to an object the terms &quot;normalized coordinates&quot; and &quot;device coordinates&quot; are practically synonymous, just one refers to the object you altered so that it would fit within the drawing area and the other refers to the drawing area itself.
<h1>Object and World Spaces</h1>
<blockquote>
The 2D [or 3D] pipeline involves with the construction of world coordinate scene ...
</blockquote>
Yes, but you start in &quot;object space&quot;.
When someone creates a model of an object (or draws a sprite) all that matters to them, coordinate-wise, is where zero is within the space they're working. This consideration is called &quot;object space&quot; because the artist isn't concerned with the -1 to 1 drawing area, only accurately representing the object they'd like to draw. A model of a pen might be 6 units long and a model of a person might be 5.5 units tall. The important thing is that all of the points that make up some object are positioned with regard to the coordinate (0, 0, 0) and nothing else.
When later loaded into memory they will be too big for the drawing area (which is only 2 units tall and wide) and the pen will appear larger than the person. It's up to us humans to know what the units mean and adjust them properly. Resizing and positioning all objects in relation to each other instead of each individually being sized with relation to zero transforms the objects into &quot;world space&quot;.
From the shortness of your question I wasn't sure if you knew that yet or not, but I thought I'd include that for completeness, as a good foundation for answering the next part of your question.
<h1>View Space</h1>
<blockquote>
... followed by converting world coordinate to viewing coordinate ...
Isn't viewing coordinate and device coordinate the same things?
</blockquote>
Note that in my explanation above nothing ever happened to the drawing device, or the coordinates of the drawing area. The only thing that ever changed was the objects we wanted to draw. The drawing area is fixed and unchanging, only ever drawing any object that fits within the coordinates -1 to 1.
Each object loaded appears at the center of the drawing area at whatever size it was designed to have (object space) which is practically always too big for the drawing device. After rearranging and resizing every object around each other (object space → world space) we still have a final scene that is too big for the drawing area, and we have no way to move around within the scene. This is where we transform everything into &quot;view space&quot; and work with &quot;eye coordinates&quot;. Again, there is no such space, but what we do to work within it is to consider an imaginary camera and, treating the entire world as one giant object, we resize and reposition everything with respect to the position of the camera. That is &quot;view space&quot;, the movement of everything around a camera, and the terms &quot;view coordinates&quot; (or &quot;eye coordinates&quot;) refer to the positions of everything in relation to the camera.
<h1>View to Viewport</h1>
At this point everything that you want to see should be within the device space, but there are still a few last tasks to perform to get everything to draw.
If you were working on a 3D scene instead of a 2D one, you would perform a &quot;perspective transformation&quot; to create the illusion of depth. This is where you squish and warp things to make them look like they're shrinking into the distance.
Anything outside the drawing area needs to be thrown out. This saves on work for the computer, and it also is considered another transformation from view space to &quot;clip space&quot; because you are &quot;clipping away&quot; the extra data.
And finally, after clipping, you'll do a &quot;viewport&quot; transformation that turns the -1 to 1 coordinates into pixel coordinates.
<h1>Summary</h1>
Well... I didn't intend for this answer to get so long. My apologies if I covered anything you already knew. It's hard to guess what someone does or does not already understand. Please leave a comment if you have any further questions.
Object Coordinates: The positions of points relative to a zero point. The points referred to are the building blocks of some single object.
World Coordinates: The positions of collections of points (objects) relative to a single shared standard zero point.
View Coordinates: The position of all points (the whole scene) relative to a camera.
Device Coordinates: Any position within -1 to 1 on both the X and Y axis (and Z too for 3D). Any point within the drawing area of the device.
Normalized Coordinates: The positions of points of any object (or the whole scene) that have been transformed to fit within the -1 to 1 space of the drawing device.

The 2D pipeline involves with the construction of world coordinate scene followed by converting world coordinate to viewing coordinate, then transforming viewing coordinate to normalized coordinate and lastly converting normalized coordinate to device coordinate.

I am confused. Isn't viewing coordinate and device coordinate the same things?
Can someone give me the detail differentiation among these?

What is the difference between world coordinate, viewing coordinate and device coordinate in computer graphics?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

二维管线包括构建世界坐标场景，然后将世界坐标转换为观看坐标，再将观看坐标转换为归一化坐标，最后再将归一化坐标转换为设备坐标。我很困惑。查看坐标和设备坐标不是相同的吗？有人能告诉我这些细节的区别吗？

在计算机图形学中，世界坐标、观察坐标和设备坐标有什么区别？-腾讯云开发者社区-腾讯云

问在计算机图形学中，世界坐标、观察坐标和设备坐标有什么区别？
EN

回答 1

Computer Graphics用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在计算机图形学中，世界坐标、观察坐标和设备坐标有什么区别？EN