jonsky7

Well you're not wrong 😎
 
{pressed = device_commands.Button_2, up = device_commands.Button_2, value_pressed = 0.01, value_up = 0, cockpit_device_id = devices.APN_209, name = _('RAD ALT LO SET DOWN'), category = {_("RAD ALT")}}, {pressed = device_commands.Button_2, up = device_commands.Button_2, value_pressed = -0.01, value_up = 0, cockpit_device_id = devices.APN_209, name = _('RAD ALT LO SET UP'), category = {_("RAD ALT")}}, {pressed = device_commands.Button_3, up = device_commands.Button_3, value_pressed = 0.01, value_up = 0, cockpit_device_id = devices.APN_209, name = _('RAD ALT HI SET DOWN'), category = {_("RAD ALT")}}, {pressed = device_commands.Button_3, up = device_commands.Button_3, value_pressed = -0.01, value_up = 0, cockpit_device_id = devices.APN_209, name = _('RAD ALT HI SET UP'), category = {_("RAD ALT")}},  
You can adjust the values in the part
value_pressed = 0.01
value_pressed = -0.01

0.05 seemed too fast to me, but 0.01 may be a little slow. Maybe 0.02 would be good.

Copy into both keyboard and joystick "default.lua" files.

"Pressed" means the action will be repeated as long as the key/button is held down

or you could change that to 
{down = device_commands.Button_2, up = device_commands.Button_2, value_down = 0.01,     value_up = 0
(probably better for a rotary encoder)

if you want to move the setting a certain amount each key press, like the notch in the mouse wheel

Regards
Jon.

I've made a few changes bringing it in line with the description that was found in one of the original config files.

Not sure if FC3 was a usable unit type, so added them separately for each aircraft.

Removed the duplicate entries for the Mirage F1 exports.

On a side note, the whole point of the configure for unit type was so you didn't have to modify the export names for any default exportable display. Most of your aircraft have mods applied for the RWR etc, so it's a bit redundant.

Helios2.lua 
 
Give a try I suppose, there wasn't anything glaringly obvious, name in settings menu = Helios2

When I asked ChatGPT to compare it said:

Helios2.lua is now better written, more efficient, and easier to maintain than the original Helios.lua. With additional comments and modularization, it could be even more user-friendly and robust. 😎


edit: error in the above file at line 128, corrected below
 
Helios3.lua

Here is my Input folder, from 

DCS > Mods > aircraft > CH-47F

Input.zip
The main controls has this section 
Line 968 onwards
 
and the gunners section has 
Line 85
 
The only other thing I can think of is if you are not using English as the language for DCS (I've never had to change it so I'm unfamiliar), I've seen at least one other post where a keybind was hard to find due to translation. From your screenshot it looks like you are using English, but I thought I'd mention it anyway.


And just some info:
If you modify any game files at any time, and then do an update or repair, all of those files are saved in the main directory in a new folder called Backup.000, and they are saved with the folder structure intact, so you can just drag the contents of BackUp.000 back into your main DCS folder to restore all your Mods. A mod manager is much better though, for when the files can changed (can break stuff)

More info.
The files and folder for the Crew Indicator are located

DCS > Mods > aircraft > GCBase > Cockpit > Scripts > AI > ControlPanel

and the location is in the file
g_panel_page.lua

It is extremely similar to the Huey's Crew Indicator file.
To change it's position I mess with Line 62

base.init_pos       = {aspect + shift_X,firstLineY + shift_Y} 

Mine being
base.init_pos       = {aspect + shift_X - 5.2,firstLineY + shift_Y + 1.6} 
 
Hope any of this helps.

Yep
 
local group = Group.getByName('name_of_group_to_be_activated') group:activate()  
script activate.miz

Turns out I had a Voice Command action working off some button presses and I had forgot to make it module specific..... D'oh  🤦‍♂️
I spent hours trying to fix this lol.

This post is quite old but I thought I would share the solution.
The action required is
"Start playing actor" and the value should be 2,
this sets DCS into the navigator seat, although you will still be in the pilot seat. This is only required for switches not accessible from the pilot seat.
Be sure to add "stop playing actor" at the end of the actions.
While the "actor" is doing their thing, pilot only switches will be locked out, so best not make the actor do stuff for too long.

Yes, If you go into your monitor config file
usually located in Saved Games\DCS\Config\Monitorsetup
there is an entry at the bottom that says 

UIMainView = Viewports.Center
 
The UIMainview sets the boundaries for the Main menu, F10 map, Mission editor, and the dialogs that appear in game.
 
You can change it from the above to something like

UIMainView = 
{
x = 0;
y = 0;
width = 2560;
height = 1440;
}
and limit the boundary to either one of your monitors.
 
If you have absolutely no idea what any of that means, you might want to have a read of this thread
 
 

The bomblets don't seem to necessarily explode the tanks like they do in DCS, but disable them, maybe?
 
 
The only difference between the CBU-97 and CBU-105 is that the 105 has a guidance kit on the main weapon cannister, all of the internals are the same.
Like the difference between a MK-82 bomb and a GBU-38 
Looks pretty effective to me
 
 

You have the right file.
To be honest with you it has been a long time since I made this change, so I don't exactly remember how the number changed the location but...
line 18
local aspect        = LockOn_Options.screen.aspect

I changed that to
local aspect        = -1.34  
 
I think making it more negative moves it left.

The UIMainView defines where the following are placed
The Game main menu
The F10 Map
Mission Editor
The boundaries of the Comms Menu (Right) and subtitles (left)
 
GU_MAIN_VIEWPORT
I've only found
The gunner reticle in combined arms tanks etc
 

Ok, I have been trying too, and can see that it doesn't seem possible to invert 2 axis setup like above.

Shall we give UCR and vJoy another try?

From your first post it seems like you have UCR and vJoy installed.

vJoy is at least present in your windows game controllers, correct?



If so, on we go

Open UCR, Click on create profile, you should be presented with this window.

Give your profile a name, for input device select your pedals, output device is vJoy

null
 
Click on Axis Merger (1), you will be prompted to add a name for your axis.

2. Click on the Axis High Input, press your left pedal to bind it
    Click on Axis low button, press your right button to bind it.

3. You have to select an output Axis using the 3 ... button, I have X here, but Axes Z is a good one.

The mode should be Average

We will have to test the output, and maybe have to come back to change the Invert High, and Invert Low options

4. Press the play button >

The profile should now be running.

Go back to windows games controllers, select vJoy and select properties. Test your output by pressing each pedal in turn.


 
This is where you may have to go back to UCR and play with the invert settings. 

You will need to close the above window when you make changes because it stops working.

When you make changes in UCR, press the stop button [] 4, then press play again >.

If inverting the High and low still doesn't work properly,

Switch the left and right pedals between Axis high and Axis low (step 2)
 
🤞 please work

Just to elaborate a bit on what raz+r has said above.
The CTRL, ALT, SHIFT, and WIN keys are classed as modifier keys. This is so you can have hundreds if not thousands more keyboard commands.
As you can have for eg "B", LCTRL+B, LALT+B, LCTRL+LALT+B, LCTRL+LALT+LSHIFT+B etc etc etc.
As raz+r has said, if you are holding CTRL to operate the speed brake, then when you are operating your POV hat, you are actually sending the command LCTRL+POV Hat, and not just POV hat which is the assigned command.
You can however have multiple binds to do the same "action", so you could assign both POVL and LCTRL+POVL to look left.
All you have to do is select the look left command in the joystick column, press LCTRL and POVL.
You will then see two binds assigned to that action eg POVL, LCTRL+POVL.
Then look left will work whether LCTRL is pressed or not.

You can get into an issue with the graphics card's maximum supported 3D application resolution

You're trying to export a resolution of 8560x1440 which is now more than most graphics card can support.
As a educated guess I'd say you're losing 880pixels off the edge.

3x1440p monitors are 7680x1440

eg
GTX1080/RTX2080ti/RTX3090 Max res is 7680x4320

7900XTX max resolution is 7680x4320

In fact I can't find a single graphics card that will do more, seems to be a standard, equivalent to 2x4K displays.

Are you selecting the controller column? 

I don't think you can load it all in one go, you have to select each controller in turn.
Left click the controller name

eg, the red circled area
 

 

There is a way yes, it will require a little bit of editing a file though.
If you go to

DCS World/Mods/aircraft/FA-18C/Input/FA-18C/joystick

and find the file called default.lua

Add this line
{ down = hotas_commands.THROTTLE_SPEED_BRAKE, up = hotas_commands.THROTTLE_SPEED_BRAKE, cockpit_device_id = devices.HOTAS, value_down = -1.0, value_up = 1.0, name = _('Speed Brake Switch - EXTEND, else RETRACT'), category = {_('Throttle Grip'), _('HOTAS')}}, You will have a new keybind option called 
Speed Brake Switch - EXTEND, else RETRACT

The speed brake will extend when the button is pushed, and retract when the button is released.

I have modified the file for you, so can paste it into the folder listed above. >>>>>>>  default.lua
You will have to re-copy the file after every update, and it will break integrity check on servers that have the new "REQUIRE PURE SCRIPTS" enabled, but I haven't seen many that do yet.


Alternatively, for the Warthog, there is an excellent script for the TARGET software than changes the way the buttons work slightly.
 

The Apache is not available on the stable branch of the game yet.

So the forward position on the force trim hat is the button you want to set the trim centre position of the stick.
With centre trimmer mode option activated, 
1. Hold forward on hat
2. Put stick and rudder where you want it
3. release hat
3a, in other helicopters this now means your joystick and pedals are locked out until you centre them.
4. centre your joystick and pedals.
5. New centre position should be recorded by heli.
Press right control and enter to bring up the controls indicator. 
To be honest I haven't tried that trimmer mode. But that is how it normally works.
 
 

If you are inputting a trailing zero for the last pair of coordinates in the Viper, then like Blinky.Ben has mentioned, you are looking at the wrong coordinate type in the F10 Map.
The default coord system for the F10 Map is Degrees' Minutes' Seconds (DD.MM.SS)
N37'25'23 E45'12'17
The Viper users the Decimal Minute system, Degrees' Minutes' Thousands of Minutes (DD.MM.mmm)
N37'25.321  E45'12.282
You can change the default F10 coord system in the settings if you mostly fly the 16, or as Blinky.Ben mentioned use LALT-Y in the F10 map to change coordinate type.

Thanks, it was FFB turned on 🤦‍♂️
Had to start with a new saved games folder to fix another issue, and didn't realise FFB default is on.