Game Development Community

Mission Editor cursor draws itself thousands of times

by Steven B · in Torque Game Engine · 11/25/2004 (12:32 pm) · 10 replies

If I hit F11 to open the mission editor the cursor
draws itself like I was drawing with the mouse in mspaint only it's drawing cursors. If I go up to the main menu in the editor the menus will come down and stay down. If I click on anything in any of the menus nothing happens. While I am doing this the cursors continue to redraw.

About the author

www.AnswerRack.com Ask Questions There, Get Answers. You can Ask a Game Development Question You can Ask A Mechanic A Question. Ask just about anything.


#1
11/25/2004 (12:41 pm)
Is this a new behaviuor? Did it always do this, or has it just started doing this?

Is it possible this is a graphics driver issue?

Have you modifed the code at all? If so did it work before the modifications?
#2
11/25/2004 (1:58 pm)
That usually happens when there's nothing to draw, for example if you set the canvas to an invalid control, or if the mission editor isn't working properly, so it's not rendering the world, could happen if you open the editor without a mission open. Did you modify the code? That might be your problem then.
#3
11/26/2004 (7:52 am)
Yes this has always done this since I got torgue. I brushed it off at first because I was new to it. It has happened to me with the starter.fps also. I tried using a tutorial from code sample .com which is in the torgue getting started section. I tried that to clear up the issue but it did it anyway.
I got torgue about a week ago and all I have been dealing with is trying to get it to work.
My computer is not the problem.
The drivers are not the problem.
I have updated everything.
It is more than up to par to handle torgue.
This would be a scenerio to use
I have set torgue to open with
tutorial.base I can hit F10 fine no problem that part works. But if I hit F11 then the problem starts. It did that in starter.fps too. Same problem.
Also the racing starter kit won't work
I get a blank screen with a filled square as a cursor, there is a blinking caret in the upper left hand corner and the screen has a one inch thick border. I changed my console colors to yellow and purple that is why I know it has a one inch border.
I did also go into the starter.fps and move around the huts,poles,fire,and terrain but I had to go to New Control and do it that way. The thing is going by any tutorial and pressing F11 the problem happens.
#4
11/26/2004 (7:58 am)
Are you running it as DirectX or OpenGL? Its ounds like a driver problem. When I run under directX the editor don't work properly but are fine under openGL
#5
12/01/2004 (7:58 am)
I went to Add/Remove programs and deleted the Sample Torgue Demo App that tou can download from the website, the one that has the purchase price in the lower right hand corner. As soon as I did that and ran tourge the problem was gone.
#6
12/08/2004 (11:17 am)
I have the same problem... It happens when I create a new mission or load an existing one.
The strangest thing is, there are no console errors whatsoever and it works like a charm in the starter.fps mod. Only not in my game :(

Any help is really appreciated...
#7
12/08/2004 (12:56 pm)
Pfffff.... Finally managed to fix the problem... If anyone has the same problem:

make sure you add your connection to the RootGroup...

createServer("SinglePlayer", %mission);
   %conn = new GameConnection(ServerConnection);
   RootGroup.add(ServerConnection);   // <- This line was commented out...
#8
12/08/2004 (10:16 pm)
That's really mysterious... All objects are added to the RootGroup by default. Is the $instantGroup maybe getting set wrong? That's where objects are actually added by default.
#9
12/09/2004 (12:28 am)
@Ben...

I think the $instantGroup is set by default... I started my project from scratch and I can only find it in the default common code in my project.

In the common/server/clientConnection.cs
$instantGroup = ServerGroup;
$instantGroup = MissionCleanup;

Do I need to fill this variable myself?
#10
12/09/2004 (11:30 am)
Not necessarily, just that it might explain why you have to add stuff to the RootGroup.