kingpinzs: In general falling back to GDI to overlay text on a DirectX game is a fairly bad idea; I''m an OpenGL guy myself but I understand that you''ll get a major performance hit if you do that - plus you won''t be able to take advantage of DirectX niceties like antialiased text. Not an expert as I said, please correct me if I''m wrong.
TheNerd: When you call System("cls"); as recommended by ToohrVyk you''re (under Win 2000 and XP) creating a whole new shell instance, allocating 640Kb to it, and then calling a system function that gets trapped by the emulation layer anyway (I *think*).
If you''re asking because you''re doing a console-mode game, I''d seriously recommend implementing a rendering layer using the console functions described here.
It''ll actually help you in the long run too, because you''re essentially getting a good taste of using an output API - which gives you a great context for understanding what level of abstraction you''re at when you get onto DirectX/OpenGL/whatever.
A really great implementation would be if you wrapped the console functions in a wrapper class of your own, which you then call with member functions such as renderer.OutputText (line, column, "Some text"). You could then expand the class to draw little windows for you and all sorts of stuff - AND you''d be getting really used to using an API to handle your output.
I use the console functions in my ASCII renderer class, which provides a similar implementation to that described above but doesn''t handle text output - although do feel free to extend it
www.coldcity.com
code, pics, life
