Sign in to follow this  
AndyEsser

Doom 3 Style Consoles

Recommended Posts

Heya all, I'm currently in the process of making a Star Trek mmorpg for a small select group of people. I'd like to have the consoles found around the ship to be similar to Doom 3 in that you just walk up to them and a cursor appears, rather than having like a pop up window. Can anyone think of the best way I could implement this? I was thinking along the lines of having the texture put together offscreen and then textures onto the terminal, but what about the cursor and how do i detect the clicks? Thanks in advance

Share this post


Link to post
Share on other sites
Render to Texture would work good for mapping the GUI to a 3d quad. Since the GUI is on a plane (quad) you should be able to simply do ray projection/intersection (with the GUI plane) to map the cursor coordinates to the local GUI coords.

As for detecting clicks, just use your input system (Windows/DI/etc).

HTH

Share this post


Link to post
Share on other sites
Yup, agree with all of the above. You might want to look into some type of compositing system too, but that might be too much for what you need.

Share this post


Link to post
Share on other sites
Thanks for the suggestions guys, i'll let you know how it goes.

Another quick question, don't know if you'll be able to help me or not. I'm using Visual Basic at the moment, and currently using Display Lists (will be moving to VA's soon hopefully if I can get my head around them). I'm currently hard coding the display list code in, but I've just made a crate with 1024 polygons in and whenever I run the program it's coming up "Procedure Too Long".

Anyone know how to get around this? And does anyone know if this'll disappear when I insert my real object loading code, which is obv. much shorter.

Share this post


Link to post
Share on other sites
I'm guessing that all the calls to create the object is exceeding some kind of internal limit for the display list.

The only way I could think to get around this would be to split the display list up into a few parts and call them one after each other.

However what you really should do is get your head around VAs and then VBOs, if only because the driver writers (IHVs) would prefer you to use them over display lists, certainly for large objects, and because display lists are going to be phased out in time.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this