Static meshes

#21 Yes, I was looking for a VRAM buffer simply due to the fact that I am under the impression that this will raise performance of the 3d-engine (load once, show many).

Mark > I have been peeking around my habitat for skilled OpenGL programmers and seem to have found one depending he has the time, that would help me alot since your advices (tough well put) is a tad over my current level (hasn't started messing with the engine yet) and my "lead programmer" are not experienced in OpenGL.
What is this Ogre you are reffering to, cant remember it being listed among the resources (hazy memories).

#22 And the project I'm planning NEEDS high performance/lots of meshes !

#23 You have the source... it's not like you're barred from getting that. :)

#24 Hehe, well I guess I'm not the only one looking for high speed and low latency :-)

#25 Ogre is an open source 3d graphics engine. They have a fairly general vertex buffer class that might be worth a look for inspiration - well, when you get a 3d programmer, anyway.

#26 You realize the issue here is not rendering speed/optimization, because 3space already in theory does that, but rather getting the shapes to work in the level properly...

#27 Hehe, well I guess I'm not the only one looking for high speed and low latency :-)

#28 ?? double post above, look at the timestamps!! ??

Ben > I am confused, my initial point actually was to relieve the 3D engine (TGE) of some geometry calculations, let the gfx-card work what it works best (transforming a 3d-space in to a 2d-scene). Do you mean that getting the shapes working is the problem here ??

#29 If you want to replicate what Unreal does with its static meshes in level, all you need to do is get TSStaticMeshes to effect lighting properly. If you want them to be lit, you'll have to add that, which might be... exciting... but still do-able.

As far as I know, Torque's shape rendering library already does what you've described vis a vis keeping vertex information buffered in memory... and if it doesn't, you don't want to write a new rendering infrastructure, but probably just retrofit the functionality into 3space.

The whole point of static meshes is to allow added details to a level without incurring huge collision/visibility calculation hits. The static meshes aren't considered for visibility and collision checking in the same way that level geoemetry is, thus the savings.

#30 Here's a few other vertex buffer code snips that might be of interest:

www.flipcode.com/cgi-bin/msg.cgi?showThread=COTD-VertexBufferClass&forum=cotd&id...

www.flipcode.com/cgi-bin/msg.cgi?showThread=COTD-D3DVertexBuffers&forum=cotd&id=...

www.flipcode.com/cgi-bin/msg.cgi?showThread=COTD-FVGenerator&forum=cotd&id=-1

www.flipcode.com/cgi-bin/msg.cgi?showThread=COTD-VertexBufferProxy&forum=cotd&id...