Quote: "Ditto. DBPro and GDK are separate products and should be treated that way.
Woa.... Just now understood your post! I disagree completely. GDK IS built on DBPro code. 1.0 had (almost) all the same commands as DBP but used C++ as its native language-- and that goes for the 2.0 version as well. Mistral hasn't changed DBP code, he (assumed masculine) is only changing the way C++ talks to DBP. If that's true, then the functionallity should still be there for ALL DBP commands. If he is re-writing DBP code, then I could see where it would be different. At any rate, compatability with previous versions or not, the functionallity should not suffer from a version change. I do understand that there are some functions that would (and are) faster when using the C++ funtions that DBP uses for DBPro (as a compiler), but there are also funtions that don't even have a comparable C++ function. There are even some that you would have to write in DX/C++ just to make it work. For instance, dbCreateImage(..) or dbCreateImageFromMemblock(..), just isn't working. I had to resort to using a bitmap to write to and the getimage(..) to make a custom image-- this is unacceptable when 1.0 could do it. I was told by Mistrel that all the DBP compatable plugins were working in 2.0 to include Dark AI. Dark AI uses the DBP vector assignments and 2.0 excluded them. This is more than just a "not backwards compatable" issue, it's something that was told to me by the person in charge of "making it happen" not "making it happen".
I paid for rc4 but it hasn't lived up to my expectations or even those told to me by the programmer (Mistrel). Perhapse when the final version comes out, it will be everything I expect (and more), but for now, it's not even functional enough for me to use to make the game I want to make. If I hadn't decided to start another project in DX/C++, I would simply go back to 1.0 and work around the issues it has.
Don't get me wrong, I appreciate the work Mistrel (and anyone else that is working on 2.0) is doing, but it's not ready for the lime light. Perhapse it should go back to beta and get the compatability with DBP fixed first, and then send it to release candidate status.
I hope that soon it will be ready to use as a fully functional extension of DBP. I have learned a lot from programming using 1.0 and I think I could learn a lot more with 2.0 when it's ready. Please don't think I'm "dissing" Mistral; I know it's not easy to do what he's doing and I have great respect for that. I just wish he had told me how many problems 2.0 had before I invested so much time in it. I understand there are issues with every product, especially before it's ready to be released as "finished".
All the love to you fellow programmers.
The fastest code is the code never written.