Code center > Suggestions
Walls!
PurpleYouko:
DirectX sets up the graphics card as an object then sends commands directly to it just as if it was an integral VB object like
application.something-or-other
or
rob(t).mem(.Ties(k).nrg)
All you have to do in order to use DirectX in VB is to go to "Project->References" then scroll down the list to "DirectX 8 for Visual Basic Type Library"
The concept is very simple but it takes a lot of messing about to get anywhere. The beauty of it is that graphics functions don't drain processing power from the main processor speed. Thay are all done directly on the graphics card.
Numsgil:
The one thing I've noticed between OpenGL and DirectX is that it generally takes less code to get something up and running in OpenGL than DirectX.
And there's those nice NeHe tutorials on OpenGL (most of which have a VB port ready.)
PurpleYouko:
Ever seen any benchmark speed tests between the 2 systems?
Numsgil:
As near as I can tell they're both about equivelant.
One runs faster on some systems, one runs faster on others. Generally speaking they're about equivelant.
PurpleYouko:
From what I have just been reading they appear pretty similar except for the coding.
From what I can tell from reading a few articles, OpenGL is more like C in its format while DX is more like VB.
As I am not a great fan of the style of C and greatly prefer to program in VB, I think DX is probably better for me but for you I expect the opposite is true as you are very familiar with C.
I am really pretty new to both but DX looks easier from my persective.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version