Machaira: That is code modularity, not Binary Modularity.

UDT means User Defined Type, yep. If speed is the most important, just one exe is best, for VB.

When increasing resolution, the thing that is important is fill rate. For instance, at 300x300 resolution, with, say, 900 triangles transformed, 2700 vertices are being transformed, and 90000 pixels are being drawn to the screen. At 1000x1000 resolution (I am making up these resolutions so they are easy to square, by the way =), with 900 triangles, you are STILL transforming 2700 vertices, but you DRAW 1,000,000 pixels. Obviously, the speed at which your video card (HW accelerated rendering, even on older cards, all drawing is done in hardware, while on newer cards, the vertices are also transformed in hardware) can draw pixels.

I first learned DX8 with VB, and http://www.directx4vb.com . Once I got a little experience with C++, I decided to give it a go. To tell the truth, the difference between using DX8 in C++ and VB is VERY small. There are a few differences, but the majority is the same. As time went on, I STILL used the DirectX4VB site, even while implementing the things in C++.

On the other hand, given your timescale, I wouldnt go C++ since there is a lot of getting used to, and you want to spend most of your time getting your project right.

Z.