Red Dog

Didn't even have to make a repair update. Simply changing from FR to UK in said file and simply restarting DCS did change the language to english for me (DCS stable 2.5.5, no beta) That's good because honestly some of the key definition in french (probably badly translated) were confusing as hell and it made creating a HOTAS file really complicated.

Hello Gents, Apologies for the seemingly stupid question. Not sure it's supposed to be posted here or straight in the cockpit section, but feel free to move accordingly. I'm banging my head on a wall on something probably very stupid but this is driving me crazy I'm changing key assignation for the F/A 18 hornet sim (stable DCS 2.5.5) and what I see working in the UI (option/control) does not work in 3D once i'm in the cockpit. The reason I am not going with the default keys is that I have a cockpit and I'd rather not change the programming of the cockpit, but rather keep that exclusive and adapt the keystrokes of the simulators I may use. It sound complicated but somehow unrelated to the issue I face trying to assign keys to DCS, read on: For instance, I assigned "LCTL LALT y" for Arresting Hook Handle - Down and "LCTL LALT t" for Arresting Hook Handle - Up When I test my cockpit hook switch when I'm in the UI option screen, I can see the line jumping correctly to the hook up and hook down line. So in effect, the key change worked and my switch seems configured correctly. When I return to the 3D hornet cockpit, and place the hook switch down: Nothing happens - hook stays up. If I press "LCTL LALT y" with the keyboard, same thing: the hook doesn't go down. That's a major mismatch with what I set earlier in the UI. Obviously, if I click the 3D hook with the mouse, the hook comes down but the idea i!s specifically to avoid using the mouse in the cockpit. With the hook down, if I move my physical cockpit hook switch to it's UP position, the hook comes UP. So hook down, although programmed correctly doesn't work, whereas hook up, programmed in the same manner does work. Any idea what I am doing wrong? Many thanks fo rany help you may provide

Thank you very much for that pointer, Thanks to these Lua files in the package I could adapt mines and I now have the UFC and IFIE as viewports declared and working great Many thanks

Bear with me, I'm new with DCS F/A-18 but not quite with cockpit building. I'm trying myself at carrier ops with DCS and I want to export the MFDs and some more stuff from the pit to a secondary screen. At this point, exporting the Left_MFCD, Right_MFCD and Center_MFCD wasn't a problem thanks to previous search on the forum and the multi monitor topic in the DCS A-10 forum. So this work already. What I couldn't get to work was how to declare viewports for instance like the UFC or the EFIE or some analogue gauges I couldn't find a list of terms not using dedicated viewports name in the LUA Editing from the Cockpit/scripts folder) The only three seeming to work are the 3 listed above (MFCDs) is there such a list or do we have to manually declare these alternate viewports (for UFC and IFEI for instance)? All the references I could find about this are dated back from 2011 and specific to the DCS A-10 and for starters to file folder structure has changed. I can easily find back the relevant files in the new structure but I Wonder if the coding of the LUA files linked there are still valid? https://forums.eagle.ru/showthread.php?t=70716 Since all that is pretty old, I'm wondering if I'm not missing some topics about doing the same for other newer aircrfat modules? or if there is a GUI to perform these exports easier than messing the LUA files? Sorry if the question has been asked before. I have ben looking different forum but wasn't able to get a relevant topic about it. Bear with me if it was explained somewhere I couldn't find and i'd appreciate some pointer to these topics. Many thanks for any help provided

Signing in for interest. I salute the initiative as I went through the 90 pages with awe. I have been personnally involved with the Cougar and the Warthog development and testing, not within TM but just outside as adviser and avid tester. Been fighting some TM flaws since day one but that's another story. I have been providing the community with spare parts for Cougar for ages since then. During all that time I have been wishing third party grips to be done and I hope to see you succeed in your venture Hegykc. I'll definitely buy extra grips whenever they become available. Looking forward to it

i'm also a bit surprised that i can't update my Black shark 1 to DCS. After all i bought DCS A-10C before BS and i was able to install A-10C very easily in DCS 1.5 & 2. I always have been a user of Flanker 1, 1.5 then 2, then flaming cliff and A-10 and Black shark. All were bought as soon as they were released (some even before release as beta) and except for black shark all were used to some extend. My sim experience shifted to other series but i always came back a bit to DCS for a welcome change, concentrating mainly on the A-10 and Su25T. Nowadays with the Nevada release i'm drawn back to DCS and installed 2.0 alpha, and consider my options to port my previously bought software to DCS. A-10C was installed without issue but DCS balckshard (v1) seems impossible for me to port to DCS. Maybe I 'm guilty to have missed the opportunity to update in time as i was busy with other sims. But I fail to understand why a Customer is different from another one in that aspect. It's a little bit of a shame that returning Customer aren't granted the same update conditions that other Customer. ED should have thought better about it in my humble opinion. because one of the possible consequence is that returning Customer may not stay long when they realize they have to buy the software twice .... Anyway, that's how ED decided to proceed and although i don't necessarily agree, the decision is theirs

I have the same project, but the idea is to go front panel only so I can move this one to LAN whenever needed :) Anyway, I already know that I will work with a TFT to implement gauges on the front panel. I started creating A10 gauges for Flaming cliff a while ago with gauge composer. Don't mind the ADi and VVI, they were done to match my current instrument bezels, it's a WIP anyway

Thanks Acedy, and yep i'm the one, i'll start working on checklists the minute I get BS. It's my way of mastering a new complicated sim, and from what I read, BS is really for the avionics freaks isn't it :) Sorry for the hijack TriggerHappy, just wanted to say how much I love your work

Hello TriggerHappy Just wanted to salute your work from one pitbuilder to another :thumbup: Well done and keep at it I should get Blackshark any day now (waiting for the boxed release) ... Cheers Red Dog