LeCuvier

Please excuse my ignorance, but where in ME do you disable the afterburner?

You are wrong: I didn't check this as I've never touched these commands. You are right: that was the problem. I have never touched these bindings for any of my many aircrafts, and all except the Bf-109 carried over to the new PC without any glitch. Strangely, I don't see any .diff.lua file for the mouse. Any idea where that's hidden? Thanks anyway, you made my day!

Yes the reflections are gone, but now it seems that the side windows are made of very bad or old plexiglass. When I fly the free flight instant action in Caucasus, I cannot see anything on the left or right. Only the windshield is clear and transparent.

I have migrated all my software to a new gaming PC, and I've been able to get almost everything working as it used to. Exception: When I'm in F2 view I can no longer change my camera around to look at the different aircraft from different angles and distances. I used this mostly during replays. Now, the mouse has no function at all in F2 view. This applies to all aircraft I use. I've been through my options settings multiple times, but I cannot find where to correct this. I would be grateful for any help.

No problem here. If it was a software problem lots of people would be screaming. Sounds like you have more than one game controller bound to that axis.

You have obviously overlooked the request "...no discussion here plese!" in the title of this thread. I made this request because I want this thread to be a knowledge resource, and not to be diluted with lots of posts.

I think I have found the culprit. The joystick button I use as TMS seems to be a bit capricious especially when I use it for "TMS Forward Long", so sometimes it works and sometimes it doesn't. Thanks to your post I know now that i need to watch for the ""TDC" indication in the bottom left of the HUD. I apologize for reporting a bug while it was poor precision of my VRP stick.

I'm a bit puzzled. You say "the HUD was never set as SPI". Shouldn't it be "SOI" rather than "SPI"? In step 1. I use Coolie switch up short to set the HUD as SOI. Is that the wrong thing to do?

Here is a new track. I replayed it and it showed the real sequence: 1. set HUD as SOI 2. Slave TDC to TVV 3. Manoeuvre the TVV to the target 4. Ground-stabilize the TDC 5. Make SPI 6. Slave all to SPI Up to and including step 5. all was fine. But when I did "China hat forward long" to "slave all to SPI", the little square pointing to the SPI disappears. A-10CII cannot SLAVE ALL TO SPI.trk

wrong. I always set the the SOI (not SPI) to the HUD first. But I don't trust the tracks. Why are you talking about waypoints? When the target is at a waypoint I don't need to go through the process I have described in my original post.

May I correct the correction... The default binding "RWin + C" does not work. But "RShift + C" works fine, and also a game controller button works.

I posted this in January. See https://forum.dcs.world/topic/368442-slave-all-to-spi-fails-most-of-the-time/#elControls_5595989_menu @f-18hornet Replied that this issue was "reported for analysis" and the thread was locked for replies. I have not seen the bug confirmed, and there is still no statement whether and when this will be fixed. In my opinion this is important functionality for designating ground targets. I have successfully used it for a long time, and then an update destroyed it. Not an indication of good software configuration management! The bug fix should be a priority item! ED, please provide an answer!

Unfortunately the problem came back. Apparently the scroll wheel of my old mouse was the culprit. I bought a new one and the problem is gone.

I looked at this and saw that the command is default-bound to "RWin + C". My German keyboard doesn't have a "Right Windows" key, so I bound the command to "RShift + C". I also bound it to a button on my Joystick. Both work fine here.

My added line actually triggers the "Eject" command 3 times with a single button press. Twice when you push the button down, and once when you release the button. This is the LUA line: {down = iCommandPlaneEject, pressed = iCommandPlaneEject, up = iCommandPlaneEject, name = _('Eject (press once)'), category = _('Systems')}, And of course I have all modded "default.lua" files under saved games, using the Command Injector by @Quaggles, so I don't have to mess around after every update. Is "General" a better place than "UI Layer"? I wouldn't know why.

It took me about 15 minutes plus a bit of testing time, to add a line into the "default.lua" for "UI Layer", so it works across all aircraft modules.

My understanding is that the stick smoothing option helps to make stick input less "nervous". I wouldn't think that it helps to "slow" the pitch trim, which is the main subject of this thread. Please correct me if I'm mistaken! My method for providing a slower pitch trim is to add these lines to the "default.lua under "Saved Games" (I use the command injector by @Quaggles): {pressed = iCommandPlaneTrimPitch, up = iCommandPlaneTrimPitch, value_pressed = 0.3, value_up = 0, name = _('Trim - Nose Up Slow(Hat Aft)'), category = {categories.flight_controls, categories.stick}}, {pressed = iCommandPlaneTrimPitch, up = iCommandPlaneTrimPitch, value_pressed = -0.3, value_up = 0, name = _('Trim - Nose Down Slow (Hat Forward)'), category = {categories.flight_controls, categories.stick}}, This methodis very robust.

I found that Heatblur provides 3 different setting speeds ("normal", Fast and Slow) for a number of commands (e.g. "Weapon Slew". I do not believe that the real Phantom has those options, but it helps the sim users. A good reason in my opinion to do the same for the pitch trim command.

I see, you also used the "traditional" format of the .lua lines. That seems to work fine.

Has anybody managed to make this mod work with the F-4E Phantom? I couldn't make it work, and in the end I had to remove the sub-folders for the Phantom under "..\Input Commands\" because it blocked the DCS software completely. Heatblur uses a different structure in its "default.lua" files and I suspect that the @Quaggles mod doesn't handle that correctly. Edit: I also didn't see anything for the F-4E on the Github page owned by @Munkwolf. @Munkwolf do you intend to provide bindings for the Phantom? Edit: I seem to make progress, using the "traditional" format in the "default.lua" under Saved Games. Example: I wanted to make "slow" versions of the Pitch Trim Nose-up and Nose-down commands. The original command lines have this form: { name = _('Trim - Nose Up (Hat Aft)'), up = iCommandPlaneTrimPitch, pressed = iCommandPlaneTrimPitch, value_up = 0, value_pressed = 1, category = { categories.flight_controls, categories.stick, categories.essentials } }, { name = _('Trim - Nose Down (Hat Forward)'), up = iCommandPlaneTrimPitch, pressed = iCommandPlaneTrimPitch, value_up = 0, value_pressed = -1, category = { categories.flight_controls, categories.stick, categories.essentials } }, In the original "default.lua" (under "keyboard") I could use these modified lines and they worked fine: { name = _('Trim - Nose Up Slow (Hat Aft)'), up = iCommandPlaneTrimPitch, pressed = iCommandPlaneTrimPitch, value_up = 0, value_pressed = 0.3, category = { categories.flight_controls, categories.stick, categories.essentials } }, { name = _('Trim - Nose Down Slow (Hat Forward)'), up = iCommandPlaneTrimPitch, pressed = iCommandPlaneTrimPitch, value_up = 0, value_pressed = -0.3, category = { categories.flight_controls, categories.stick, categories.essentials } }, But when I used these lines under "Input Commands" in "Saved Games", DCS World stopped running when I opened Options/Controls or tried to run a mission with the Phantom. So now I used the traditional command line format under Saved Games: {pressed = iCommandPlaneTrimPitch, up = iCommandPlaneTrimPitch, value_pressed = 0.3, value_up = 0, name = _('Trim - Nose Up Slow(Hat Aft)'), category = {categories.flight_controls, categories.stick}}, {pressed = iCommandPlaneTrimPitch, up = iCommandPlaneTrimPitch, value_pressed = -0.3, value_up = 0, name = _('Trim - Nose Down Slow (Hat Forward)'), category = {categories.flight_controls, categories.stick}}, I entered these lines under "C:\Users\MyName\Saved Games\DCS\InputCommands\F-4E\Input\F-4E-Pilot\joystick.

Interesting reading! I struggle with the pitch control not only for the trim, but also for the response to stick movements which, to me, appear very "nervous". These "large oscillations" don't help when I try to aim at something. So I added "slow" pitch trim commands to my "default.lua" with pitch trim response values reduced from 1.0 to 0.3. Will see how that works for me.

We get what we pay for. We pay for new modules, and the number of active modules is ever-increasing. Unfortunately, every module requires maintenance. But that maintenance requires manpower and manpower is costly. Impossible to finance all that work with one-time payments per module. So that maintenance is reduced to a level that produces more and more dissatisfaction. As long as we don't pay for maintenance we won't get much. I have bought 22 aircraft modules, not counting the ones in Flaming cliffs. But in reality I only fly about 6 or 7 of them more or less regularly. I would like those to be kept in shape and accept to pay a reasonable annual or monthly maintenance fee for maybe 6 of them. And I will be very reluctant to buy any more modules, no matter how enthusiastically they are welcomed by the community.

I un-checked the option F10 AWACS View, ran a quick mission, and re-checked F10 AWACS View. Now I can zoom the F10 view with the mouse wheel. I just hope it stays this way!

This is really weird! Yesterday I was agreeably surprised when I could control the F10 zoom with the mouse wheel without having touched any setting. But today, alas, it didn't work any more. @NineLine: is this a new feature for which I cannot find the option to change?

Thanks for your feedback, but this did not work for me.