Red Dog

Happy to report that it does work André. I have more subtle reaction than I had with DCS running straight from Aviator. But I get G forces, gear, speedbrake and stall. I don't get guns and payload discharge But I'll play some more with the settings. Many thanks for pointing it out to what I did not see I do have the software saying that it's working in Demo mode though. I updated to latest version last week and reactivated the software but the tab advanced options and registration still shows the button activate soffware and the top of the windows report Version 2.17 Unregistred, working in DEMO mode.

indeed a very good point Andre. I'll try and report back

i'm confused now Andre? is Wing compatible with DCS? I though aviator was supporting DCS and Wings was supporting others (like BMS) You mean what happens if I use Wings with BMS or are you telling me I should try wings with DCS?

Hello André Yes Sorry, always been confused with these two Aviator indeed Thanks

Hello gents, I got a compatibility issue I can't get my nose around to fix on my own and I seek help. My cockpit use Simshaker Wings for DCS and another app named DCSto F4 which is a great app allowing me to make my cockpit completely working with the DCS F-16 through the F4 BMS shared memory. Don't ask Basically my pit has been designed for BMS use but now flies DCS. That app allows my pit to run perfectly with DCS as well with no further programming. The problem is that depending on the order of the declaration in the DCS export.lua file, I either get Simshaker to work or DCSto F4 to work. I can't have both working at the same time If I declare Simshaker first, it does not work If I declare DCStoF4 first in the export.lua file, then DCSto F4 does not work. The team responsible for the DCStoF4 app is aware of the problem but I wanted to see if you guys had any idea what i can do to get both of the useful app in my pit working at the same time? attached current export. lua where DcstoF4 works but shimshaker does not Thanks for your time, any help appreciated Export.lua

Is there a way for the user to change that "CTL SHF D" combo in settings somewhere? It conflicts with one of my pit keystroke and once that window is open I can't move it and cannot close it Many Thanks for the app it's a great asset

Your're everywhere helping us poor guys and I want to say thank you. I spent a great deal reading this: and this: but I didn't encounter the one you linked above. More reading and I thank you for that

Hello gents, I'm a f-16 regular flyer but I welcome a change from time to time and lately was attracted to the A-10C I am thus reconfiguring my environment to the A-10 and the usual first step for that is setting up keybinds and analog axis. I'd like to kindly request some full state position binds alongside the usual toggles. I understand toggle might work for most users but many of us (more and more) build custom button boxes or even cockpit and having both toggles and all state switch position ensures both type of guys can have all they want. Please understand I am not requesting the replacement of thge toggles, but indeed adding All states alongside the toggles. I understand there is a way for users to create their own bindings in the .lua files but 1. I forget how to and I am currently looking at how to do it to avoid having to wait for the next update that may or may not address this situation 2. I am under the impression (I may be wrong) that each update might actually delete the custom added key lines from the .lua files and I just hate redoing all this after each update. Please If I am wrong or if there is a way to keep these adds persistent, please do let me know. 1. Canopy is currently exclusively a toggle in the A-10CII keybinding Although the real switch is a ON-OFF-MOM with MOM on canopy close (just like the F-16 btw) So I'd like to request a bind for Canopy Motor OPEN, canopy motor STOP and canopy Canopy motor CLOSE (MOM) 2. Seat ARM is currently exclusively a toggle in the A-10CII keybinding We could use a two position keybinds: SEAT ARM and SEAT SAFE alongside the current toggle 3. AAR DOOR is currently exclusively a toggle in the A-10CII keybinding and not quite obvious to find for that matter Air refuel control it's called. We could use a two position keybinds: AAR DOOR OPEN and AAR Door close 4. The CMSP switches are also exclusively toggle in the A-10CII keybinding We could use two position keybinds like RWR ON & RWR OFF, JAMMER ON and JAMMER OFF, MWS ON & MWV OFF alongside the current toggles 5. I have seen other discussions about this but FLAPS are very hard to setup with you own button box Indeed the keyboard can only be used for Flaps down and flaps up but FLAPS are 3 positions switch: Flaps UP, Flaps 1 (or TO) and Flaps 2 (or LDG) Having a full state (FLAPS UP, FLAPS middle, FLAPS FULL or whatever you call it) could be much easier to setup than the current increment way which is not possible to setup with a regular three position switch. Some will certainly say that there is the special for joystick which mimicks the warthog throttle behaviour but these cannot be assigned to keyboard (unless I am mistaken) and not all of us fly with a warthog throttle. Again, if there's a way to assign the special joystick binds to a button box switch, please let me know. I am pretty sure there are others (analogue axis anyone) which I will find later on as I progress with my setup. And I will list them here hoping for these binds to be added at some points Many thanks for your input and guidance in the meantime

very useful info, thanks gents I finally put some orders in these icons

Apologies, I said reprogram but I meant switch the programmin. hence download into the HOTAS Points remain, you have to manage your stick whenever you switch airplane in DCS They all have gears and flaps don't they? That's my point. I never said it had to be 100% Actually not if you consider the whole thing as a keystroke management To be honest I didn't expect anyone to understand unless they face the same challenges I do. it was just a question to see if there was a better way to manage than what i am actually doing. It seems there is not, so I have my answer Thank you for taking the time to answer

I understand that argument when you don't have many to do But consider three points : 1. HOTAS - 3 modules: F-16, A-10 and F-18 Would you prefer to program your HOTAS each time you switch airplane, or would you prefer trying to have 1 stick file for 3? Hotas are most of the time the same function, A-10 and F-16 for instance shares more feature than the ones that differs: TMS (4) DMS (4) CMS (4) trim (4) etc etc 2. There are more and more users with cockpit of some sort. We have to program something around 280 switch state for each module we fly. If only 25% of these are common, that saves A LOT of time and makes the process much easier. Again many functions are similar or identical - they just have different names. MFD buttons (28 per MFD) - 3 MFDs in average = 84 functions ICP = UFC = F-18 UFCI= ... Many functions are again similar Gear - flaps - speedbrakes - trims - etc - Many functions are the same but organized differently and with different names.... 3. When you have multiple joystick devices connected with DX buttons, like Cougar, Leobodnar, ... By default DCS assigns to ALL the same DX function per BTN (BTN 1 = VIEW UP) for Cougar and for Leo Bodnar device 1 and for LeoBodnar device 2, ...) So the first thing you actually need to do when you setup for the first time a module is to actually delete these redundancies because you do not want all BTN 1 of all your devices to emulate VIEW UP (for this example) That's unnecessary hassle and IMHO default could be set much more efficiently I understand I probably have a vision different than most of DCS users. I am not trying to match my cockpit/HOTAS programming to DCS module but I am doing the opposite: That is match all common features from one module to another module (like having DMS up for the A-10 the same as DMS up for the F-16. And to make DCS keystrokes match my cockpit programming. That actually ensures I do not have to reprogram my cockpit or my HOTAS each time I want to fly the F-16, the A-10 or even the F-18. It is much more work before flying, but much less hassle when using DCS. and doing so I must say I found the DCS keystroke management not quite user friendly when considering all of the above I know automation will not happen - but better management in the idea of being more user friendly should be something profitable for many DCS users IMHO

is there a way to partially (reads at least common feature) match the controls input from one module to another one? Let's say I matched all key input from my F-16 cockpit to the F-16 modules but I sometimes fly the A-10CII and many controls are the same. Is there a quick way to have a maximum of entries to be taken from the F-16 list and applied to the A-10CII list? Currently i have to go through each an everyone of them individually in the control UI section which takes a lot of time. But gear down is always gear down and it might be automated. I understand specific entries can't really be automated but is there a way to classify the common entries and at least have these match? Is there another way to do it straight from editing the lua files? How do you guys manage this - Is the hard way the only way? Thanks

Hey Tiffy, Nope I got one. Thanks mate But now I'm looking for another rudder Simpeds or Slaw. How's life been to you mate?

bump, still looking

I understand this is not only for the F-16 but may benefit other modules as well (F-18, A-10, ...), but since this request originates from F-16 cockpit builder I posted it here, feel free to move it if it is not 100% the best place. We would like to request data from the RWR and EHSI to be extracted with other means than as external screen only. Extra screen extraction is easy but in some cases (think guys having real instruments or other replicas) it is not always the most efficient manner To make a physical instrument work, we need hard data from specific parts of these instrument, it would be great if we could get these data for the RWR and HSI. Unless I am mistaken, even Helios reverts to screen use for these twos. Thanks

Found my issue: Removed Military Aircraft Mod (MAM) 1.7 and DCS started Just in case that helps some other ppl

Just updated to the latest patch and the minute after DCS doesn't start, it just vanishes after the DCS logo screen Logs says 2022-05-06 06:09:39.994 ALERT Dispatcher: Error running db_scan: ?:0: attempt to concatenate field 'CLSID' (a nil value) 2022-05-06 06:09:39.994 INFO APP: application shutdown

Merci sorry I so missed the obvious. It's already something indeed, but it remains tedious to rotate the new item to fit the local terrain Something like the ability to create custom "object templates" would be great But that will do for now

Hello All, Is there a way to create/replace the default map images with custom ones? Or are these hardcoded? Thanks

I am trying to group a series of static objects (training range) to create an item that can be placed multiple times on the map - at different location So I placed a dozen static and wanted to create a template out of it, just like the SAM templates available. But only 1 static creates the template I'm saving which kinda negates what I'm trying to do I can select all statics at once, but I can't duplicate them, move them or save them. Is there a way that eludes me to do that? I'm aware of the whole map templates - and I use that - but this is not working as I want the same objects to be placed multiple times on the map at different location. Creating my first objects took a while because I took long time to finely align statics objects with one another at specific distances. The purpose obviously is to avoid going through the same process to place the same type of grouped static at another location on the map - especially since rotating it to suitable heading makes the aligning even more tedious Thanks for any hints you may provide

Hello Eduardo, Are these templates still working with the latest DCS? Trying to download the required third party, I realised some of them are unavailable? many thanks for your input

3:30 F/A-18C doing ILS approaches at LAX Yes they are canadians, not US navy.

Are you using multi monitor configuration? If yes, there is a possibility that the kneepad is displayed at some weird place invisible to you (ask me how I know) When that happens you either have to drag the kneeboard where you want it, or maybe try to fix the issue all together by defining a set of viewports specific for the kneeboard? I haven't done the last thing so I don't know if that will help at all, but I intend to try soon.

Need to separate my rudder from my cougar connection. Looking to buy a RUSBA If you have one that you don't use, contact me. Am in Belgium and can do paypal Thanks for looking

I'm bumping this request as I really would like to add another vote for this to be changed. ILS IMHO should stay on whatever the conditions in DCS. They should not be turned OFF according to active runway, and they should not be turned OFF according to weather or any other factor for that matter The situation at this time is really chaotic and it is very hard to create missions for training purposes (or other purpose for that matter). 1. considering the ATC in DCS is almost nonexistent, there's no reason to try on a runway which is the active one - especially when the winds are wrong for the active one. 2. The way the wind is set in the mission editor is confusing as hell and may make the active runway choice complicated. 3. Sometimes you really need to have bad weather or strong winds to have the ILS turned ON so you can fulfill your goal. 4. When training -at least the first time - you might want to train in ideal conditions before trying in the soup. All the above make the ILS in DCS highly unstable and it is not rare to need a week of hard work just to create a mission where the ILS is ON - I'm past a week trying and I couldn't make it happen yet. Either we need to know the exact conditions for the ILS to be active or the situation may be much more fluid if the ILS are ON at all times, whatever the conditions. Thanks for considering this request