FeistyLemur

You don't say.

This is how I secured my pedals to the bare floor, and still how I secure them to the plate on my wheelstand. https://www.amazon.com/Command-Picture-Hanging-12-Strips-17204-12ES/dp/B00LW1APOC When you're pushing at the pedals from an angle the shearing force isn't enough to dislodge these velcro strips. And they easily tear off being velcro, and are easy to remove if you have to remove them completely.

Hmm, still no luck with the new profile. What I'd done to make it simpler was copy the Shooting Range mission, and I just deleted the predator so there's only Darkstar on the mission. Basically it appears to be stuck thinking it's at the inbound stage. As soon as I readback remarks JTAC says clear to engage. So I engage, kill the target, JTAC says target destroyed. I say copy kill, the menus flash but that's it. Then its stuck again. But... If I say IP inbound at this stage, it actually calls ready for nine line by hitting f4, f2. So that's where it thinks it's at in the flow. But there is no IP inbound stage for this type of JTAC, so im not sure what to do. Basically after readback, it's right at the stage where f2 calls target destroyed. So if you call ip inbound, it calls target destroyed. I had hoped the updated profile addressed exactly this by the notes but it appears it didn't. I downloaded that training mission linked and practiced with type 2 jtac with smoke. It works perfectly. It seems to be just the other kind I'm getting stuck with.

I had been doing that but it wasn't helping. I notice the a10 profile on the downloads page has been updated since the one I have for type 3 jtac. So maybe that's it. I've downloaded the newest one to try but was unsuccessful in the first attempt last night. Voice attack crashed and I gave up for the night. I seem to be having a lot of issues with unhandled exception crashes with the .12 version from the site. I thought I had it solved with the calling a profile from itself thing but apparently not. There continue to be random crashes and freezes. Some of the searching I've done on that has turned up threads linking unhandled exceptions to the joystick ptt, so my dreams of continuing to use that may be dashed.

I've been practicing with the JTAC flow in the A10. I seem to always get stuck on the same issue. I've been practicing with the default "shooting gallery" mission. I can get up there, call JTAC, do one successful run right to the letter as per the instructions. All the steps work along the way. Once the target's destroyed the JTAC calls in and says target destroyed. At this point this is where it gets stuck. It refuses to work without the brute force command force next. If I call "ready for 9 line" to get my next task I hear it beep successfully, then the menus flash and it makes it as far as the JTAC menu where I see the options. But I can't call commands properly at this stage. I have to force my way through the rest of the mission. It's as though it's one step behind where it should be and just not executing the command. I'm not sure what I'm doing wrong at this stage.

I've been waffling back and forth on getting a revolution for some time. But with the accessories and shipping it comes down to like 1800 dollars here. Decisions decisions.

You could call your modified setup the Obutto no-zone. I'll see myself out now... PS, you want to sell me that VKB.

It took me some time to figure out how the joystick binding works in it, but I got it updated and I like it. One thing I came across in .12 that didn't cause issues in .8 is I had my profile switching set up where calling the existing profile from itself just does the "load profile" feature and loads itself. That seems to cause unhanded exception errors at random. This was out of pure laziness mostly to make it easy to copy my load profile commands across all profiles and rather than switching it to _Menu_Initialize for the in profile call.

The sync is pretty much impossible to deal with unless the module supports a two or 3 way toggle with individual binds. At least I know no way of dealing with that via lua if for example there's a function like G for gear up G for gear down again with no option for separate binds in the modules default LUA. There was a whole kerfuffle with mig21 some months back when 1.5 first arrived where they decided to nix all the individual binds and put in toggle keys for everything which caused me a great deal of grief (and led to a great deal of protesting by me on their board to put the separate binds back).

This is my best invention relating to the wheelstand. I attached an old sling to my chair and ziptied it tight around the tension adjust so it stays up high and within reach. Then I just latch this carabiner over the main post adjuster to clip into it tight. This way the chair doesn't roll back when using the pedals. It's more comfortable to use, and convenient to hook up and unhook.

The way I ended up getting turned on to it was with Vaicom which required it at the time. I liked it so much I started using it for everything. Here's an example of how you set up a 3 way WH swtich (which is basically treated exactly the same as 2 ways but with a shared position for off when it detects the button being released.) ; --- HOTAS WH Throttle Buttion 13 3Joy13:: Send g SetTimer, WaitForButtonUp13, 10 return WaitForButtonUp13: if GetKeyState("3Joy13") return Send ^g SetTimer, WaitForButtonUp13, off return ; --- HOTAS WH Throttle Buttion 14 3Joy14:: Send +g SetTimer, WaitForButtonUp14, 10 return WaitForButtonUp14: if GetKeyState("3Joy14") return Send ^g SetTimer, WaitForButtonUp14, off return What that does for example is when i use the pinky switch up (button 13) it sends g, then waits for it to release. When it releases it sends ctrl g. Likewise button 14 (pinky switch down) it fires alt g and waits. Then when it detects release it fires ctrl g. This effectively binds the 3 position gear selector of the mig21 to the pinky switch on the throttle. Basically an auto hotkey script is a simple plaintext script file you can put on your desktop (eg Mig21.ahk). When you want to run it you double click, and that's it, it's running, and a little icon appears in the system tray. To stop it you right click and hit stop. The only negative traits are. 1: you have to remember to start it. 2: you should really remember to put all your switches in the off position before triggering a script, or else it spams a bunch of keypresses at once which can be annoying, and 3: there is a learning curve. 4: as always single press functions can become "out of sync" toggle keys such as press G for gear up press G for gear down again. But it's well worth it, and you can do very simple things like what I've done here up to extremely complex and powerful things. Very useful tool. I find it much simpler and convenient to use than something like TARGET. And TARGET I found was laggy and just a bitch to use. This is fast and very responsive. Once you have one file set up for all the keys on your warthog it becomes super trivial to make a script for a new module too. Because all you have to do is duplicate a script for your next module, and change the "send" lines appropriately for what you want it to do, comment out any buttons you may not want to rebind, rename it, and you're done. Unless they change the default bindings for the module, which seldom happens, you're permanently set for that module and never have to piss around with LUA again. At worst you might have to do a simple edit if for some reason they changed a base keybind.

Am I reading something wrong or is that article not completely inaccurate?

Why is it only the Russians are making awesome gimbals? I need to learn to speak Russian or something. I'm so sick of tearing this warthog apart, I need a cam based solution. That or to figure out a way to install grease zerks on it.

As far as updating goes, do you know if you can install voice attack overtop of itself in an upgrade fashion and have vaicom still work? Or is it pretty much install from scratch and re-import all the profiles.

This is my solution to mounting the crosswinds. Use the flat steel plate that comes with the wheelstand and use these. http://www.amazon.com/dp/B01KZWQOTS The nice thing is, being how filthy pedals get and how they require frequent vacuuming, you can rip them right off being these velcro strips easily detach when pulled upward, vacuum them and the plate, then put them back down. They're very solid and I never have any issues with them detaching while using the pedals.

So the newest version of Voice Attack is safe to use with Vaicom? I'm using 1.5.8 and I know at the time I got started the beta version 1.5.10 I think it was? didn't work right with it. I'm loathe to update something that's working. But direct joystick binds would be nice in this case, because then I could leave the default numpad keys alone. Which is preferable because if you're setting up custom snap views you have to use those functions they are normally bound to.

I used to use the in game config files to set up all my TM warthog switches. But honestly I've found Autohotkey to be a far superior and more flexible solution which I highly recommend to anyone in this situation. It's simple, it's universal, you never have to worry about updates overwriting changes to the lua files, or ED changing the way they work. You just leave all of the game commands as their default keyboard commands, and use autohotkey to make a script file for each DCS module binding the keys you want to the switches you want. I find it works better in general too. I was following some lua editing examples for the mig21 from the leatherneck forum, and I found that the commands would eventually time out and not work. For example the WH switch left in the up position for a long time, I would flip it down and it wouldn't respond, as if it had timed out. This is never an issue with Autohotkey. It's fast, responsive, and reliable. Yes, it can be a nuisance to start a script before flying each module. But I automated that process too and built it into the profile switching in Voice Attack. At worst you have a bunch of scripts on your desktop and you have to alt tab and start a different one if you want to go fly another plane. Take my advice and look into it, you'll never want to go back to fiddling with the DCS configs.

numpad 0 1 2 and 3 are also supposed to be unbound as well and used by voice attack for the various talk keys. Only the A10c uses multiples that I know of and the other modules use a single talk key. Which is numpad 1 on all the modules I've tried. Then typically you use your joysticks software to bind that push to talk key to your stick or throttle, or autohotkey. I bind mine to the coolie hat ptt swtich forward on the warthog throttle with autohotkey. I believe it has to use a keyboard key because of limitations of Voice attack not being able to use joystick keys to trigger it.

What server is this? I'm having trouble finding any servers that are mig vs tiger. I'm really not interested in playing aim120c online.

Flipping views is a result of the comms menu not being triggered properly. Common causes of which can be multiple things. Such as the system failing to detect easy vs hard coms. Failing to unbind f11 and f12 as per the instructions, or even just needing to reset the profile while in the game to refresh it. First make sure all keys are set up appropriately as per the instructions. Unbind the ones it says to. Then make sure its detecting your coms mode and doesn't give errors in the voice attack window about failing to detect and falling back on easy mode, then lastly reset the vaicom profile while in the aircraft before you're about to start by saying "profile reset".

The way you say "still fly the mig21" is there a reason to stop I wasn't told about?

The hold up is getting the top gun theme song licensed for the menu screen wallpaper.

Not really, there is this thread that could potentially help. But I think it's kind of old and a lot of the links in it are broken and out of date. http://forums.eagle.ru/showthread.php?t=42462 I don't know if it's adaptable to windows 10 though. Basically your calibration could be corrupt or something. You might need to investigate into that angle. Or unfortunately the throttle could be faulty, hopefully not.

You also have each axis bound to every single device on your system. When working on controls the best thing to do is go into the module you want to work on, do a cold start mission or something where you can just sit and try stuff out, then edit the controls for that plane and play around. What I do when I start binding any new modules controls is go to the axis settings, unbind every single axis for all controllers. Like in your case, you have a steering wheel bound to it too for example. Then I rebind only the Axis I wish to bind on the controllers I wish to bind. Start from scratch essentially on Axis bindings. If you have TrackIR or a mouse, don't unbind those. DCS will auto assign stuff to all kinds of controllers that it finds connected. Out of the box it will be a conflicting gigantic mess with axis bindings on everything. You're going to run into the same thing on buttons. There will be tons of button assignments that were auto assigned to your wheel, pedals, etc. One really powerful tool is the clear category button. If you click that, it wipes out every binding for a device. So for example, I'm going to guess you aren't using your steering wheel in DCS. You could safely click any binding on it and hit clear category and wipe all those out. Same thing works with Axis bindings. The single greatest thing about DCS keybinding setup to me is that you can press a key or button and it instantly goes to it. So you can rapidly clear and rebind things at will. Once you get the hang of it, it's the best key binding system ever made in my opinion.

That's pretty weird. I don't know how much effort you have put in to custom controls, and therefore how much work it's going to be if you have to reset them, but you could try moving the config files out of your settings folder to reset them completely to defaults just for testing and see if that helps. I don't remember off the top of my head the file path but there's a settings folder under the windows user folders where it saves all your keybinding profiles and game settings. You don't delete the config files, just move them out of there and back them up, then you can always put them back if it doesn't fix anything.