Need help w/2 basic questions

#1 The first question lies in the .cs files. on the client side. I dont have access to the them right to tell you exactly what file and where it needs to be removed. It use to be just one line in the startup file but that might have changed.

As for #2 I have no idea. As far as I know F9 has never did a wireframe effect for me.

#2 Thnx for such a fast reply!!!
So the engine needs to be recompiled to get rid of the message box? uhmmmm If anyone has got the line to modify in the .cs please let me know.

and, yup! F9 used to do that. A bit similar to the visualizing set of tools (and render modes) that are around in the resources.

here r some shots of them:

http://holodeck.st.usm.edu/vrcomputing/vrc_t/tutorials/editing/
check the "interior render" section
cheers! and thnx!

#3 I thought F9 still did go to wireframe? Oh well...

I hat that box also, and every time I try to get rid of it, and just have text, it deletes the entire box, and nothing shows up.

#4 K

#5 You have to run a debug build of the engine for f9 to work.

#6 You're absolutely right Dylan! I started getting this error ever since I compile release versions only. How come that happen? I thought release versions were optimum?

and what about the message box? any ideas?


thnx!

ps. The weird thing is that the view render mode tools I mentioned above only work with debug versions too.... now that you mentioned it.

#7 There are a few things that have #ifdef blocks around them based on the TORQUE_DEBUG symbol, which is defined in debug mode builds only. The render mode changes are one of those things. Another is the stuff to show bounding boxes. A few of the assert tests that loop on a collection of things get the treatment as well. Basically, stuff you like in development but would never want to show up in what you ship.

Do a find in files on 'TORQUE_DEBUG' to get an idea of that you're missing in release mode.

#8 Haha I wondered why I didn't see that wireframe feature til now, been running damn release versions. GRRR

#9 Great guys, thx for the explanation. I wonder why they don't make it work with release versions. I mean, #ifdef stuff to work with releases versions too... or r we supposed to do that? h ah ahah a =)

Now I'm only missing the "hiding the message box" issue.

#10 Alvaro: if I recall, the message box is push'd in the onWake function in playGui.cs, if you just comment out the call, it'll not appear.

//Canvas.pushDialog( MainChatHud ); <-- like that.

Or do you want it to be there, but now show the background box?? in that case, just change the background control in the .gui to be transparent.

#11 Beautiful Phil, that did it!

Sorry gor being a pain with something so simple, and many thnx to all of you guys for the assistance.


cheers!