Jump to content

Recommended Posts

Posted

Is the solution @scoobie provided still the answer?

I'm having the same issue with having to chase the trim in pitch. I've checked the file Scoobie referenced but I can't find the relevant line. Just wondering if the file structure has changed since this thread began? I'm on Steam and not the stand alone version.

File attached

Cheers

default.lua

Posted

Yes, the edits still work fine in 2.7.8, but the file you attached is certainly not Mosquito one. Double check - you're supposed to edit the files located in \Mods\aircraft\MosquitoFBMkVI\Input\MosquitoFBMkVI\joystick (or keyboard, depending on which one you use for trims operation) folder.

i7 9700K @ stock speed, single GTX1070, 32 gigs of RAM, TH Warthog, MFG Crosswind, Win10.

Posted
12 hours ago, Art-J said:

Yes, the edits still work fine in 2.7.8, but the file you attached is certainly not Mosquito one. Double check - you're supposed to edit the files located in \Mods\aircraft\MosquitoFBMkVI\Input\MosquitoFBMkVI\joystick (or keyboard, depending on which one you use for trims operation) folder.

Sorry, I should have been a bit clearer. The file I attached is for the A10C II, I don't have the Mosquito module. Is the lua file edit not possible for other modules?

Thanks for the reply Art-J, appreciated.

Posted

The LUA edit @scoobie provided still works for the Mosquito. It works generally for modules where the line of .lua code for the trim command has something like "value_down = 1.0". In the A-10C (both versions) that's not the case. If you have questions about the A-10C please post them under the related sub-forum, "Controller Questions and Bugs"

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
21 hours ago, LeCuvier said:

The LUA edit @scoobie provided still works for the Mosquito. It works generally for modules where the line of .lua code for the trim command has something like "value_down = 1.0". In the A-10C (both versions) that's not the case. If you have questions about the A-10C please post them under the related sub-forum, "Controller Questions and Bugs"

Thanks LeCuvier.

I've played around a bit with the controls and found a deadzone of 4 and a curve of 20 seems to help a lot. No idea why as my simple brain doesn't understand what curves do. So I'll just accept it as a fact 🙂

  • Recently Browsing   0 members

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