Previous Posts http://www.darkbasicpro.com/apollo/view.php?t=5343&b=1
Heh, well its too bad for these people you still dont agree with me, Raven.
Yes, I understand that those engines are not mainly based on the DX API, it also is made to be compatible with OpenGL, as well as Software execution, and I didnt state that "The Quake Engines were Dx Based"...never said anything close to that. It was just an example, that it Utilizes Dx Functions and windows based extensions, when chosen to run on a DX display and when running on a windows platform.
Direct X is just code and addresses that are compiled (and simplified) into an API, in order to utilize these commands in a Software Developement Environment. Wether it is Visual Basic, or C++, or .Net Developers, Direct X is used to get promising results communicating with multimedia hardware and the cpu, with out haveing to Code everything intricately in C++, or Assembly. Thats what an API is for.
You dont need your work to be 1 000 000 000 lines long.
(Building Blocks), you build, then someone will build on top of that, then someone else on top of that, etc...
API is the Application Programming Interface, it helps more simpler Languages (like RAD Languages), do things that they couldnt normally do with there basic code. Wether is it Speed of the Program, or versatility or Direct Access to hardware, as well as the Power the Language has over the OS the application is Developed for, API's are to help get those things done....but there also used bigtime in C++ code too.
Im mean you could write a whole fricken game in C++ code, or assembly, it would be fast and everything without using your essential API's, but it would take your team Forever to do it...why the hell waste the time.
Heres the Deal, what im trying to say is (Im gonna try to explain myself as best I can cuase this is the last time),
In General..(read backwards)
Harware
Athlon +2000 -=- Plus GeF4 -=- 786DDR <br>
I would rather USE VB and the DX SDK....