VertexBuffer constructor: why both Type and VertexFormat?
- From: "Peter Oliphant" <poliphant@xxxxxxxxxxxxxxxx>
- Date: Mon, 12 Dec 2005 12:37:45 -0800
I'm using the following constructor to create VertexBuffer's:
public VertexBuffer(Type, int, Device, Usage, VertexFormats, Pool) ;
I had a problem with my application, until I realized I was passing a Type
based on a PositionColored vertex and a VertexFormat set to PositionTextured
(FWIW, the goal was PositionTextured).
Why are both parameters required? It seems like if I passed a Type based on
a vertex that was different VertexFormat than what is passed it just
wouldn't work. I'm very much a beginner in regards to DirectX, so it's
possible mixing and matching can be done. I just don't know the rules yet
(except for the above based on the my example, where I learned you don't mix
PositionColored with PositionTextured)...
Thanks for responses! : )
For context: VS C++.NET 2005 PRO (and Express, using both!!! : ) using
clr:/pure syntax...
[==P==]
.
- Follow-Ups:
- Re: VertexBuffer constructor: why both Type and VertexFormat?
- From: Stephan Rose
- Re: VertexBuffer constructor: why both Type and VertexFormat?
- Prev by Date: Re: Deployment Problems
- Next by Date: Re: VertexBuffer constructor: why both Type and VertexFormat?
- Previous by thread: Deployment Problems
- Next by thread: Re: VertexBuffer constructor: why both Type and VertexFormat?
- Index(es):
Relevant Pages
|