531-Ghost

Not that you NEED it, but, in Control Manager, it can be done ;)

Okay, let's see Autohotkey or Joy2Key do this: // CMS Script File // Gain and Response // Trim & Scalling //-------------------------------------------------------------- %define jsy js1.a3 // the input axes %define trim_value a1 // the value of trim %define dvy a2 // The deviation of the stick from the center. %define mult3 a3 // multiplier for x^3 %define mult1 a5 // multiplier for x %define ability_control b1 // The ability to control the stick // script //-------------------------------------------------------------- if (firstscan) then trim_value = 0; // the value of trim = 0 mult1 = 4; // multiplier for x. By default 1:4 ability_control = true; // the control stick is allowed mult3 = 128*128*128; // the calculated ?ultiplier for x^3 endif // if( ability_control and (not js1.b2) ) then // if B2 is not pressed and allowed control... // ... Calculated output value axis// if ([jsy >127]) then // For the first half dvy = jsy - 127; // The deviation of the stick from the center for the first half cms.a1 = 127 + (dvy*dvy*dvy*(127-127/mult1+trim_value))/mult3 + dvy/mult1 + trim_value; // polinom else // ...and for the second half... dvy = 128 - jsy; // The deviation of the stick from the center for other side cms.a1 = 127 - (dvy*dvy*dvy*(127-127/mult1-trim_value))/mult3 + dvy/mult1 - trim_value; // polinom endif endif //------------------------------------------------------------------- sequence // calculating the Trim values when the Button 2 is pressed wait( js1.b2 ); // ...when the Button 2 is pressed trim_value = cms.a1-127; // ...calculating the Trim values ability_control = false; // Prohibit the control stick endsequence // // ...until... if ([jsy==127] OR [jsy==128]) then ability_control = true; endif // ...stick to return to center //-------------------------------------------------------------------- sequence// reset trim wait( js1.b3 ); // ...when the Button 3 is pressed trim_value = 0; // reset value of trim endsequence // Gain control---------------------------------------------------- sequence // Decrease gain to 1:1 wait( js1.b14 ); if ([mult1>1]) then mult1=mult1/2; endif endsequence // sequence // Increase gain to 1:8 wait( js1.b16 ); if ([mult1<8]) then mult1=mult1*2; endif endsequence endscript // Successful flights! Discuss... :)

Not always. Depends on how you'd like to program the mini-joystick in Control Manager.

The ProThrottle has been doing that for years (no hack needed).

You've obviously never programmed in, or used Control Manager v4.55 :smilewink: "Fixing" software to be as good as Control Manager, you'd need another Bob Church :noexpression:

VKB, Still not nearly as programmable. Then again, neither are any other HOTAS, Throttle Quadrants, Pedals on the market today. CH Products were the first with FFB. Alas, 'tis no more, and I said "most". Unfortunately, there have been no new hardware since the Eclipse Yoke.

You sir are delusional if you think the average flight sim enthusiast is going to shell out that much cash for a hobby. Unless they've got nothing better to do with their cash. Not to mention, still not nearly as programmable as CH Products using Control Manager v4.55.

Most of what you are looking for... Can be found here. Granted, no fancy lights, bells, or whistles, but, still to this day the most programmable bullet proof HOTAS out there. IMO.

Still a work in progress, but the keys/macros are there... Enjoy! Copy of KEYS.zip

Now, I have found 2,444 assignable keys/macros.

No need, after the last patch to v1.5 all modules are now installed.

LOL I forgot about LWIN and RWIN and their combinations! Still a work in progress. All I'm doing is creating the list of available keys/macros in the game. If you'll note, I've written the keys/macros in Control Manager speak. I'll import the data into notepad to create a Command File to be used in Control Manager.

Well, through the magic of MS Excel I put together a spreadsheet of ALL 1235 available/assignable keys/macros that can be assigned in the game. Errrr sim. Of course, your mileage may vary.

DCS v1.5 Autoupdate/Logs attached Logs.rar autoupdate_log.rar

Thanks, will do when I can. In the mean time, here's what I'm seeing in the Module Manager: DCS v1.5: DCS v2.0:

Sorry, not FC3 either. ;) Purchased the F15C , Su25 and Su27 during the Christmas Sale.

So was it the Module Manager, or the F15C that was the third party project? Answer: F15C

Only this time it's the F15C :doh:

managing all modules. Don't get me wrong, I appreciate the help in that thread, but, just thought if the Module Manager were going to manage modules, it would manage all purchased modules. Obviously due to SkateZilla's tutorial, I'm not the only one affected. Bug? Glitch? Dunno, just reporting.

Fixed! Thanks Skatezilla!

Pressing ALT ENT makes the menus, un-clickable.

No joy, but thanks. This after a complete un-install, and re-install of the current 1.5 version. So far, un-playable. Edit: The weird part is, screenshots of what I'm seeing show the complete screen, not what I'm actually seeing (upper left corner of the game).

Having the same issue here after the latest update. Tried the ALT ENT and it got the view-able area to what it should be, but, none of the menus are clickable...

AH! Thanks! :thumbup:

Yes, I'm aware that this is the A-10 C portion of the forum/s. However, there is no A-10 A portion to address this. Taking advantage of this weekend sale, I purchased the, I'll call it a 4 Pack. It included the A-10 A, F15, Frogfoot (Su-25) and Su 27. As you may know the A-10 A is pretty minimal in the cockpit compared to the A-10 C as well the HOTAS. I've worked up a Command File for the A-10 A and will be for the rest as well. Now, it's a matter of assigning what to where... I've looked and can only find references to the A-10 C HOTAS. :helpsmilie: