BeNews recently ran an interview with Realtech-VR (great name, that) which covers everything they have been doing since SpaceGirl, a great looking 3d space shooter that has been discontinued for quite a while. The intriguing thing is that it quickly came out in the interview that Realtech-VR is strongly considering creating a Direct3D wrapper for BeOS api’s. In otherwords, Direct3D apps would just build on BeOS. Read on for details…
While the interview only touches on a wrapper for Direct3D, comments posted by Realtech-VR peeps indicate that they are planning to continue after Direct3D on to a port of the whole api. Says a RealTech-VR employee:
Since DirectX5 to DirectX7, the API didn’t really evolved. Just new functions, easy to update. DirectX 8 was completly rewritten (by NVidia) and it’s simpler and also designed to run on the XBox. That’s means, it was ‘portalibilized’ and easier to adapt on other plateform (for console).
That point, it enables us to really do the porting into BeOS. At the end, the DirectX 8 SDK will have the same headers than the DirectX 8 SDK official, with perhaps slight changes.
Same name of shared and static libraries will be given and some samples of the original SDK will be ported into BeOS (some of them are too Win32 specific and will be rewritten but in final, the results will be the same).
Only I hope that display drivers writter will includes the OpenGL extensions that enable us the use of single pass multitextures (ARB extensions) and other extensions in order to have a ‘perfect’ implementation.
What this will do is create a wrapper for the BeOS openGL and media wrappers, which allow games coded to Microsoft’s DirectX coding API to compile correctly as BeOS applications, and just run. Of course, mild porting will be required for other portions of the windows API, but the work will be extremely simplified.
Above and beyond that, they have also created a great looking resource translator, that takes windows resource files (which define the layout of the gui windows) and translates them to BeOS layouts and resources. This would be invaluable in porting a gui application with lots of complicated controls.
This could be HUGE, and allow all sorts of games (and other apps) to make their way to BeOS with minimal cost. If this group manages to get all these items completed well, it will be astounding. They are single handedly lowering the barrier ports are facing by exponential amounts. It’s coming down to “change the gui front end by running the resources through a translator, and writing a bit of code, compile and fix a few warnings in the directX engine. Link.”
Anyone else excited about this?
[powered by WordPress.]
BeOS geeks and
haiku error messages -
the perfect marriage.
Since 1998 - Until the Last User Leaves...
— BeGroovy, established 1998
23 queries. 0.064 seconds
[powered by WordPress.]