Deezle

Sounds weird but I have found the setting "Synch HOTAS controls at mission start" or whatever it's called can cause more problems than it solves, including things similar to this. I would uncheck that if it's currently checked and see what happens.

Agreed, CPU and PSU are ridiculous and the money could be better spent elsewhere. Such as 32gb of RAM. I often exceed 20bg RAM usage when playing MP.

When the Gazelle was first released, VRS was a thing, and it was pretty sudden and violent from what I remember. It certainly doesn't exist anymore.

Adding these lines to the default.lua found in the FA-18C/input/joystick folder should do the trick. This will create two new keybinds and just reverses the logic of the default bindings. { down = iCommandLeftEngineStart, up = iCommandLeftEngineStop, value_down = 1.0, value_up = 1.0, name = _('ALT Throttle (Left) - OFF/IDLE'), category = {_('Throttle Quadrant')}}, { down = iCommandRightEngineStart, up = iCommandRightEngineStop, value_down = 1.0, value_up = 1.0, name = _('ALT Throttle (Right) - OFF/IDLE'), category = {_('Throttle Quadrant')}}, Do note, DCS will overwrite the file every time it updates, best to create a JSGME type mod to uninstall and reinstall for updates.

I don't use curves with the Gazelle. I turn down the pitch and roll Y axis saturation to 70. Keeps it linear at the expense of losing the last 30% of travel, which you absolutely never need. And my stick has about a 7" extension. I do think the Gazelle FM is weird though, for sure.

Looks correct to me.

Good questions, I wanna say they started out as 1/4" (~6mm) rod.

That is not the issue. It doesn't work using another controllers axis or using a hat switch, either. It will not auto lock for several of us here.

Same. Track attached to this post (won't let me upload it to this thread) https://forums.eagle.ru/showpost.php?p=3798051&postcount=296

Long time no see, guys. So a while back I tried a DSD input board for my collective, I had trouble with all the axes moving about in a cyclical fashion, back and forth, even when the controls weren't touched. I emailed DSD about it and their response basically said there's nothing wrong with their board and that I can pound sand. So I ordered a Leo Bodnar board not long ago, got it all hooked up and I must say it works perfectly, LB boards are bit spendy, but worth every penny. I then used the DSD board in my NMSP since it doesn't have any axes to worry about, it works fine in that capacity. My next plan is to buy the big Leo Bodnar board and combine my right panel and lighting panel into one device. This will simplify my pit even more, then I will have no more Arduino stuff, which is fine for what it is, but has a few problems. I have also added a 3rd MFD to my display monitor since I got the F/A-18C. I did some cleanup in my pit today, took the pedals and stick out and vacuumed them since they were covered in dust and lint. You may also be able to notice a new pickle button on the stick. It's an OTTO Mil-Spec type switch, the original started going bad, the new one sticks out a bit more, but it's pretty nice. You can also see the custom pedals a bit better. I also worked on cleaning up the rats nest of wiring behind the monitors. I wasn't that happy when I was done, but looking at the before picture, I must say it's a huge difference. Please forgive the dust bunnies still present back there.

The biggest Leo Bodnar board is about the best you're going to find without getting into specialized stuff. 8 axes, 32 buttons, 1 POV hat. Each rotary encoder will use two button inputs. For the F/A-18C UFC and HUD control panel I'm counting 40 button inputs, so even if you use the 4 POV inputs as buttons (which works fine in momentary applications, like the number pad) you're still 4 inputs shy. There's 7 pots, which is fine. I have an Arduino Mega running MegaJoy in one of my panels, it supports something like 64 buttons and 12 axis inputs (it show ups in windows/game as two devices). I will be replacing it with the aforementioned Leo Bodnar board, though. Arduino is cheap and can get the job done, but IMO it's an imperfect solution compared to dedicated hardware for the task. That and good luck figuring out the code to make an encoder work with it, I never figured it out. Rotary encoders send out a specific pulse "code", this must be deciphered with the input board of the your choice before it will show up as a proper button press. The boards that support rotary encoders will have software to set specific inputs for rotary encoders. If you connect a rotary encoder to an input board as if it was just another switch/button, it will not work properly. All the assignments are there to my knowledge, and if not they're pretty trivial to add.

Same, tried joining a couple times over the years.

Doesn't matter what I use, it will not lock by itself after you stop slewing. Tried the nipple on the WH throttle. Tried using the coolie hat on the WH throttle. Tried the thumbstick on my collective as well. Nada. I also made sure to unbind the axes binds when trying the coolie hat to make sure there wasn't any kind of conflict or interference from them. Zilch. ED needs to go back to the drawing board since there's obviously a problem for some of us.

I've never noticed a difference, therefore I keep it all the way down.

Yeah, it definitely will not lock on it's own when "realistic slew" is unchecked. Disappointing :( Track attached. mav slew.trk

I'd make sure you guys have enough of a deadzone on the mini stick axes, Wags said it will only lock after being released for 1 second, if the sim still sees any little jitter in the axes it will probably prevent a lock. I may be way off base here since I'm still at work and have yet to try it.

Thanks. Reproduced and track added. elevation stuck.trk

The RWR is weird compared to the other western ones. Threats only move inward when they lock you, and only move to the center when they fire. The other RWRs will move inward as you get closer to lethal range. The filtering logic is borked as well, it's capable of showing enemy airborne threats with the chevron over them, but often I try to use the filter to show the "6 highest threats" and it will filter out all the enemy aircraft and leave all the friendlies on the display :doh: I sure hope it's still WIP.

Reproduced and track added. Seems to happen when changing from A2G weapons to A2A weapons. rearm bug.trk

Has definitely happened to me too.

Looking at your track, it looks like a key/button bind is pulling the throttles down since they move slowly back to idle. A duplicate axis bind would move them back instantly.

I'd like to see this addressed, it's a one character change in the FA-18C.lua file to correct this.

Has happened to me, too, a few times. Been a while though, wish I knew how to reproduce it. Howdy fellow arfcommer ;)

Happens to me, too. Track attached. 2D HUD Glass.trk

I have a VKB Gunfighter Pro (the one with the extension) with the TMWH grip mounted on it. I use the TMWH throttle and have no reason to switch. It's a nice setup, I like it. I like the Virpil offerings because they support the TMWH grip natively, if they were available when I bought my stick I probably would have gone that way.