LeCuvier

@motoadve: You do not tell us which one of the VIRPIL sticks you have. Some of their sticks have a paddle/lever with an axis (plus a button), and some them have a paddle/lever with button only. As long as you don't share which model you have we really have no idea what the problem might be and how we can help you. Be specific please!

1. I have disabled the deadzone on my VRP stick, and I have no deadzone in the axis tuning for the FA-18C 2. I have no problem with AP/BALT. I adjust my flight path to level flight, which is easy on the Hornet, and engage AP/BALT. That does it. 3. However, I confirm the problem with AP/HDG. I had set the heading to 20 ° and engaged AP/HDG. The UFC shows HDG engaged, but the Hornet continues flying straight ahead. Only after I wiggled the stick a little bit, it turned to the 20 ° heading. I attach a track demonstrating the issue. @NineLine: Please report! FA-18C AP HDG Bug.trk

A "Global" curve definition, if it were possible, might not do you any good, because the response to stick inputs varies between airplanes.

If you don't have analog brake pedals that might be a totally different ballgame. I have no experience with that.

That's your subjective assessment. I find it much easier to taxi than the Spit or the Mosquito with their strange combined pedal & brake method. If I flew those aircraft frequently, I would probable find them just as easy to taxi.

What exactly do you mean by "reset"?

Can you elaborate? Which command is that? My mouse has a scroll wheek in the middle. I can depress that, but I don't see how that changes the pilot Point Of View. I use TrackIR and I have to make the strangest contortions to see the 10s of the TACAN channel, let alone select the channel.

Good thinking, @scoobie! But it might be difficult to achieve a solution that works for most people. And it adds new complexities which could cause new problems. In reality, there are very few truly common commands, and when you installed a new module it takes very little time to bind those manually. On the other hand, default bindings as they work now cause a lot of non-value-added work. Like, recently I had plugged in my old TM WH joystick trying to add some bindings for the Ka-50. Next day I wanted to fly the Hornet, and I was cursing my VRP stick because the pitch and roll actions were jittery. I recalibrated the VRP stick, but no improvement. I then went to Options controls and realized that the old TM WH stick had been bound to the Hornet's pitch and roll axes "by default". And the same with all my other aircraft! I don't mind if ED create a better default binding method, under one condition: I want to be able to de-activate it. For the sake of simplicity, I would vote to just eliminate default bindings altogether. They are not worth the trouble. A rule I learned from my US colleagues back in my younger days: keep it simple, stupid!

I agree, these commands are there, under the category "Systems". They actually do exist in my "default.lua" under \Joystick. But as you say they don't work for game controllers with pushbuttons only. Regarding the duplicated line for the "Right MFCD - OSB 12", I could not figure out why they display twice and in red. The lua lines in his two "default.lua" look absolutely the same. On my rig the line is not duplicated.

Re the commands "Left Engine Throttle set OFF" and "Right Engine Throttle set OFF", they seem to be missing in both of your LUA files. They are present in my installation. I suspect that the problem might be related to localization.

I understand the duplication of the ILS Volume commands (will look at the MCD next): It helped to look at the "default.lua" you posted. The A-10C II has two pairs of ILS Volume controls: one on the ILS Control Panel and one on the Intercom Control Panel. I attach screen shots of the respective LUA lines. When you look at the command definitions you see that there are two different commands. Unfortunately these different command pairs have the same names, except that the one for the Intercom Control Panel is spelled with lower case, and the one for the ILS Control Panel with upper case. The command names in the "default.lua must be unique, and when they are not the software for Options/Controls shows the duplicate with red font. The software apparently does not consider the commands as duplicates because of the upper/lower case difference. And in my installation (English) the duplicated lines are not red. The French translation however spelled both command pairs with upper case, and now the software recognizes the duplicate and shows it red. The root cause of the problem of course is that ED used practically the same names for 2 paires of commands. @Yurgon: ED ought to fix that by making the command names truly distinct. Edit: I would also consider that the duplicate detection logic should not be case sensitive!

I feel that we have vented a lot of frustration and worry, related not only to the fate of the F-15E but also the question which way ED will be going. This reflects the passion we have for this game, which we all want to see continuing on a solid path. Unfortunately we don't have a lot of hard facts, so much of our discussion is based on speculation and hear-say. I hope that ED will come forth with a statement of facts and intents in the near future. Until they do that, or we are are confronted with hard facts, I see little benefit in continuing on this thread.

If ED went out of business with no successor, it might not take long before this complex software became useless. I've had to provide budget for an engineering software development for some years, and I was amazed by the amount of money we had to spend for maintenance.

Oh hell, yes that was a totally unintended joke. With no typo it was 01-DEC-2018 of course.

I'm afraid that the underlying problem is an unsustainable business model. The only source of revenue is the sale of modules. In order to generate revenue, ED launches new modules before earlier modules are completed. Most of that revenue is probably not spent for the development of the new modules but for (very slowly) completing recent modules, software maintenance and support. Every new module adds to the workload ( = Cost) of software maintainance. It's easy to see that this business model cannot be sustained in the long run. It doesn't work finacially, and it doesn't work for the customer base. I bought the Hornet on 01-DEC-1918, and it's still in "Early Access". I'm not happy about that at all, and I will be very reluctant about buying anything in EA going forward. I believe that ED will be obliged to go to a business model where you pay a monthly or annual fee for using the software. A lot of people won't like that and the customer base might get smaller. Changing to that business model will be challenging; but the alternative is to go belly-up. Just my assessment, maybe ED finds another way to continue their Games line of business.