Jump to content

Recommended Posts

  • 4 months later...
Posted
3 hours ago, Schlomo1933 said:

Could u pls  explain how to input these ? 

Follow the second link first. Quaggle's. 

Read how to manually copy that file into DCS, needs to be done after every update, or use a mod manager like Open Mod Manager (also on Github) or OvGME. 

Also make the default folder structure in your Saved Games, and copy Munkwolf's complete keybinds from his Github. 

https://github.com/Munkwolf/dcs-community-keybinds

Or just for the modules you need. 

Everything is explained on Github. 

  • Thanks 1
  • 1 year later...
Posted

Is it possible to add the RSI-6K knobs as axis like the flaps handler?

I tried to do it copying and adapting the lines in joystic/default.lua. I am able to see the new command axis and assign them, but nothing is moving later in the cockpit.

I5 12600KF - 32 GB DDR4 - Nvidia RTX 4060 - SSD + NVME

Nadie es un completo inutil, por lo menos sirve de mal ejemplo.

 

Posted (edited)

I've added these lines to the Mig-15bis\joystic\default.lua

axisCommands = {
        {cockpit_device_id = devices.CONTROL_INTERFACE, action = control_commands.Mig15_Command_FlapsHandle, name = _('Wing Flaps Handle'), category = {_('Systems'), _('Custom')}},
        {cockpit_device_id = devices.CONTROL_INTERFACE, action = control_commands.Mig15_Command_FrictionLever, name = _('Throttle Friction Lever'), category = {_('Custom')}},
        {cockpit_device_id = devices.CONTROL_INTERFACE, action = control_commands.Mig15_Command_HydroGainLever, name = _('Hydro Booster Lever'), category = {_('Custom')}},
        {cockpit_device_id = devices.RSI_6K, action = control_commands.Mig15_Command_RSI6K_Volume_EXT, name = _('RSI-6K Audio Volume Knob Custom'), category = {_('RSI-6K Radio'), _('Custom')}},
        {cockpit_device_id = devices.RSI_6K, action = control_commands.Mig15_Command_RSI6K_SetTransmitterFrequency_EXT, name = _('RSI-6K Wave Control Handle Custom'), category = {_('RSI-6K Radio'), _('Custom')}},
        {cockpit_device_id = devices.RSI_6K, action = control_commands.Mig15_Command_RSI6K_SetAntennaFrequency_EXT, name = _('RSI-6K Antenna Control Handle Custom'), category = {_('RSI-6K Radio'), _('Custom')}},
        {cockpit_device_id = devices.RSI_6K, action = control_commands.Mig15_Command_RSI6K_TransmitterFrequencyFix, name = _('RSI-6K Wave Control Handle Lock Custom'), category = {_('RSI-6K Radio'), _('Custom')}},
        {cockpit_device_id = devices.RSI_6K, action = control_commands.Mig15_Command_RSI6K_AntennaFrequencyFix, name = _('RSI-6K Antenna Control Handle Lock Custom'), category = {_('RSI-6K Radio'), _('Custom')}},
        {cockpit_device_id = devices.RSI_6K, action = control_commands.Mig15_Command_RSI6K_SetReceiverFrequency_EXT, name = _('RSI-6K Receiver Tuning Knob Custom'), category = {_('RSI-6K Radio'), _('Custom')}},
        {cockpit_device_id = devices.RSI_6K, action = control_commands.Mig15_Command_RSI6K_ReceiveARC, name = _('RSI-6K Receive/ARC Switch Custom'), category = {_('RSI-6K Radio'), _('Custom')}},
        {cockpit_device_id = devices.RSI_6K, action = control_commands.Mig15_Command_RSI6K_Forced, name = _('RSI-6K Forced Mode Switch Custom'), category = {_('RSI-6K Radio'), _('Custom')}},
    }

In the DCS.log I can see several lines like 

2023-11-10 14:39:20.278 INFO    Quaggles.InputCommandInjector (Main): Detected loading of type: "Thrustmaster Virtual Game Controller (root)", filename: "./Mods/aircraft/MiG-15bis/Input/MiG-15bis/joystick/default.lua"
2023-11-10 14:39:20.278 INFO    Quaggles.InputCommandInjector (Main): --Translated path: "C:/Users/uvegi/Saved Games/DCS/InputCommands/MiG-15bis/Input/MiG-15bis/joystick/default.lua"
2023-11-10 14:39:20.278 INFO    Quaggles.InputCommandInjector (Main): ----Found merge at: "C:/Users/uvegi/Saved Games/DCS/InputCommands/MiG-15bis/Input/MiG-15bis/joystick/default.lua"
2023-11-10 14:39:20.280 INFO    Quaggles.InputCommandInjector (Main): ------Merge successful

But I only see a new axis to configure in the settings options in DCS

image.png

 and the assigned control to the axis is not moving in cockpit.

 

Edited by vgilsoler

I5 12600KF - 32 GB DDR4 - Nvidia RTX 4060 - SSD + NVME

Nadie es un completo inutil, por lo menos sirve de mal ejemplo.

 

  • 10 months later...
Posted (edited)

About the MIG15bis. Is the Flaming cliffs one the same as the separately available one?

It seems i cannot create the appropriate ...diff.lua scripts to work ok, like weapon firing and flaps with my warthogt's joystick and throttle buttons.

Some keyboard pressings don't work like LCntl_Space for the weapon cover.

BTW the Warthog's Joystick Axis controllers work OK but i cannot get the throttle to work yet.though.

(not using Quaggles yet, troubleshooting without mods first).

BTW this is all since the last update ... before all worked OK.

--------------------------------

Has anyone some diff.lua scripts for a Warthog set that work for the MIG15bis?

Edited by jackd
Posted
4 hours ago, jackd said:

About the MIG15bis. Is the Flaming cliffs one the same as the separately available one?

No. The MIG15bis, this forum, is an FF module, as you know. The MIG15bis_FC, both single or in the FC2024 Pack, is not identical to the FF module. The FC ones are more simplified in the avionics, non-clickable cockpit etc. like other FC modules. I assume you cannot tune the radios etc. I have it. Have not tried it. 

If you're trying to edit the controls for the FC module. This is the wrong forum, and you cannot expect the same level of controls to work in it.

Cheers! 

  • Thanks 1
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...