=Panther=

Provide a track.

AA weapons are launched with the trigger in the Hornet. Verify that you are using the trigger and not the weapons release button (pickle).

I had to swap around to different USB ports until I found the one that didn't provide power. Seems my ASUS board can charge a cellphone from just about every port. I did manage to find one, which without looking, I believe is an expansion USB card.

6 months.... I wasn't happy but it arrived finally and of course while I was out of town.

You will need to assign the commands in DCS. Device shows up as a USB controller in windows. If you want the Master Caution to illuminate, you will need their "Raygun" application.

SimShaker.lua was removed, but SSA didn't rebuilt it on DCS launch. So I restored it to the proper directory, restoring the jetseat for other airframes but still fails for the Hornet. After reading this log I discovered something important. I have multiple installs of DCS. I have two beta versions, and one stable. One of the betas is a modded install for flying with a group. When I encountered the failure, I'm using the modded install. However the script information below shows it is pulling data from my clean install Open Beta and my stable version with no mods. So the question is why is SSA looking at two different DCS directories, but not the one I'm actually running. This wasn't an issue until the update that automatically pushed last week. 09:30:53.273 SimShaker for Aviators Version 1.3.3.0 09:30:53.276 ********** DCS World Public Release version folder found in Saved Games ********** 09:30:53.284 DCS export feature setup: SimShaker.lua added to D:\Saved Games\DCS\Scripts 09:30:53.291 DCS export feature setup: ExportCore.lua added to D:\Saved Games\DCS\Scripts\SimShaker-export-core 09:30:53.298 DCS export feature setup: ExportDevice.lua added to D:\Saved Games\DCS\Scripts\SimShaker-export-core 09:30:53.305 DCS export feature setup: KeyValueStore.lua added to D:\Saved Games\DCS\Scripts\SimShaker-export-core 09:30:53.312 DCS export feature setup: Network.lua added to D:\Saved Games\DCS\Scripts\SimShaker-export-core 09:30:53.321 DCS export feature setup: Protocol.lua added to D:\Saved Games\DCS\Scripts\SimShaker-export-core 09:30:53.327 local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua') call found in D:\Saved Games\DCS\Scripts\Export.lua 09:30:53.328 local SimShakerlfs=require('lfs'); dofile(SimShakerlfs.writedir()..'Scripts/SimShaker.lua') call found in D:\Saved Games\DCS\Scripts\Export.lua 09:30:53.329 dofile(lfs.writedir()..[[scripts\SimShaker-export-core\ExportCore.lua]]) call found in D:\Saved Games\DCS\Scripts\Export.lua 09:30:53.330 ********** DCS World Open Beta version folder found in Saved Games ********** 09:30:53.331 DCS.openbeta export feature setup: SimShaker.lua added to D:\Saved Games\DCS.openbeta\Scripts 09:30:53.333 DCS.openbeta export feature setup: ExportCore.lua added to D:\Saved Games\DCS.openbeta\Scripts\SimShaker-export-core 09:30:53.335 DCS.openbeta export feature setup: ExportDevice.lua added to D:\Saved Games\DCS.openbeta\Scripts\SimShaker-export-core 09:30:53.337 DCS.openbeta export feature setup: KeyValueStore.lua added to D:\Saved Games\DCS.openbeta\Scripts\SimShaker-export-core 09:30:53.339 DCS.openbeta export feature setup: Network.lua added to D:\Saved Games\DCS.openbeta\Scripts\SimShaker-export-core 09:30:53.340 DCS.openbeta export feature setup: Protocol.lua added to D:\Saved Games\DCS.openbeta\Scripts\SimShaker-export-core 09:30:53.342 local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua') call found in D:\Saved Games\DCS.openbeta\Scripts\Export.lua 09:30:53.342 local SimShakerlfs=require('lfs'); dofile(SimShakerlfs.writedir()..'Scripts/SimShaker.lua') call found in D:\Saved Games\DCS.openbeta\Scripts\Export.lua 09:30:53.343 dofile(lfs.writedir()..[[scripts\SimShaker-export-core\ExportCore.lua]]) call found in D:\Saved Games\DCS.openbeta\Scripts\Export.lua

Yes, the captogloves have the Captosensor in them.

DCS OB current patch LUAs were removed, but the sim nor SSA rebuilt them on system restart. So I restored them to the proper directory. SSA, latest version that auto updated earlier this week. Unless I'm blind I don't see a version number. Removed the export.lua for testing, only used an export.lua with the SSA info in the file, with no change.

SSA auto-updated a few days ago on PC start but I haven't flown until today. The only 2 aircraft that I usually fly is the A-10C and the F/A-18C. Today the hornet isn't working with the SSA and Jetseat. Here is the error, which refuses to go away when attempting to close. I have already reinstalled SSA, restarted, rebuilt the luas and nothing has corrected this. Please assist. TIA.

Okay, I'll test my install this week. Very likely something changed with 2.5.4, I have noticed that there is a very noticeable box around the chat now, where as before it was completely transparent.

Odd, but did you restart DCS after disabling it?

Just disable it in the module manager section of the settings page. The same area you put your OATH key in at.

Head on a swivel, preemptive flare release, and get in and out quickly (think element of surprise) is important keys of surviving an IR missile WEZ. It is much easier in a CO-OP MP environment, especially in groups where you're in direct communication with your wingman. Wingman should be covering the other wingmans 6.

I think this is called debounce, and it is something that needs to be adjusted in DCS code. Seen it in other sims like iRacing with certain controllers. The software team at iRacing had to make some tweaks to the controller settings. I suffer from the same exact problem, and it is frustrating.

Somethings that come to mind, you pitch or cut wires, your ground wire is unsecured, or firmware issues. Check your install for all of the above.

It's called flight idle, which is different than ground idle. System is correct, nothing wrong with your hardware or the physical function.

That is what I did, removed bottom base plate. Loosen the two screws holding the throttle arm in place, NOTE there is a spring behind that cover plate. Not a lot of spring tension, but it could spring out and become a cat toy if not prepared. With that piece out, and the detent cover removed, the throttle arm will slide upwards, to reveal two screws on the lower arm. Remove those screws, and the back side piece will open up.

Installed, it was very simple to install. I also had to remove the opposite side of the throttle grip. Have an early model (#1629), and the harness is routed short, with the slack on the base side of the throttle.

This video shows how to take apart the throttle to access the switches on the throttle. It's a long video, the author changed out the EAC to a magnetic switch. That part can be ignored, but the disassembly portion is helpful.

Yes, still unable to input MGRS. Probably much later down the road before that becomes available.

Spam the ON/OFF button on the UFC, it seems that it works but very intermittent at best.

The following commands cycle to MVR if using HOTAS WH Throttle: Toggle Flaps Dn Toggle Flaps Up

Can you duplicate it? Or did it only happen once?

Something is a miss with your install then. That issue was resolved last year or so. With the A-10C and F/A-18C modules, I use my CMS switch for CMS functions. I then use the paddle (modifier), and CMS to interact with sim e.g. RMB, LMB, Scroll, Zoom, recenter. Neither mapping overrides the other, both still function correctly. Sounds like you have a bad install, or worse keep dragging in an old input folder on each patch.