Hotkeys for TDC commands (RE: changes in 1.3)?

XanderF · 07-10-07, 08:33 PM

In another thread regarding the changes for 1.3, I mused...

Quote:

Originally Posted by Me

Are there hotkeys that can be used to set the various range getting functions?

I'd like to minimize my scope time, and it definitely adds time to have to keep running the mouse up to the upper right corner to set the bearing, then switch the mode to range, then work the stadimeter, then move the mouse back to the upper right to transmit to TDC, etc.

If I could just [pg]-[up] to raise the scope, hit a key to run the stadimeter, hit a key to send to TDC (with voice comms, could program this key to saying "range, mark"), [pg]-[dn] to lower the scope...that'd be great.

With the above changes, this would be damn near EXACTLY how the real skippers did it. Up scope, "Bearing...mark", "Range...mark", down scope. Wait a few seconds, up scope, "Bearing...mark", "Range...mark", down scope. Estimate speed and heading.

...now, looking at the "commands.cfg", I DO see some commands that would be useful, here:

Quote:

[Cmd334]
Name=Set_TDC_bearing
Ctxt=1
[Cmd335]
Name=Set_TDC_target_range
Ctxt=1

...thing is, even with RFB installed, these do not appear to be mapped to anything.

Does anyone know if they work at all? And, hopefully, as I think we'd like?

It would seem if these commands worked properly, it would tie in with the new targeting method WONDERFULLY.

Jaeger · 07-11-07, 05:54 AM

very interesting idea, i will try it. are there hotkeys to start and stop the stopwatch?

WernerSobe · 07-11-07, 07:54 AM

These are old. You can even find them in sh3. And you cant do anything with that.

Not all commands in that file can be mapped to a key. They call a function and require attributes. So basicly Set_TDC_Target_range requires the range as attribute. This function is called when you click on the little triangle on stadimeter. The current stadimeter Range is used as attribute. But if you just call the function without attributes by binding it to a key an error will accur. Its just a minor error and you can only see it by looking through debuging logs. In game just nothing will happen.

Most of the commands in that file are like this by the way. They are needed for the game mechanics but they are not usefull for us.

XanderF · 07-11-07, 01:03 PM

Well, crap. So is there no way to get around this but to keep mousing up to the upper right corner to keep flipping 'pages' in the rather ridiculous input device?

mgbmike · 07-11-07, 08:20 PM

@ XanderF

Maybe this will help?....

http://www.subsim.com/radioroom/showthread.php?t=117517

07-11-07, 01:03 PM	#4
XanderF Samurai Navy Join Date: Jun 2003 Location: Portland, OR Posts: 554 Downloads: 14 Uploads: 0	Well, crap. So is there no way to get around this but to keep mousing up to the upper right corner to keep flipping 'pages' in the rather ridiculous input device? __________________

07-11-07, 08:20 PM	#5
mgbmike Bosun Join Date: Apr 2005 Location: Central Connecticut Posts: 66 Downloads: 2 Uploads: 0	@ XanderF Maybe this will help?.... http://www.subsim.com/radioroom/showthread.php?t=117517 __________________ Dual core 2.8 Ghz HP Media Center running XP pro 2 Gb mem ATI X1650 w/512 Mb mem Realtek High Definition Audio

07-11-07, 05:54 AM	#2
Jaeger Chief Join Date: Jul 2005 Posts: 316 Downloads: 28 Uploads: 0	very interesting idea, i will try it. are there hotkeys to start and stop the stopwatch?

07-11-07, 07:54 AM	#3
WernerSobe Commodore Join Date: Jul 2006 Posts: 625 Downloads: 5 Uploads: 0	These are old. You can even find them in sh3. And you cant do anything with that. Not all commands in that file can be mapped to a key. They call a function and require attributes. So basicly Set_TDC_Target_range requires the range as attribute. This function is called when you click on the little triangle on stadimeter. The current stadimeter Range is used as attribute. But if you just call the function without attributes by binding it to a key an error will accur. Its just a minor error and you can only see it by looking through debuging logs. In game just nothing will happen. Most of the commands in that file are like this by the way. They are needed for the game mechanics but they are not usefull for us.