The main reason to stick with OGL is portability.
Even if you can specify the use of DX on Windows, If I need to write some custom function to do something not implemented that I need - I wouldnt want to have to write that twice to work both on OpenGL *and* Direct-X.
If I wanted some 2D DX7 code, I still have my own 2D engine I did when DX7 was out (which didnt use any 3D at all and could run even on a Trident 1mb card hehehe), even made some games out of it (Revenge of the TimeLord and Frosted if anyone here ever saw them)
My point is, the best feature of BMax is portability and the "write once, compile everywhere" idea. And if it's having trouble with Intel's GMA chipset (which is now everywhere on laptops), it is a big problem in my book.
Have anyone tested to see if this also happens on Linux machines with those GMAs? This would clarify if it's a drivers problem or an incompatibility with the way BlitzMax handles OGL stuff.
Even if you can specify the use of DX on Windows, If I need to write some custom function to do something not implemented that I need - I wouldnt want to have to write that twice to work both on OpenGL *and* Direct-X.
If I wanted some 2D DX7 code, I still have my own 2D engine I did when DX7 was out (which didnt use any 3D at all and could run even on a Trident 1mb card hehehe), even made some games out of it (Revenge of the TimeLord and Frosted if anyone here ever saw them)
My point is, the best feature of BMax is portability and the "write once, compile everywhere" idea. And if it's having trouble with Intel's GMA chipset (which is now everywhere on laptops), it is a big problem in my book.
Have anyone tested to see if this also happens on Linux machines with those GMAs? This would clarify if it's a drivers problem or an incompatibility with the way BlitzMax handles OGL stuff.