VertexBuffers: Lock/Unlock and same memory address....

Hot Topic

problems with DirectX 9.0c
Question about managed DirectX DLL versions (and compatibility with future versions)
DirectX Extensions For Visual Studio .Net 2005
Height of a picture
Microsoft.DirectX.dll version 2.0.900 You Can Not Create the device Manual
MDX Matrix.RotateX not doing what I expected...
I am going into development of games(help needed)
i need help! pls I want to begin to write games
Disable FSAA for some primitives each frame? (disable it temporarily)
How do I develop games for the XBox 360?

Game Technologies

DxDiag shows missing files after .Net 2.0, Oct and Dec 2005 SDK.
.X Export a simple Maya model
How to set vertex color prior to DrawPrimitiveUP call?
Geometry.IntersectTri
DirectX and Visual C# .NET Express???
Setting a custom cursor image [MDX2]
Static Buffer and Stack Back Trace error
Meshes & Textures
non-FVF VertexBuffer
Having a cpu usage issue...

VertexBuffers: Lock/Unlock and same memory address....

If i create only one static vertex buffer in my program and i do:
Lock/Unlock....Lock/Unlock....Lock/Unlock....etc - all this calls return me same start memory address for vertex buffer data if this buffer not been recreated or not
P.S. sorry for my english pls :)

Answer this question

VertexBuffers: Lock/Unlock and same memory address....

  • PierreEric

    It might or it might not. But do NOT assume you will always get the same address. Also, NEVER write to the address without doing a Lock first, and ALWAYS use the new address. It will work on some cards, and not on others.

  • bbyrd

    Tom is correct - it depends on what pool the VB was created in, what lock flags are used, etc.  It will also depend on the driver behavior, and may change even by driver revisions.

    Also as Tom said, since you have to Lock to write to the VB, there's no reason not use the new memory address you just got with the most recent Lock call.

  • VertexBuffers: Lock/Unlock and same memory address....
Answer this question