I haven't explored JOGL enough to remember, but the loadIdentity function (its the function name i'm not sure about) replaces the current matrix with the identity matrix, which should do what you need. Draw your shapes, call the identity matrix, draw your interface.

ok. I almost got it;
(this is real time online learning)

I can type a translate(width/2, height/2) after the reset Matrix to recover the original x and y, but how do I figure out the original Z value?


[edit]
(I meant how can I figure out without printing the matrix, copying and pasting the value - I'm looking for the formula of the original z. Where does the height*8660253 comes from?)

If you call "camera();" it resets the camera to the default 0,0 in the top left, and width,height being bottom right.

the problem however, is that the screen has a z-index stored form all the 3D stuff. What may be happening, is that the 0,0,0 -> width,height,0 plane may be "behind" the 3D stuff you've drawn (as far as processing is concerend).

Iv'e had to fiddle with the scene I'm drawing in the game I'm writing, so that things do not project too close to the camera, and so pass through the interface.

Not knowing what you're doign in the 3D section of your code, it's ahrd to suggest possible solutions. But if possible, I'd reccomend trying to move objects away from the camera (maybe make them bigger to compensate) and see fi that helps.

Have you tried calling perspective(); and camera(); after the 3D part, and before the interface section, to reset the view back to the default settings?

I've juse done a test with an applet where I'm doing similar to what you want (albeit without modifying perspective() previously), and I had things working fine.

What I have is:
Code:

void draw()
{
  camera(cx,cy,cz,cx,cy,0,0,1,0); //set camera for 3d stuff
  perspective(PI/7.0,1.0,cz/10.0,cz*10.0); // set perspective for 3d stuff
  .. draw 3D stuff ...
  camera(); //reset camera
  perspective(); // reset perspective
  image(radar,0,0);
  ellipse(... etc ...);
} 

This seems to work fine for me (except z-depth stuff, but that would be solved if I changed the 3D stuff to be further away because of the perspective)

Having had a look, it does look like there may be some issues with perspective(...); things.
I couldn't get the box to be obscured at all.
The second call to perspective(); does reset the perspective, but doesnt stop the second box() being drawn behind the first at all times.

The only way I could get it so that the box can be "behind" the interface (or infront, if close enough) was using camera(...); to move the camera closer or further away from the object.

The only weirdness that I've experienced so far with multiple camera/perspective calls is that lights seem to only apply for the last camera instead of per camera. Of course, this doesn't mean that this is the only weirdness, just the only weirdness I've experienced. Here's an example:

Code:

import damkjer.ocd.*;
 
Camera persp;
Camera orth;
 
void setup() {
  size(320, 240, P3D);
  persp = new Camera(this, 100,-150, 200);
  orth = new Camera(this);
  rectMode(CENTER);
}
 
void draw() {
  lights();
  background(204);

  orth.feed();  
  rect(0, (height / 2) - 20, width, 40);

  persp.feed();
  rotateY(PI/3);
  box(50, 50, 50);
}
 
void mouseMoved() {
  persp.tumble(radians(mouseX-pmouseX), radians(mouseY-pmouseY));
} 

-and-

Code:

import damkjer.ocd.*;
 
Camera persp;
Camera orth;
 
void setup() {
  size(320, 240, P3D);
  persp = new Camera(this, 100,-150, 200);
  orth = new Camera(this);
  rectMode(CENTER);
}
 
void draw() {
  lights();
  background(204);

  persp.feed();
  rotateY(PI/3);
  box(50, 50, 50);
 
  orth.feed();  
  rect(0, (height / 2) - 20, width, 40);
}
 
void mouseMoved() {
  persp.tumble(radians(mouseX-pmouseX), radians(mouseY-pmouseY));
}