Creating static VBs on the fly

GlowBuffer::setuporthogeometry calls begintobuffer and endtobuffer which causes a d3d vertex buffer allocation every frame. I wanted to note this because creating a d3d resource on the fly is VERY expensive. Worse than any renderstate changes, worse than inefficient locking of a dynamic buffer.

Just want to make it known for anyone who uses beginToBuffer as a replacement for opengl code.

Well just thinking about it, maybe the drivers are catching this because it is such a small buffer. I remember that using drawprimitiveUP for such small buffers isn't that bad because there was some driver hack where it worked in software. Not sure if that applies.

Eric