Jump to content

Recommended Posts

Posted
I wouldn't know what to do with those Lua files. You should put them into a OVGME Mod pack and offer them as a download. 
Now, that's where Quaggles and Munkwolf's repository comes in handy. You just copy the files to the correct place!

Sent from my SM-A536B using Tapatalk

  • Like 1
Posted
I don't use their software. 
Yeah, I know. We have established that before. While you should look into it. It's not even software per say. It's just a bunch of pre-made Lua files, so you don't have to mess with it. And only one file to copy/deploy after every update.

Sent from my SM-A536B using Tapatalk

  • Like 1
Posted (edited)

"The correct place"............ If I were good at finding the lua files I probably wouldn't need the other two software items. I could just do it my self and create a mod I could install and uninstall. 

The controls he has done new lua for are not really a problem with me, I really want the fuel selector switch to work as the Jug and mustangs does.

 

 

Edited by _Hoss

Sempre Fortis

Posted
If I were good at finding the lua files I probably wouldn't need the other two software items. I could just do it my self and create a mod I could install and uninstall. 
 
That's the whole point. You don't need to make mod to install after every update. And you don't have to update said mod every time you need something new. You just apply the one mod after update, Quaggles. The rest is kept in Saved Games. I give up.

Sent from my SM-A536B using Tapatalk

  • Like 2
Posted (edited)
2 minutes ago, MAXsenna said:

That's the whole point. You don't need to make mod to install after every update. And you don't have to update said mod every time you need something new. You just apply the one mod after update, Quaggles. The rest is kept in Saved Games. I give up.

Sent from my SM-A536B using Tapatalk
 

Thanks for the input, but like I said, the Hog as is, isn't that bad, and his fixes aren't a niggling necessity for me. 

Edited by _Hoss
  • Like 1

Sempre Fortis

Posted

Show pilot needs to be mappable to controller.

"You see, IronHand is my thing"

My specs:  W10 Pro, I5/11600K o/c to 4800 @1.32v, 64 GB 3200 XML RAM, Red Dragon 7800XT/16GB, monitor: GIGABYTE M32QC 32" (31.5" Viewable) QHD 2560 x 1440 (2K) 165Hz.

Posted

System Specs:

Spoiler

📻Callsign:Kandy  💻Processor:13th Gen Intel(R) Core(TM) i9-13900K - 🧠RAM: 64GB - 🎥Video Card: NVIDIA RTX 4090 - 🥽 Display: Pimax 8kx VR Headset - 🕹️Accessories:  VKB Gunfighter III MCG Ultimate, VKB STECS Standard, Thrustmaster TPR Pedals, Simshaker JetPad, Predator HOTAS Mounts, 3D Printed Flight Button Box 

📹 Video Capture Software:  Open Broadcaster Software (OBS), 🎞️ Video Editing Software:  PowerDirector 35

 Into The Jungle (MP Mission)  F18: Scorpion's Sting  Apache Campaign - Griffins  Kiowa Campaign - Assassins 

 

Posted (edited)

Posted a question in here about not able to key bind the auto start and auto stop, then found this dedicated F4I-1D section…

 

Edited by gdx65

GDX65,

AMD Ryzen 9 9950X3D, ASUS TUF Gaming B650-PLUS WIFI, RTX5090FE, 64GB Kingston FURY Beast RGB DDR5-6000 -32GB - CL36 - Dual Channel (2 pcs), 2 x Crucial T700 SSD - 2TB - M.2 2280 - PCIe 5.0, Quest 3, HOTAS Thrustmaster Warthog & Pendular rudder. - Flight sims, DCS and IL2

 

Posted
14 hours ago, gdx65 said:

Posted a question in here about not able to key bind the auto start and auto stop, then found this dedicated F4I-1D section…

If you want to bind it to a button on a game controller, you need to make a very simple edit in the file "default.lua" under "disk location:\Eagle Dynamics\DCS World\Mods\aircraft\F4U-1D\Input\joystick" by copying a line from the "default.lua" under "disk location\Eagle Dynamics\DCS World\Mods\aircraft\F4U-1D\Input\keyboard" and pasting it into the file under "...\joystick". Since most people don't want to get into that, I won't go into more detail now.

  • Like 1

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Posted (edited)

Hi and thanks. I am familiar with editing the .lua file. Just did not think about that as I am not an expert into this type of details but can edit with confidence if guided.

Edited by gdx65

GDX65,

AMD Ryzen 9 9950X3D, ASUS TUF Gaming B650-PLUS WIFI, RTX5090FE, 64GB Kingston FURY Beast RGB DDR5-6000 -32GB - CL36 - Dual Channel (2 pcs), 2 x Crucial T700 SSD - 2TB - M.2 2280 - PCIe 5.0, Quest 3, HOTAS Thrustmaster Warthog & Pendular rudder. - Flight sims, DCS and IL2

 

Posted
12 hours ago, gdx65 said:

Hi and thanks. I am familiar with editing the .lua file. Just did not think about that as I am not an expert into this type of details but can edit with confidence if guided.

These are the two lua lines for auto-start and auto-stop:

{combos = {{key='Home',reformers={'LWin'}}}, down = device_commands.AutoStart, cockpit_device_id = devices.AUTOSTART, value_down = 1.0, name = _('Autostart Procedure'), category = _('Engine')},
{combos = {{key='End',reformers={'LWin'}}}, down = device_commands.AutoStop, cockpit_device_id = devices.AUTOSTART, value_down = 1.0, name = _('Autostop Procedure'), category = _('Engine')},

For general guidance on the subject, see here: https://forum.dcs.world/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4646929_menu

LeCuvier

Windows 10 Pro 64Bit | i7-4790 CPU |16 GB RAM|SSD System Disk|SSD Gaming Disk| MSI GTX-1080 Gaming 8 GB| Acer XB270HU | TM Warthog HOTAS | VKB Gladiator Pro | MongoosT-50 | MFG Crosswind Pedals | TrackIR 5

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

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