oh gosh i've had so many problems getting d3d setup correctly to display just a triangle. i mean after that it's great, but the initialization is a pain. are you just init d3d directly? i just started a 3d modeller and it uses ID3DXContext and it greatly simplifies D3D initialization. the d3d util library also includes functions to make the view and projection matrices for you, which i've found to be the problem most of the time when i can't get the triangle to show. clearing the buffers to a color other then black also helps in case the triangle is drawn with no light. also make sure it isn't being clipped, i was stupid a couple times and created projection matrices with near Z at 0.0f and far Z at 1.0f.

but above all, if your triangle is being placed correctly (i'd put it at (0,0,0)), check to make sure your view matrix is pointing towards it and that your projection matrix isn't screwed up


Edited by - mutex on 1/3/00 7:42:57 PM

Ok, if you''re writing an editor take a look at retained mode since it has mesh functions, and you can pick primitives out of the mesh. If you''re good in math then go with Immediate mode and write those functions yourself if you really want to or need customized ones. I started in d3d by shutting the lighting off and used D3DLVERTEX struct, in which you specify the color yourself. Then I switched to D3DX that made it heck of a lot easier to setup my app. The wireframe mode in dx7 imm.mode is broken so if one of your primitive''s side touches the clipping plane it goes haywire. Try retained mode where the wireframe works, and can use progressive meshes for LOD. Above all, if you have a great game idea and want to implement it quickly go with an already made engine with a strong editor, like Genesis3D. To go beyond writing a simple room in d3d/OpenGL you need an editor because you will get lost in all the drawprimitive() calls without one. Plus you''ll need to write some kind of structure that holds visible and non-visible polygons to speed up rendering. Plus you will need physics, sound, input, installer and other routines and unless you''re a wizard or have 5+ years of free time then I suggest picking an already made engine, Genesis3D, CrystalSpace, or others. This is from my own experience. Most people think about the rendering side only, forgetting the other stuff like managing large code, documentation, finding/fixing bugs in later stages, and other major parts.
There are some smart cookies out there that can pull it off and more power to them;)

Jerry