RodentMaster

To eliminate variables that it might be, regarding DCS and its (at the time) recent patch update.

I don't like the instant action generator. Seriously, it gives me nothing of the functionality I used to love. I could create a new mission, go to advanced, choose time of day, season, levels of enemy activity, but most importantly, I can pick and airfield, a plane, say I want to start on the ramp. I can set up my own training missions. I can set up a no-enemy free-fly. The full mission editor is woefully annoying to use, horrific to actually use and clunky AF to even try placing a player aircraft at a field you want to spawn at. Having the easy mission creator screen was a god-send that really made learning new modules so much better for me. Learning new, or just enjoying old ones. Fine-tuning control mapping changes and ergonomic changes I make to see what's better for flying, I enjoyed the old editor way better. Is it still available? I don't think I saw it. I'm not saying get rid of the instant action generator, just don't remove a very appreciated tool and replace it with one that gives me none of the things I need.

When Windows Defender nixes a file (and it has happened before) you get a log, a list of quarantined files, a history of what it did. I've dug into it. That did not happen here. Rather, and this is also not the first time it has happened, ED released a launcher/updater version that screwed something up as it updated itself. Repair, update, and file check, all within the updater version itself that ED just updated, failed to catch this, but "install" on one specific tab worked. Note that the AV did not stop the workaround. Note that AV does not have any logs, quarantined files noted, nothing. As I said, I jumped through every hoop I could. This was not AV related. I know it's an easy scapegoat, but I hate when people keep blaming the AV when the first thing everybody does is make sure the AV wasn't the problem, and then ask for help.

I'm not wrong on my assessments, and not on my machine. I went through all the hoops. I tested everything. I opened up every DCS executable and major folder in my firewall and added defender exceptions to those folders. Nothing was impacted by any AV/Firewall. I was not wrong. I never said it wasn't SOME peoples' issue. EDIT: Also see my workaround. It had nothing to do with firewall or AV. EDIT2: Oh, I'm sorry. I thought I quoted you on it. I neglected to. Here's the link:

Did any of you solve it? I stumbled across the stupidest most-desperate attempt at problem solving my way around it. Logic be damned, it worked. My fear was that I was going to have try some kind of backup-less redownload of hundreds of gigs of files all over again and lose all my custom skins and missions and settings and control mappings. So I went into the game, cleared the error, and went to the module manager (top left of screen, 9 squares in a grid icon). I went to the "installed" tab and was dreading trying to uncheck and uninstall one, and then reinstall. I know the launcher is worth f*** all and I don't trust it at this point so I'm looking for a solution in-game. When stumbling around, I noticed the specials page. I had one already. Instead of "buy" next to the price, it had "install". I went to the middle tab, "Modules" (NOT the "installed" tab) and saw to my surprise all my many many modules that I owned were all marked as owned. It knew I had them. I clicked "install" on one of them as a test. A smaller one in case I had to download it all. It started, and since all the files were there, it skipped downloading and went right to reviewing the files there for any missing files, and when it was done that module was available for use. I confirmed this by exiting and restarting the game, and noticed the module I did that to was NO LONGER ON THE ERROR LIST!!!! So the patch, the installer, the install checker, the cleaner, even the game itself under installed modules, every part of it has a broken link to which flight modules you own, that reinstalling from the module page re-connects. Here's the bad news: Start game, wait for load, clear error, go to module manager, go to modules tab, find the next one, click install, it pops up an error, saying the updater will be used, waiting for that to clear, finally closing, and doing it all over again for every... single... module... took over an hour. I have a lot of modules and it's a slow-ass procedure. It worked, though. Before I couldn't even enter a mission because it said I didn't have that plane, and after it let me. Give it a try. I hope it works for you. Shame on ED for severing whatever registered link was in there between the installed modules and the version update.

Nope. I can assure you it is not the AV, because it worked fine through windows defender and the firewall before the update, and the same executables afterwards gave errors. Remember, it's not crashing. It's RUNNING. It just doesn't let me have my modules. If it was firewall or quarantine related it would be manifesting other problems and they would have come out before this update. I may have found the solution but not the cause. Will reply to another post with it.

Installed latest patch, but still has not resolved the error every time that wants to disable every flight module I have because the Authentication Failed box pops up.

I have this problem, and it updated with a new patch, but the problem persists.

I'm having the same problem. Standalone ED launcher. Updated, and it killed all auth on flight modules. Went through every firewall and windows defender loop I could, and still won't recognize my aircraft modules. I have a feeling a lot of people are seeing this.

hawkeye those are interesting. They aren't the M but they have the type of HUD that Caldero had a picture of in that diagram. Must be a different model than the EE. Very cool. Caldero, there's a short bit where the F1 is making a dive attack on a car on the road and has some kind of rising bar that locks (or the pilot pickles the weapons when it passes) the target. Does that match something you've seen so far? That's much more advanced that I was thinking it would be. All the better!

A thought entered my head. I was seeing somebody discussing the HUD of the F-1CE and how it doesn't show "level" but that's not what it was designed to do. Other planes of that era, like the F-14, had similar HUD ladders and limited symbology. However, this made me think about something. In the preview we saw a non-textured picture of the F-1M cockpit with glass MFDs and a definite improvement in modernity. So... When did Mirage move to the more modern symbology of the F-2000? It's much more modern and I think it has the modern symbology including level HUD and hash marks. That was in the late '80s, right? So the F-1M was in the late 80s also, right? So was there an update to the HUD symbology of the F-1M along the way? We don't see that in the F-1EE, but it predates the F-1M. I tried googling it but found precious little on this topic. I'm curious if anybody in here knows more about it. Would it more closely match the early era HUD ladder and symbology, or would it match what we consider the standard "now" and have something more similar to the F-2000 and western air forces?

Thanks. I took up the offer!

Funny you say that... I really like the idea of the F1M but I find more and more I love the simplicity of the F1CE. I wish it was more capable, but as it is it's a nice fun platform to fly. I don't have to worry about TADS screens or SADL info. It's very old-school. Push a button, fire a weapon. Don't get me wrong I love the digital screens on the F-16 and A-10C, but the F-1CE is like a guilty pleasure. I don't have to wait for INS warmup for 10 minutes like some planes. Okay, I do miss a moving mission map. That's just an awesome SA tool, but it's still cool.

You can turn the axis into a band or something where the top 1/3 is "radar elevation up" and the center is unmapped, and the bottom 1/3 is "radar elevation down" or so. My winwing allows me to toggle an axis to a slider directly and I just map the new buttons to what I want. I don't really like how the F1 radar is mapped out. It's a little clunky because I think they're trying to recreate the original mechanics rather than focusing on ease of use.

Normally I might agree, but for the past few month after a move for work, I have been without my HOTAS and chair mount setups. All I have is mouse and keyboard. I have hte F4 (only one I ever preordered) but I can't even fly it yet. Le sigh.

Not even a post or reply in 4 months. No updates in even longer. I'm kind of giving up hope on this one. I know these things take time and can't be rushed, and I appreciate the size of the team but also recognize how much of their work has already been done. I need a little inspiration, or something to spark hope. Who's got any?

There is a minimum time before you can press a second button, and if you flip too fast to "mid" then on to "up" or "down", it will still be processing the "mid" and not work on "full".. You have to toggle back to mid then full again. It's a timing issue, built into the code. Not sure if it's a game engine (DCS) or a mod issue (Aerges). I wish it would just read the status of the switch, but it doesn't. It treats it like 3 buttons instead of a switch.

Still waiting on mine. Fingers crossed.

Master arm, safe, and train are on most of my modules. I have a 3-way switch on my throttle that is the master arm toggle. I can't use it in the Mirage F1 because there's a safety cap on the switch. I tried to use it "under" the cap but nothing registers until you open that cap. It's a very annoying thing when I'm trying to set up a VR HOTAS binding. Likewise, jettison and selective jettison do not work because they also have guards/caps on top of them. About a third of all they buttons or switches in this cockpit have some kind of flip up guard over them, and you must bind a toggle to that guard. It's highly inefficient from a gamer point of view. Is there a way to get this mapped so it works without needing to waste 2 buttons (open and close the cage) for all the covered buttons? Like the simplified gun trigger, and landing gear option?

Wow... I would NOT have made that connection. I'll give it a try!

The problem with any mod like the F-35 or F-22 is that the aircraft, their systems, and even the technological capabilities of it are all very top secret. Like, you go to jail for the rest of your life if you share it with anybody, top secret. So, anything this mod may have, anything at all, is pure speculation. Even if well-intentioned speculation, it will never be accurate. It is and will only ever be a "for fun" mod and will never approach the level of accurate modeling, systems integration, or combat capabilities of any other official mod in this game. Their nature is to spark imagination for a while, then burn out quickly. Thus is the life of a mod like this. Best to move on, nothing official will come of this plane for another 40 years, is my guess.

I did some searching and can't seem to find this anywhere... I've looked around, asked around, and I just can't seem to find it. You can click the wheel that increases or decreases the gunsight depression, with the mils counter changing along with your clicks... But you cannot seem to map this at all. I want to map it to a rotary switch like I have on the A-4E mod and some other planes. I don't think these bindings are included in the game. Can we add them please? Or enlighten me as to where I find them?

A couple of different mappings with modifiers. Maybe I should outline it in a bit more detail, but I'll try not to write a novel. So, looking at that image, we have hats 1,2,3,4. I have 3 modifier buttons that act as additional modes. 1 on my stick, 2 on my throttle quadrant. Stick default mode: Hat 1 = coolie Hat 2 = DMS Hat 3 = TMS Hat 4 = mouse clicks/scrolls Throttle Mode 7 ("Flight" in my mind) Hat 1 = trim Hat 2 = misc Hat 3 = NVG toggle, VR re-center Hat 4 = flaps up/down, gear toggle, wbrakes toggle Throttle Mode 9 ("Combat") Hat 1 = CMS Hat 2 = boat hat + misc Hat 3 = slew Hat 4 = airbrakes extend/retract and china hat fwd/aft The examples of problems: Airbrakes wouldn't respond. Even if I cleared the mapping, remapped it, they would not work. Even the keyboard mapping for it would not work. It nuked that entire command somehow. This is because the mouse mapping on the same buttons. However, in the controls setup page you can press the right combo (mode 9+hat4) and it would register the airbrakes being pressed and jump to that bind option, and highlight it. It would simply not work in-flight. China hat also would not work in either direction (mode 9+Hat 4 also). However, flaps worked fine (mode 7+Hat 4) as did gear and wbrake toggles. It was also inconsistent as to which mods it allowed and which it nuked. I tried remapping it in-game, but it was unremappable and would do the same thing (register in the mapping menu, jump to it, but never work in-flight and the key presses would not work). One by one I tried a million things until I unmapped the mouse button options in default mode. One by one as I cleared those, that direction of the Hat 4 started working in other modes as well. This took so long because 1) even when I cleared out all the other options, I still needed the mouse-click options and didn't realize they were part of the problem, and 2) when I cleared them out in an active game session, it was already too late and they were nuked. Only when I 100% wiped my config and started clear without even setting the mouse options in UI Layer settings, was I able to use the keyboard options to toggle those air brakes. It led to some very disruptive confusion. In the second example, NVG was causing problems. Hat 3 was set to TMS. Mod 9+Hat 3 was set to slew. Mod 7+Hat 3 was set to NVG and VR recenter. I didn't have problems with recenter that I can think of, but didn't use it too often. When I hit TMS up in default mode, it did not trigger as TMS up but rather toggled my NVG on. I could slew all directions no problem. I just couldn't TMS up or up long to set any kind of SPI, and couldn't use china aft/fwd to assign SPI either (as you can imagine that hobbles the A-10s abilities GREATLY). However, looking in the controls it mapped fine, and NVG were only toggling with Mod 7+Hat3 under the settings screen. For a while I thought it might be limited only to the UI layer commands, because I had a throttle button 11 in default mode mapped to "escape menu" and I tried mapping the Mod7+Button11 to "lower seat height" but it would stop working. I had Button 12 to "VR Zoom" (also a UI layer option) and it was Mode 7+Button12 mapped as "seat raise height" and this also didn't work. I thought they were considered in the same class as the mouse keys click/scroll as they were under the same menu, so I didn't single them out. Most recently I mapped a simple button my my CH throttle quadrant to "toggle gear" (I was forced to make a lot of difficult choices on how to remap my setup to avoid mapping modes on top of that Hat 4 mouse-click option) and this is why I posted my reply to my initial post. The gear was Button 3 default mode. Mod 7+Button3 was R Eng Start. I never had that many problems before this getting that one to work. Now I did all of a sudden. Mod9+Button3 was my kneeboard quick glance and it also stopped working. Nothing worked. Until I cleared out the default mode bind for toggle gear. Then Mod9 and Mod7 worked fine. It's a very complicated problem and I don't fully understand everything behind it, but it's all very directly tied to the key mapping in the controls setup.

There are two buttons for NVG BRT and DIM. Once goggles are active you can really dim it out and see the MFDs with no problem. I mapped them to a stick to play around a bit, and even in daylight with the goggles on, I could bottom out the dimmer option and still see my TADS. Not as easy to read as normal, but still made a world of difference. Try messing around with the brt/dim button on them. Default is about mid-range.

Follow-up and new conclusions: It's not specifically the mouse keys, though that may be part of it. It is the overall modifier behavior and unreliable behavior. If you read my previous post, I had to unbind all the mouse keys to get things to work that were modified mappings of those mouse keys. Well, in VR those mouse keys are vital, so I wound up moving the other modifer+ mappings to different key combos and leaving the mouse keys to be the ONLY mapping on that 4-way hat. That seemed to work. Mostly. I got my speed brakes back, I had to move flaps and some other items as well. As I'm at a premium of buttons and DCS A-10C II has an ungodly amount of things needed for it, I moved them to various places on the stick map I have drawn up. I moved "gear toggle" to a non-modified button on my throttle quadrant. I removed a couple of less-needed options from my map to make room. However, this same button when modified with throttle_but7 is my "right eng start" and no matter what I did I could not get this rt engine to start. It's really annoying. Also note when it screws up the command it screws up the KEYBOARD MAP AS WELL, so hitting the keyboard option was a no-go. It would not start my rt eng no matter what I did. I looked at the mapping in-game to see what other modified uses I had on this key. Only thing was the gear toggle. I removed that, hit OK, went back to my in-progress test-game, and what do you know? They rt eng started up just fine. I can also report that I cannot raise or lower my seat position because these are button7+ modified versions of my "act as ESC" and "VR Zoom" The crazy thing is that I have a modifier pinky switch on my stick for view-related things and when I hit it for spyglass zoom it's modifying the VR Zoom and that has no problems at all. Again, once it screws up my seat up/down mapping on those keys I can't even use keyboard shortcuts to toggle it up or down. I have to literally click the cockpit switch that allows me to do the same. Some things, however, have no clickable cockpit equivalent (like "start rt eng"). So I'm baffled as to how this system can be so screwed up with regards to modifiers. Some work fine, others won't work well at all. Once it won't work well, it salts the earth and takes away your keyboard option as well -- all while still showing under the controls settings screen and registering in there just fine, as if there is no problem at all. I have questions: Are there any known input mapping problems related to this? Are there a cap on modifiers? Is there a cap on how many different modifier-enhanced mappings you can put on a single button? (for example, button 1 mapped, modifier1+But1, modifier2+but1, modifier3+but1, etc) What are our limitations in this? Because from what I thought/saw, there were none. P.S. As a personal note: I swear, the god awful keybind mess that is DCS World never used to be this painful, and when they keep wiping your keybinds with updates, it's really driving me away from the game months at a time as I dread fighting the control mapping every time I try to get back into it. I'm not even combat capable right now with all the screwed up mapping, and flew one flight in an A10C II without boat or china hat switches. You have NO idea how impossible that would be without at least HMCS for TGP slave targetting. I can fly, mostly, but can't get any training done.