Thread: Random Window Close

Hey guys, ok whats going on here is, that my game when it is in the actual game play screen, when it has the map and stuff drawn, it loads everything fine, connects to the MySQL server and draws all my pretty little squares and triangles I am using for testing, but after a few seconds it closes with this error

The thread 'Win32 Thread' (0x1498) has exited with code 1 (0x1).
The program '[4988] TD4.exe: Native' has exited with code 1 (0x1).

Now it only happens when it is in the game play screen, in the menu it will run fine, does anyone have any ideas why or how I can fix this, I am doing Windows progamming and using OpenGL

Thanks in advance guys

Thanks, I found where it is exiting, now I just need to work out why :P

Hehe, yes it can be quite annoying sometimes, it's in my MySQL code and I do not have a clue why it's exiting so I am going to have to go through it all and see whats going on

maybe you could help me, it's a completely different problem but you seem to know what your talking about, I think my code is generating a MySQL error, thats the only reason for the line that is exiting my program to have been called. Does MySQL complain if you try to connect and disconnect to it very very fast, because everytime my screen refreshs I connect to MySQL to get screen data, building locations and unit locations and the like. And if that would cause an error is there a way I can limit that connect to say once every second, cause thats what I want for my game

Thanks in advance

I also don't want to do it that way, cause the game, once it's finished it going to be a multiplayer online game, I will be connecting to a remote server and what i need is a way to connect once every few seconds say, can anyone help me out in limiting my connection to MySQL, I assume the easiest way would be to use a timer, but my knowledge of Windows programming (in that sense) is limited

Thanks in advance

What Shakti is referring to is very similar to replicating the database on the client computer. However replication can take a long time if the database is large. Instead of always accessing the server you access the local database and modify it. Then when you are done you send the new data to the database on the server.

The point is you don't want to tie up network traffic for every single piece of data you need. Also when it is inevitable that you must communicate with the server you want to make your request as simple as possible. This is, of course, speaking from a game programming perspective as to how you should use your database.

If you tie up the server or the network (in a LAN game) you will cause lag both on the client systems and on the server. This could bring the game to a standstill very quickly.

I recommend buying a book on multiplayer game programming.