Vertex buffer - Revision history

Tonyhilliam at 00:46, 18 January 2018

2018-01-18T00:46:37Z

← Older revision		Revision as of 00:46, 18 January 2018
Line 34:		Line 34:
	[[Category:Modeling]]		[[Category:Modeling]]
	[[Category:Content creation]]		[[Category:Content creation]]
	~~[[Category:TRS18]]~~

Tonyhilliam at 03:54, 17 January 2018

2018-01-17T03:54:57Z

← Older revision		Revision as of 03:54, 17 January 2018
Line 31:		Line 31:

	Vertex count also has a minor direct impact on performance. Given two meshes where all else is equal, the one with the lower vertex count will have better performance and is considered more efficient. Except in extreme cases, mesh efficiency is not a major performance concern.		Vertex count also has a minor direct impact on performance. Given two meshes where all else is equal, the one with the lower vertex count will have better performance and is considered more efficient. Except in extreme cases, mesh efficiency is not a major performance concern.

			[[Category:Modeling]]
			[[Category:Content creation]]
			[[Category:TRS18]]

Windwalkr at 10:01, 13 October 2017

2017-10-13T10:01:45Z

← Older revision		Revision as of 10:01, 13 October 2017
Line 26:		Line 26:
	An efficient mesh will approach three indices per vertex.		An efficient mesh will approach three indices per vertex.
	All meshes will have exactly three indices per polygon.		All meshes will have exactly three indices per polygon.

			= Impact on Performance =
			Vertex count is loosely correlated with polygon count, which is one of the primary concerns when optimizing for performance.

			Vertex count also has a minor direct impact on performance. Given two meshes where all else is equal, the one with the lower vertex count will have better performance and is considered more efficient. Except in extreme cases, mesh efficiency is not a major performance concern.

Windwalkr: Windwalkr moved page Vertex Buffer to Vertex buffer

2017-10-13T09:44:48Z

Windwalkr moved page Vertex Buffer to Vertex buffer

← Older revision	Revision as of 09:44, 13 October 2017
(No difference)

Windwalkr: Created page with "A vertex buffer is a component of a render chunk which stores an array of vertices. A vertex buffer in E2 is limited to 65k vertices; any mesh which is larger ..."

2017-10-13T09:44:24Z

Created page with "A vertex buffer is a component of a render chunk which stores an array of vertices. A vertex buffer in E2 is limited to 65k vertices; any mesh which is larger ..."

New page

A [[vertex buffer]] is a component of a [[render chunk]] which stores an array of vertices. A vertex buffer in [[E2]] is limited to 65k vertices; any [[mesh]] which is larger than this will be split into additional [[render chunk]]s, each with their own vertex buffer.

= Vertex Format =
Each vertex in the buffer contains the coordinate (XYZ) of the vertex in 3D space along with various metadata, possibly including:
* Texture UV coordinates.
* Normal vector.
* Tangent vector.
* Animation bone weights.
* Color.
* etc.

= Correlation with Polygons =
There is no true correlation between the number of vertices and the number of [[polygon]]s in a mesh. A number of approximations can be made, but these may be wildly inaccurate depending on the nature of the mesh:
* Each polygon in the mesh is a triangle, with exactly three vertices.
* However, the vertices may be shared between polygons. A fully contiguous triangulated mesh has three polygons sharing each vertex, resulting in an overall average of one polygon per vertex.
* More complicated meshes might have additional polygons sharing each vertex.
* Discontinuous meshes might have less polygons sharing each vertex.
* Even where polygons appear to share a vertex due to their 3D shape, they may in fact be using separate vertices because the vertex metadata differs per polygon.

Large and well smoothed meshes are likely to approach the one-polygon-per-vertex average because any discontinuities in shape or metadata are likely to be in the minority.

No mesh should have more than three vertices per polygon.

= Correlation with Indices =
An exceedingly inefficient mesh will have one [[index]] per vertex.
An efficient mesh will approach three indices per vertex.
All meshes will have exactly three indices per polygon.