PiedDroit Posted July 8, 2015 Posted July 8, 2015 One possibility to mitigate the problem (of not having physical switches) is to create a snapview centered on the armament panel (or radar panel, etc), and map a joystick button to this snapview. In flight, while looking somewhere (e.g. a bogey), you could bring the snapview using the joystick button, click on the appropriate switch with the mouse (using the other hand) then go back to your normal view. The use of snapview should allow you not to lose sight. I don't know if it's workable, I'll try it tonight. Turns out it's VERY workable, I wrote a tutorial here: HOW TO: Use snapviews to easily manipulate the cockpit switches while keeping sight
Sokol1_br Posted July 9, 2015 Posted July 9, 2015 (edited) I find a good solution for turn Mig-21 Weapon Selector without "high end" HOTAS or specific hardware, using one 'stick button. Using the keymaper Xpadder, one HAT corner send the 1...9,0,- sequence. The problem with this is that after some flights/re-flighs you dont know what is the last position in Xpadder, so I insert the Caps Lock key after '5' and ' -', and so know that when the keyb' LED became ON the selector should be in the 1st position of AA sector, when became OFF are in the 1st position of AG sector. Work good. EDIT - More practical way - clockwise and counterclockwise - with 2 joy' button in Joy2Key: http://forums.eagle.ru/showthread.php?t=145398 Edited September 4, 2015 by Sokol1_br add info
GriffonBR Posted September 4, 2015 Author Posted September 4, 2015 Well, after many requests and bad reputations on my account... Replaced multiple existing inputs with toggle inputs. http://forums.eagle.ru/showthread.php?t=146655 Thank you Leatherneck team. And thank you to the other users that supported me if this matter.:thumbup: 1 Intel 8700K@4.7ghz(all cores) / 32Gb DDR4 /WD Black SN750 Heatsink 500gb (DCS Only) / MSI GeForce RTX 2070 GAMING Z 8G / Windows 10 PRO / VPC WarBRD Base + Warthog Stick + Foxx Mount / Thrustmaster TPR pedals / Thustmaster MFD / Thrustmaster Warthog throttle + Monstertech chair mount
Pizzicato Posted September 4, 2015 Posted September 4, 2015 Why "replaced" instead of "in addition to"? I hope this doesn't screw up things up for HOTAS programming. Toggles are a pain in the ass for getting horribly out of sync. :( i7-7700K @ 4.9Ghz | 16Gb DDR4 @ 3200Mhz | MSI Z270 Gaming M7 | MSI GeForce GTX 1080ti Gaming X | Win 10 Home | Thrustmaster Warthog | MFG Crosswind pedals | Oculus Rift S
Dudikoff Posted September 8, 2015 Posted September 8, 2015 I hope so, too. If anything, we need more keys (e.g. IIRC the Ka-50 has only toggles which are next to useless for my new switch panel), not less :) i386DX40@42 MHz w/i387 CP, 4 MB RAM (8*512 kB), Trident 8900C 1 MB w/16-bit RAMDAC ISA, Quantum 340 MB UDMA33, SB 16, DOS 6.22 w/QEMM + Win3.11CE, Quickshot 1btn 2axis, Numpad as hat. 2 FPH on a good day, 1 FPH avg. DISCLAIMER: My posts are still absolutely useless. Just finding excuses not to learn the F-14 (HB's Swansong?). Annoyed by my posts? Please consider donating. Once the target sum is reached, I'll be off to somewhere nice I promise not to post from. I'd buy that for a dollar!
Exorcet Posted September 10, 2015 Posted September 10, 2015 Why "replaced" instead of "in addition to"? I hope this doesn't screw up things up for HOTAS programming. Toggles are a pain in the ass for getting horribly out of sync. :( Yes, it would be a shame if the problem went from one group to another. Outside of technical limitations, I don't see why you'd remove an established and already functioning system. There should be as many options as possible ideally. Awaiting: DCS F-15C Win 10 i5-9600KF 4.6 GHz 64 GB RAM RTX2080Ti 11GB -- Win 7 64 i5-6600K 3.6 GHz 32 GB RAM GTX970 4GB -- A-10C, F-5E, Su-27, F-15C, F-14B, F-16C missions in User Files
Uther Posted September 20, 2015 Posted September 20, 2015 Replaced is rather worrying. I hope it is in addition to the existing system rather than just 'replaced'... i5 4690k / MSI Gaming 5 / 2 x 8 GB Crucial Ballistix ram / Zotac AMP! 980Ti / 2 x 250 SSDs Flight Controls:Virpil VPC MoogoosT-50 / MFG Crosswinds / GVL Throttle / Oculus Rift CV1
Krupi Posted September 21, 2015 Posted September 21, 2015 Yes this is of major concern to me too, it is unfair to forget about one group in favour of another I love the immersion that the current system gives me.. Please can we have some clarification!? Windows 10 Pro | ASUS RANGER VIII | i5 6600K @ 4.6GHz| MSI RTX 2060 SUPER | 32GB RAM | Corsair H100i | Corsair Carbide 540 | HP Reverb G2 | MFG crosswind Pedals | Custom Spitfire Cockpit Project IX Cockpit
streakeagle Posted September 29, 2015 Posted September 29, 2015 As long as I can manually create the button functionality I need, I don't mind the change. But if the ability to operate switches is limited to only toggles rather than matching the state of actual switches, this is a step backwards. Per above, I would much prefer the addition of toggle functionality for those that want or need it to replacing functionality that I am currently using with toggle inputs. If I can't operate the MiG-21 with the switch mapping I currently have, I will be greatly disappointed. [sIGPIC][/sIGPIC]
Pizzicato Posted September 30, 2015 Posted September 30, 2015 Can we get some clarification on this please, LN? Please tell us that you haven't removed the base functionality... i7-7700K @ 4.9Ghz | 16Gb DDR4 @ 3200Mhz | MSI Z270 Gaming M7 | MSI GeForce GTX 1080ti Gaming X | Win 10 Home | Thrustmaster Warthog | MFG Crosswind pedals | Oculus Rift S
FeistyLemur Posted September 30, 2015 Posted September 30, 2015 The lack of clarification or any comment at all is definitely nerve wracking, particularly as I'm having a 1/8 thick steel plate cnc cut for my authentic mig21 themed toggle panel this week. 1
Woots Posted October 25, 2015 Posted October 25, 2015 Don't like that some commands dont have the option to map to a joystick. [sIGPIC][/sIGPIC]
Nereid Posted November 3, 2015 Posted November 3, 2015 Don't like that some commands dont have the option to map to a joystick. Well.... buy a better joystick then. Any good HOTAS will give you the option to map keys or a combination of keypresses and releases in any order to any button of the stick or throttle. DCS:A-10C / DCS:Ka-50 / DCS:UH-1H / DCS:Mig21bis / DCS:P-51D / DCS:Mi-8MTV2 / DCS:Fw190D9 / DCS:Bf109K4 / DCS:C-101EB / DCS:L-39C / DCS:F-5E / DCS:Spitfire LF Mk. IX / DCS:AJS37
xaoslaad Posted November 3, 2015 Posted November 3, 2015 I'd for one love to see a weapon select increase/decrease in addition to the 1-0 and - keys. Mapping 11 buttons where two, or even one in a desperate pinch, could do the job is crazy. I have an encoder (works in the same way that this switch does - spins infinitely in either direction) that would be perfect for this function. To be clear I am not arguing that the other 11 should necessarily go away, but having an option to emulate what the left/right click does would be nice.
tintifaxl Posted November 3, 2015 Posted November 3, 2015 Well.... buy a better joystick then. Any good HOTAS will give you the option to map keys or a combination of keypresses and releases in any order to any button of the stick or throttle. I own a TM Warthog and can't use TARGET as it has it's issues with stuck CTRL-keys in DCS. Same with the Logitech profiler for my G940. So having the option to map any function within DCS to a joystick button is a must. Windows 10 64bit, Intel i9-9900@5Ghz, 32 Gig RAM, MSI RTX 3080 TI, 2 TB SSD, 43" 2160p@1440p monitor.
Sokol1_br Posted November 3, 2015 Posted November 3, 2015 (edited) Posted by Woots View Post Do not like that some commands dont have the option to map to a joystick. Well.... buy a better joystick then. Any good HOTAS will give you the option to map keys or a combination of keypresses and releases in any order to any button of the stick or throttle. Probable he is referring to Mig-21 flaps that in 1.5 came without option to map in joystick buttons - easy fixable editing the LUA file (are some topics about). Anyway is not need buy a "better joystick" to map keys combinations in joy' buttons, are good freeware/shareware (10$) keymappers around like Joy2Key, Xpadder, SVmapper... that to this for any joystick. :thumbup: Sample, Mig-21 weapon selector with 2 joy buttons (+Joy2key): http://forums.eagle.ru/showthread.php?t=145398 Edited November 3, 2015 by Sokol1_br
531-Ghost Posted November 5, 2015 Posted November 5, 2015 Using a combination of Control Manager (CH Products) and controller options in the game I'm having no issues using the following: FighterStick, ProThrottle, Throttle Quadrant and 2 MFPs as well a XKeys Pro USB. :joystick:
PiedDroit Posted November 5, 2015 Posted November 5, 2015 Using a combination of Control Manager (CH Products) and controller options in the game I'm having no issues using the following: FighterStick, ProThrottle, Throttle Quadrant and 2 MFPs as well a XKeys Pro USB. Same here, I'm using TARGET with only keyboard mappings, no issues at all. (Gear, flaps, IR/SAR switches are mapped on it).
WildBillKelsoe Posted November 9, 2015 Posted November 9, 2015 It is meant for cockpit or panel builders. I feel you but alot of people like to build panels and full cockpits. I think a toggle for all keys should be listed under Mig-21 Sim Limited. That way guys with limited controlling can still use it, and guys with panel building skills still use it. Sent from my SM-T231 using Tapatalk AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.
Johnny Dioxin Posted November 9, 2015 Posted November 9, 2015 To be honest I disagree somewhat. I found flying the plane a chore, and god help you if you don't have a full HOTAS. Then I made some autohotkey scripts and now I can fly it just as easily on a logitech Extreme 3D as my X52 pro and other systems. For me the extra controls just get in the way of actually using and employing the systems. Since then it's become one of my favourite and most flown modules. It's all well and good that the real plane has several actions to raise the landing gear and whatever else, but the differences in ergonomics and memorisation between a flip switch with 3 positions and being able to interact with it by hand instead of mouse, are already quite different and then having 3 separate keyboard commands when a toggle would be fine for many of them... doesn't really enhance the simulation or gameplay for me, it does just what you suggest it does - create more busywork. I have to agree with the original poster that the excessive separation of keybinds is rather annoying. Theoretically it should be beneficial for making a sim pit or the like - and certainly it made the autohotkey script a lot simpler because I don't need to care about what state things are in and just tell it to go directly to a position, but using them directly is a pain. Well said - I've been thinking (and sometimes saying) this since release. It's all very well rivet-counting, but a balance needs to be made to cater for the fact that it will be played on a desk PC. Another beef is having one key for lifting a switch cover, then another for flicking the switch. Fine if you want to do it within the cockpit with the virtual finger - but making two separate keys is going a step too far for me. I was on the original Indiegogo for this and was patiently waiting all that time for release with great anticipation - but I've flown it only once and struggle to find the motivation to fly it again - even though I want to - purely on account of the control assignments being a nightmare. Rig: Asus TUF GAMING B650-PLUS; Ryzen 7800X3D ; 64GB DDR5 5600; RTX 4080; VPC T50 CM2 HOTAS; Pimax Crystal Light I'm learning to fly - but I ain't got wings With my head in VR - it's the next best thing!
Dav IRL Posted November 18, 2015 Posted November 18, 2015 Well said - I've been thinking (and sometimes saying) this since release. It's all very well rivet-counting, but a balance needs to be made to cater for the fact that it will be played on a desk PC. Another beef is having one key for lifting a switch cover, then another for flicking the switch. Fine if you want to do it within the cockpit with the virtual finger - but making two separate keys is going a step too far for me. I was on the original Indiegogo for this and was patiently waiting all that time for release with great anticipation - but I've flown it only once and struggle to find the motivation to fly it again - even though I want to - purely on account of the control assignments being a nightmare. Agreed, I want to fly her but she is a chore without some toggle options. 4.8 I7, 1080, TMW&T, SSD, VKB MK.IV.
Sokol1_br Posted November 18, 2015 Posted November 18, 2015 If you want these "toggle" for map functions in joystick press buttons (eg. CH joysticks or 3in1 - no Warthog style toggle switches): A toggle function is use the same button twice for do the same thing, in FC 3 style: Ex. B10 = LG up, B10 = LG down. With little effort, you can do this with 1 joy button, just using a keymapper (HOTAS soft or 3rd part ones) like freeware Xpadder 5.3, mapping a paused sequence: The key assignment was changed without modifier (Alt, Ctrl...) to make easy see the sequence, is not needed. Press the joy button one time, the gear goes up, next time goes down. If you are using "air start", the first press do nothing. BTW - When they try mix "detailed simulation" and "videogame controls", the result can be very weird: This is correct done in Mig-15 and Ka-50, not to good in Mig-21 and weird in Fw 190 (better don't have this dumb and useless animation). :D
majapahit Posted November 18, 2015 Posted November 18, 2015 This not FC3 mode, at all! FC3 difference with DCS level is not about key bindings only, it's more about avionics simplification. And I believe that more people would be interested in the aircraft rather than the opposite, if the keyboard mapping were easier to remember. I think the request is not about making over-simplication here - that's what I understood so far, I may be wrong though. Things to be simplified are the switches that require to unlock stuff before (switch cover), and toggles. More like this: If you buy a Warthog HOTAS for 300+ euro you'll get programming software for free you can then implement programmable macro's in sequence (havent used it yet, time restraints) | VR goggles | Autopilot panel | Headtracker | TM HOTAS | G920 HOTAS | MS FFB 2 | Throttle Quadrants | 8600K | GTX 1080 | 64GB RAM| Win 10 x64 | Voicerecognition | 50" UHD TV monitor | 40" 1080p TV monitor | 2x 24" 1080p side monitors | 24" 1080p touchscreen |
Johnny Dioxin Posted November 18, 2015 Posted November 18, 2015 (havent used it yet, time restraints) ...and that sums it up perfectly! Not that it's a sensible statement in the first place - maybe you were making a joke? In any case, the discussion has turned, time to go. Rig: Asus TUF GAMING B650-PLUS; Ryzen 7800X3D ; 64GB DDR5 5600; RTX 4080; VPC T50 CM2 HOTAS; Pimax Crystal Light I'm learning to fly - but I ain't got wings With my head in VR - it's the next best thing!
Dafiew Posted January 30, 2016 Posted January 30, 2016 Hey guys I know people requested toggle bindings but why are some of the single bindings gone? Now when I want to operate nav lights with my MFD I have to look outside to see if they are on or off or med etc... :( Pretty annoying since I had a button for each state OFF/MIN/MED/MAX before any one knows if I can get the old system back? When i put my old default LUA in there I get a bunch of red commands :( Simflyin' since 1985 :smartass:
Recommended Posts