Game Development Community

dev|Pro Game Development Curriculum

Your Windows registry and Torque

by Gonzo T. Clown · 10/25/2004 (8:06 am) · 26 comments

Whenever DirectX is utilized by an application, a registry entry is made for that program. In the case of TGE and TSE, each time you recompile your code it will see the .exe as a new program and make another entry. Over time this can fill up your DirectInput key with tons of useless entries that so far none of the registry cleaners I have used will even touch. When I discovered this problem I had over 400 useless TGE and TSE entries in my registry that I was more than happy to get rid of.

WARNING!!! If you are not comfortable with your registry STOP HERE!!!! I will not be responsible for any damage you do to your machine.

That being said, this is a really easy issue to clean up manually. Fire up your registry editor and navigate to the following key....

[HKEY_CURRENT_USER\Software\Microsoft\DirectInput]

When you expand it you should see something like the photo I submitted. The TGE and TSE entries will be very obvious. Click on the first TGE or TSE entry so that it's highlighted in blue, and then start rapid fire alternating your "Delete" and then "Enter" keys (if your PC is not set to default to the 'Yes' button, then use your mouse click the 'Yes') As you do this the entry below your deletion will move up and automatically highlight so that you can just hit "Delete" and then "Enter" again. Repeat this process untill they are all gone. Removing them all will hurt nothing because the next time you start TGE or TSE it will put an entry right back. It's no different than the very first time you started Torque.

I would not delete the "MostRecentApplication" key or the "DXDIAG" keys if you have them, no point in it, but the TGE and TSE are a definate cleanup.
Page«First 1 2 Next»
#21
11/05/2004 (11:25 pm)
On the end users machine there will only be one key anyway. The many keys is caused through development ... every time you build a .exe that uses DirectInput and run it, DX checks some stuff and if the .exe has changed it creates a new key. There is no problem for end users, only developers. Developers should know about the problem and be able to fix it, but it should not be done automatically by TGE.

T.
#22
12/11/2006 (1:08 pm)
Wow, I just happened upon this by accident. Normally I would disagree with Tom here, but since this happens across the board with DX apps then I'll agree with him. The only problem is that a lot of developers don't know about this. I just spent about 6 minutes or so deleting a year's worth of old keys, which may explain some of the memory issues I've had as of late.

This needs to be moved to TDN and put right on the front page so everybody knows about it.
#23
07/20/2007 (4:55 pm)
I had about 1100 Torque debug entries.

Thanks for the tip, Gonzo!
Thanks for the reg hack Tom!
#24
04/26/2012 (6:40 am)
It has been brought to my attention that his is still an issue even with current builds so I am bumping this thread to remind people.
[EDIT]Dang, forgot you can't bump resources.
#25
07/01/2013 (2:51 am)
wow, looks like its still an issue after all this time, I had 100's
#26
07/01/2013 (10:03 am)
It will never not be an issue, it's not an issue at the engine level but at the OS and DX SDK level.
Page«First 1 2 Next»