Tango Lima Posted December 27, 2015 Posted December 27, 2015 Would it be possible to implement another way of assigning the radar cursor control where the control of it is given by two axes instead of four key inputs? Thomas
Brisse Posted December 27, 2015 Posted December 27, 2015 +1 I would like to use the microstick on my HOTAS Cougar throttle, which would control the TDC in an F-16. I know it's not 100% realistic for the M2000 but I like to map my controls so that they are similar for most aircraft. Easier to remember all the controls that way.
PiedDroit Posted December 27, 2015 Posted December 27, 2015 Also, in PPI mode the movement of the piper is very arc-ish (i.e. when slewing right or left the piper will follow an exagerated curved path), is that the way it should be?
Zeus67 Posted December 27, 2015 Posted December 27, 2015 Also, in PPI mode the movement of the piper is very arc-ish (i.e. when slewing right or left the piper will follow an exagerated curved path), is that the way it should be? If you want the TDC to be above the target, then yes. If it moves in x/y, you can place the TDC above the icon, but it won't be above the target because the target does move in an arc as well. "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." "The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."
PiedDroit Posted December 27, 2015 Posted December 27, 2015 (edited) If you want the TDC to be above the target, then yes. If it moves in x/y, you can place the TDC above the icon, but it won't be above the target because the target does move in an arc as well. I know that (polar coordinates, etc), but it feels awkward to use (if the target is below and left, I will naturally move the piper down and left). I'm just wondering how's the piper movement in the real aircraft. Also, I still think that arc is exagerated - see attached picture, I only made left/right movements ;) I guess if the movement was following the radar's symbology (display arc centering and angle) it would be quite alright. Edited December 27, 2015 by PiedDroit
IvanK Posted December 27, 2015 Posted December 27, 2015 (edited) Some have clearly got the TDC to slew ok. In my case I cannot slew it Down as the K is red in the settings screen. Reassigning a command doesnt work either. Neither does trying to bind it as a Direct X button. So is there a work around to get the TDC slew down working ? Edited December 27, 2015 by IvanK
PiedDroit Posted December 27, 2015 Posted December 27, 2015 Some have clearly got the TDC to slew ok. In my case I cannot slew it Down as the K is red in the settings screen. Reassigning a command doesnt work either. Noether does trying to bind it as a Direct X button. So is there a work around to get the TDC slew down working ?Don't know, I never had any issues with K, it worked right away. I'd suggest clearing your assignments and start from scratch (delete Saved Games\DCS.openbeta\Config\Input\M-2000C).
Zeus67 Posted December 27, 2015 Posted December 27, 2015 I know that (polar coordinates, etc), but it feels awkward to use (if the target is below and left, I will naturally move the piper down and left). I'm just wondering how's the piper movement in the real aircraft. Also, I still think that arc is exagerated - see attached picture, I only made left/right movements ;) I guess if the movement was following the radar's symbology (display arc centering and angle) it would be quite alright. Everything is perfectible. :book: I'll check and make corrections (in due time though, remember that I must prioritize). :smartass: "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." "The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."
Rlaxoxo Posted December 27, 2015 Posted December 27, 2015 (edited) Everything is perfectible. :book: I'll check and make corrections (in due time though, remember that I must prioritize). :smartass: Radar TDC controls may be little slow when going left and right but i think I can live with it for now. What's bugging me the most is that I can't use Throttle up/down on the keyboard I wouild solve this my self I knew how but I'm afraid I don't have the necessary knowledge yet = ( Pls make it high priority. And on a side note If you don't mind answering a question ... I know it might be little iffy but when can we expect to see some of these fixes roll in? After new years or sooner/later or are you guys already hard at work? Edited December 27, 2015 by Rlaxoxo [sIGPIC][/sIGPIC] Youtube Reddit
IvanK Posted December 27, 2015 Posted December 27, 2015 Don't know, I never had any issues with K, it worked right away. I'd suggest clearing your assignments and start from scratch (delete Saved Games\DCS.openbeta\Config\Input\M-2000C). Tried that to no avail. HOTAS TDC DOWN K is Red and inoperable.
Flagrum Posted December 27, 2015 Posted December 27, 2015 Radar TDC controls may be little slow when going left and right ... +1 It seems that the duration of a full left-to-right movement is the same, no matter if the cursor is at the top of the screen or lower. Although the length of the arc at the top of the screen is far greater than at the bottom, the cursor takes always the same amount of time to move along the whole arc. This results in an ok...ish absolute speed at the top and a slow moving cursor at the bottom. No idea how it is in the real thing, but it is at least ... a bit awkward.
Zeus67 Posted December 27, 2015 Posted December 27, 2015 Radar TDC controls may be little slow when going left and right but i think I can live with it for now. What's bugging me the most is that I can't use Throttle up/down on the keyboard I wouild solve this my self I knew how but I'm afraid I don't have the necessary knowledge yet = ( Pls make it high priority. And on a side note If you don't mind answering a question ... I know it might little iffy but when can we expect to see some of these fixes roll in? After new years or sooner/later or are you guys already hard at work? Some have been fixed but need testing, but you won't see any update before New Year day. We'll tell you when they are ready for the hotfix. "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." "The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."
Flagrum Posted December 27, 2015 Posted December 27, 2015 (edited) If you want the TDC to be above the target, then yes. If it moves in x/y, you can place the TDC above the icon, but it won't be above the target because the target does move in an arc as well. Disclaimer: I have no idea how this works in the real aircraft. ... but! From a usability perspective, I would say, the behaviour is wrong. I am not steering the radar beam or anything that is actually directly tied to how the radar physics is working. Instead I am steering a computer cursor on a (rectangular) computer screen. And as such, I would expect it to move accordingly, i.e. horizontally and vertically, but not on an arced path. edit: Or to put it differently: the display modes should not alter the behaviour of the cursor. The different display modes are there to enhance the situal awareness - where an cursor that moves on an arc does not add anything to it. Edited December 27, 2015 by Flagrum
PiedDroit Posted December 27, 2015 Posted December 27, 2015 (edited) Tried that to no avail. HOTAS TDC DOWN K is Red and inoperable. It seems that some bindings that belong to base_keyboard_bindings,lua or common_keyboard_bindings.lua that also appear in M-2000C's keyboard default.lua do not work (maybe all). I had the same kind of issue with the Magic II Select (which was previously 'M') and solved the problem by remapping it to RCtrl+'M'. 'M' for mirrors is still red in controls though (and doesn't seem to work). You can try to remap TDC Down (HOTAS category) 'K' to something else (leave the Kneeboard key as is), for example R_SHIFT+'i'. If that doesn't work, run a repair (in case your base config files got damaged) and delete \Saved Games\DCS.openbeta\Config\Input\M-2000C\keyboard\Keyboard.diff.lua If still nothing, I'm pretty much out of ideas. Maybe removing the 'K' binding from the common files would solve the issue but that would impact all other aircraft. Edited December 28, 2015 by PiedDroit
SageOT Posted December 27, 2015 Posted December 27, 2015 Just want to +1 again for the X/Y axis for the TDC. If you guys could see fit to include that in one of the near updates I am sure a lot of us with a mouse toggle on our throttles would be eternally grateful! Thanks Razbam, having a blast with this module. VFA-25 Fist of the Fleet[sIGPIC][/sIGPIC] Virtual Carrier Strike Group One | Discord
Neon67 Posted December 28, 2015 Posted December 28, 2015 Is the police light implemented yet ? or is it considered as a bug at the moment ? Because I don't see anything when turning it on
BaD CrC Posted December 28, 2015 Posted December 28, 2015 Police light? You mean the anticollision light? https://www.blacksharkden.com http://discord.gg/blacksharkden
grabby Posted December 28, 2015 Posted December 28, 2015 No i suppose is a light mounted on the left wing to identify the aicraft in the interception mission
Neon67 Posted December 28, 2015 Posted December 28, 2015 No i suppose is a light mounted on the left wing to identify the aicraft in the interception mission Exactly
fixen Posted December 28, 2015 Posted December 28, 2015 I think the police light is yet to be implemented.
AJaromir Posted December 28, 2015 Posted December 28, 2015 You can try that. There are to swithes. 1st one is on the left lights panel and 2nd is on the throttle stick.
Azrayen Posted December 28, 2015 Posted December 28, 2015 Yeah, basically: 1/ you "enable" the police light with the switch on the left console 2/ then you use the "palette" (trigger?) left of the throttle to light it. I didn't test if this is implemented yet.
Fishbed-21 Posted December 30, 2015 Posted December 30, 2015 Yeah, basically: 1/ you "enable" the police light with the switch on the left console 2/ then you use the "palette" (trigger?) left of the throttle to light it. I didn't test if this is implemented yet. There ins't the key on the throttle to light it up. Pain is weakness leaving your body... My Hangar: [sIGPIC][/sIGPIC] - CPU: Intel Core i9-9900KF @ 3.60GHz to 5.00GHz - MB: ASUS ROG MAXIMUS XI HERO Z390 - GPU: ASUS STRIX RTX 2080 SUPER OC 8GB - RAM: Corsair Vengeance LPX 32GB (8GB x4) - Storage: 1TB SSD Samsung 860 EVO 1TB - OS: Windows 10 Pro - PSU: ASUS ROG THOR 850W - Monitor: ASUS ROG XG248Q - Case: ASUS ROG HELIOS - Mouse: ASUS ROG CHAKRAM - Keyboard: ASUS ROG STRIX FLARE - Headset ASUS ROG DELTA - Thrustmaster HOTAS Warthog SN #95039
Azrayen Posted December 30, 2015 Posted December 30, 2015 OK, well I guess it will be added later, then :)
BravoYankee4 Posted December 30, 2015 Posted December 30, 2015 No i suppose is a light mounted on the left wing to identify the aicraft in the interception mission Any pics or films that shows this in action?
Recommended Posts