#38416 - iainprice - Sun Mar 27, 2005 10:22 am
How much progress is there on the 3D chips for the DS?
#38429 - 3D_geek - Sun Mar 27, 2005 6:25 pm
From what I can see of the code in ndslib, it seems to have been entirely figured out.
I don't have my PassMe card yet - but reading the code in ndslib, there is a somewhat OpenGL-like library already functioning.
#38447 - dovoto - Mon Mar 28, 2005 12:02 am
Well there is a lot left to do with 3D, basic polygon loading, and texturing is working in somewhat openGLish manner but there is a lot left to figure out. There seems to be a lot of texture types that can be used, toon shading, fog tables, hardware collision and bounding boxes. The 3D example in ndslib does pretty much everything that ndslib can do so far.
_________________
www.drunkencoders.com
#38774 - ecurtz - Thu Mar 31, 2005 5:33 pm
Has the 3d example included in ndslib been tested to work on hardware?
I just got everything set up with my new passMe and I couldn't get it to run. I got a black upper screen and white lower screen. The 2D example seems to build and work fine.
#38830 - dovoto - Fri Apr 01, 2005 4:04 am
Yes the 3D example works on hardware...I will rebuild from a clean dir and make sure it still runs (i change things some times without proper regression testing)
_________________
www.drunkencoders.com
#38831 - dovoto - Fri Apr 01, 2005 4:18 am
No 3D example does not work on hardware ...grrr. It worked yesterday. I am going to blame it on reverting gl to inline functions for the moment. When i get it figured out I will post the update and cause.
_________________
www.drunkencoders.com
#38886 - dovoto - Fri Apr 01, 2005 5:18 pm
After spending an hour or so fighting with CVS and rolling back NDSLIB to before my changes I discovered the issue was not due to ndslib at all. Somehow my 3d example got changed in someway. I restored it from a backup and it appears to build as expected now. Thanks for pointing this out.
_________________
www.drunkencoders.com
#39010 - Spaceface - Sun Apr 03, 2005 3:09 am
something I've been wondering.. I've seen the openGL like calls.. is it actually openGL on the DS or did the ndslib guys just built the functions openGL like so people are familiar with it?
#39012 - tepples - Sun Apr 03, 2005 3:46 am
No hardware actually "uses OpenGL." In general, a driver that implements the OpenGL API translates GL state machine calls into something that the video processing hardware understands. Yes, homebrew developers implement subsets of GL for familiarity.
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.
#39029 - dovoto - Sun Apr 03, 2005 10:19 am
In this case the DS hardware is an openGL state machine. If you look at the semi-port you will notice that most of the calls are simply wrapping a small set of direct register writes. As far as I can tell the hardware behaves very closely to that layed out by the GL min spec. This is the reason I was able to reverse things so quickly.
There are of course significant differences, mainly number formating, lack of features and texture support.
_________________
www.drunkencoders.com