gbadev.org forum archive

This is a read-only mirror of the content originally found on forum.gbadev.org (now offline), salvaged from Wayback machine copies. A new forum can be found here.

DS development > Can't compile, dualis not displaying 3D

#150345 - djmcbell - Sat Feb 02, 2008 5:42 pm

Got a bit of a problem - I've just moved to a new PC to start developing again, and have installed the latest version of DevKitPro.

In any case, it will compile the examples fine, but won't compile mine. Also, dualis (and also DeSmume or whatever it is) doesn't want to display 3D on anything compiled on my current PC. It displays my old stuff fine from my old PC however.

Whenever I try and compile my stuff on my new PC, I get these bugs in the command window -

Code:
error: 'VRAM_A_MAIN_BG_0x6000000' was not declared in this scope
error: 'VRAM_B_MAIN_BG_0x6020000' was not declared in this scope
error: 'VRAM_C_MAIN_BG_0x6200000' was not declared in this scope


All my other bugs, I imagine, will be solved when these are sorted. All I've done is copied the stuff over from my old PC (where it worked fine), reinstalled DevKitPro and tried to compile it using the new install. I assume I'm missing something because I remember having to do a few other bits and bobs after installing DevKitPro last time.[/code]

#150347 - djmcbell - Sat Feb 02, 2008 6:47 pm

Sorry - the declarations up there are going to look a bit odd, as the VRAM_C should be a sub, not main (didn't copy and paste from the command window, doesn't want to do it).

Anyhoo, seems to be a problem in setting up the banks themselves as my 2D stuff doesn't want to work either. Only thing that does is either the examples (for some reason) and my old stuff which uses neither to any great effect, like drawing on the screen.

The dualis problem will be unrelated, but if anyone can help on that too I'd be grateful.

#150348 - Normmatt - Sat Feb 02, 2008 7:41 pm

djmcbell wrote:

Code:
error: 'VRAM_A_MAIN_BG_0x6000000' was not declared in this scope
error: 'VRAM_B_MAIN_BG_0x6020000' was not declared in this scope
error: 'VRAM_C_MAIN_BG_0x6200000' was not declared in this scope



In the latest libnds the addresses were changed to have a 0 before the 6 so they should be:
VRAM_A_MAIN_BG_0x06000000
VRAM_B_MAIN_BG_0x06020000
VRAM_C_MAIN_BG_0x06200000

#150378 - djmcbell - Sun Feb 03, 2008 1:05 pm

Right then - that's sorted. Unfortunately it seems that there's other things not working -

glViewPort (not declared)
glTexCoord1i (not declared)
glReset (not declared)
glIdentity (not declared)

I think this is likely to be something else to do with the new version of libnds I'm using. Any thoughts?

#150379 - kusma - Sun Feb 03, 2008 1:16 pm

djmcbell wrote:
Right then - that's sorted. Unfortunately it seems that there's other things not working -

glViewPort (not declared)
glTexCoord1i (not declared)
glReset (not declared)
glIdentity (not declared)

I think this is likely to be something else to do with the new version of libnds I'm using. Any thoughts?


glViewPort -> glViewport
glIdentity -> glLoadIdentity

glReset has simply been removed, and that's a good thing IMO. It was a horrible function that removed the symptoms of state-leaks.

glTexCoor1i am I not sure about. I'm using glTexCoord2f32() myself, which seems to currently be available.

#150393 - djmcbell - Sun Feb 03, 2008 7:10 pm

Right then. I'm going to use the demos provided with the latest build of devkitARM to learn how to do 3D again and adapt those.

Anybody got any thoughts on the Dualis problem? Right now it's able to -

* display one old 3D demo of mine fine, which uses the bottom screen for 3D
* all other old 3D demos of mine flicker like crazy
* most of the examples will display their first frame, then nothing
* just tried the paletted_cube demo, which displays but flickers lots