gulfcoastfella

So I learned something about CH's Control Manager software when I was trying to get this all to work correctly. Apparently inverting an axis in CH Control Manager makes it so that the axis is inverted no matter what changes you make in DCS's Settings. That is to say, once I had inverted the axis in CH Control Manager, my throttle axis in DCS would be inverted whether I checked DCS's Invert Axis box or not. Checking the Invert Axis box in DCS Settings did nothing to change whether or not the axis was reversed. I had to go into CH Control Manager and un-invert the axis. Only then would DCS allow me to work with the axis. CH Control Manager is a finicky piece of software. Through all of this, I discovered that if I make changes to the CH profile in CHCM and then close it, then if I want to open CHCM again and make more changes, the only way to keep CHCM from crashing when I reopen it is to restart my computer first. This is pretty annoying when I'm trying different settings to get something to work.

Hey guys, thank you for the ideas. Frederf, I followed your advice and loaded up Instant Action, Take Off, and noticed that when my HOTAS throttle handle was all the way back, the in-game throttles were all the way forward. I never would have suspected that, since the axis assigned to the throttle in Settings showed a maximum value when the HOTAS throttle was all the way forward, and a minimum value when the HOTAS throttle was all the way back. Those DCS control curves are just this side of worthless. I worked for a while to get the curves into that state, only to find out now that the curves don’t mean much just to look at them. I’m tired of fighting with the software tonight, so I’ll try to pick this up again tomorrow or the next day. Thanks again.

I'm trying to learn how to start the A-10C from cold and dark. Everything's going fine until it's time to ignite the engines. I've followed all the items in the checklist, and when I press RALT + Home or RCNTL + Home, nothing happens. I double-checked that those keyboard commands are mapped to the engine ignitions in settings, and they are. I've also verified that in Settings > Misc., the HOTAS controls are not mapped to the cockpit controls at startup. Can someone help me figure out what I'm doing wrong?

That worked; downloading the CHCM drivers in Mapped Mode got DCS to recognize the controllers, and now I’m able to reverse my throttle axis, solving my original problem.

I read somewhere online that DCS only recognizes CH controllers through CHCM if they’re in Mapped Mode; DCS apparently won’t recognize controllers in Direct Mode. I’ll see if this fixes my problem in a little bit when I finish breakfast.

OK, I finally got CH Control Manager behaving correctly. I had to disable my antivirus when installing the CH software. Now I'm able to reverse the Pro Throttle axis in CHCM, but the new problem is that DCS doesn't see any of my CH controllers. They're visible in Control Panel, in the 'Device and Printers' screen, but for some reason, DCS just isn't seeing them.

I used to have CH Control Manager installed, and I probably had the Pro Throttle reversed there. CH Control Manager started crashing every time I tried to download a map, though, so I uninstalled it. If I uninstalled CHCM while the throttle axis was reversed in the map, would that cause the throttle axis to be permanently reversed in Windows? I tried reinstalling CHCM just this morning in an effort to see if I could fix the reversed axis, but it's still crashing whenever I try to download the fixed map. I'm under the impression that CH no longer provides support for CHCM, which makes me assume that it's becoming less and less agreeable with Windows as time goes on.

Here's a screenshot of my throttle's 'Axis Tune Panel'. In it, you can see that both the input and the curve are reversed, which results in no net change. The screenshot shows my throttle in a low thrust position.

I'm trying to use a CH Pro Throttle for thrust control in DCS. I've set the slider axis as my axis of choice for the thrust in DCS options, but no matter what I do, pushing the throttle forward drops the thrust to 0%, while pulling the throttle back raises it to 100%. I've tried both checking and unchecking the 'slider' box, as well both checking and unchecking the 'invert' box. Nothing works so far. I even went so far as to set custom control curves. This almost worked, but as the curve approached 100%, it dropped back down to 0% again, so this isn't a workable solution. Any help you can provide would be appreciated.

It’s been a while since I spent any time with DCS. I decided to check in on the DCS store, and upon clicking on several aircraft’s product pages, discovered that they’re still listed as being Early Access. The F-16 makes some sense as it only recently became available. I thought, though, that aircraft like the F-18, the Mirage, and the F-14 had been out for a while. Has Eagle Dynamics released any info about how long we can expect products to be in Early Access?

I appreciate your quick replies. Thanks hornet1a and Rudel_chw. :thumbup:

Hi, I've got the FC3 module, but training for the A-10A is not included. If I buy the separate A-10A module, I know it'll be the same model, but will the separate A-10A module include training? Thanks, Chris

I think I've figured out the problem. Is the MFD output normally rendered using the graphics card? If so, that would cause problems for a USB driven monitor like mine. My USB monitor, and I assume all USB monitors, can't utilize the graphics card resources as they're run from the CPU and not the graphics card. I'm picking up a DVI/VGA monitor to see if I can get better results by running it directly off my graphics card. If I get different results, I'll post it here.

I tried exporting the left MFD to the touchscreen at 512x512, with the gauge resolution also set to 512x512. This didn't help matters much at all, except for a small improvement due to the image simply being bigger.

To clarify: should I change the gauge resolution in the options menu inside A-10C, or should I change the export resolution in the .lua file?

Well, actually, I'm not spreading an MFD over the entire touchscreen. I believe the left and right MFDs are each being exported at a resolution of 384x378. I am, however, displaying it at a non-standard gauge resolution (I assume when you mention render rate for the MFD, you mean the display resolution for cockpit gauges? If that's not what you're talking about, describe what you are referring to.) Thanks!

Hi, I've got a higher pixel density on my 10.1" 1024x600 touchscreen monitor than on my primary 24" 1980x1200 monitor. When I export the A-10C MFD display to the touchscreen, though, it looks worse than the smaller rendering on my main monitor. Is this because the touchscreen can't use my graphics card for rendering, since it's a USB monitor?

I've got it working! Thanks a million guys. :pilotfly:

Thanks a bunch guys. You were a huge help!

Is there a thread that details how to modify the lua's to do this? Can you post your modified lua file(s) so I can see what you did? Any help you can provide would be great!

Hey, I've performed several searches on the input/output forum to learn how to export mfd screens using the A-10C .lua files, but all I can find are .lua files that were modified using the beta releases of A-10C. Question: Can anyone tell me how to export mfd screens using the release version of A-10C? I'm assuming my 10" touchscreen is positioned at the bottom right of my main monitor. Any help I can get would be awesome guys! Thanks. P.S. Sorry for the noob question, but how do I find out which version of DCS A10C I'm running?