Deezle

This has always been iffy with all modules with any type of toggle input. DCS has a hard time recognizing switches that are already on at the start of a mission, that includes WH throttles in the cut-off position. I dunno if it's a bug so much as it's "just the way it is". It will also forget they're on if you adjust controls in the middle of a mission, always been that way. You can try the "synchronize HOTAS controls" option, but I've found that causes more problems.

IIRC, the newer A-10s have a markpoint delete button on the CDU. I'm not sure why our upgrade doesn't have it. Perhaps Snoopy could chime in if ours should have it?

Yeah, in the past I used to run a mod that muted it. Now it's tolerable.

Except there's at least one person in this thread that just tested this and found that isn't the case. Cool down did not help laser longevity.

I've noticed this as well and wasn't sure if it was intentional or not, thinking that a very "hot" spot would wash out the rest of the "FLIR" image. I will give this a try, thanks!

It was posted by someone else that the laser burns out after about 20 minutes of use.

FWIW, you can add these yourself. While I don't cover axes specifically in this tutorial, the same principals apply in creating your own axis binds. These are the axis binds I've added to mine. {action = 3009, cockpit_device_id = 49, name = 'Formation Lights'}, {action = 3001, cockpit_device_id = 49, name = 'Engine Instruments Lights'}, {action = 3002, cockpit_device_id = 49, name = 'Flight Instruments Lights'}, {action = 3003, cockpit_device_id = 49, name = 'Auxiliary Instruments Lights'}, {action = 3005, cockpit_device_id = 49, name = 'Flood Light'}, {action = 3006, cockpit_device_id = 49, name = 'Console Light'},

They seem to work fine at night. They are no longer visible at all with any daylight like they used to be (may have been a problem for months now in the A-10, as I've been away).

This started to get worse in the A-10C a couple years ago. Now in the II, I often get a gimbal roll notifications as I'm turning towards the target, but when I roll out for the attack, it usually goes away and all is well.

Completely unacceptable. Just asinine. I have fun with the module and it has it's problems, but for something like this to go on for 3 years without an update is a bridge too far.

The order numbers started at 1000, so 1000 sold which is still quite awesome :thumbup:

Thank you! I had downloaded the calibration tool earlier and thought it was for both the stick and the throttle, and since I don't use the TMWH base anymore I couldn't use that program. But it turns out it was only for the stick. Finding the correct throttle calibration tool through google was a lot harder than it should have been, but I now see it's also on the DeltaSim website :doh: Anyways, the thumbstick now properly reflects the full range of motion. Now if I could just get the junk modern 360 controllers to do the same :rolleyes:

EDIT: Disregard, works great!

Got mine yesterday but I've been fighting a broken computer so I haven't had a chance to use it yet, looks great though!

Mine is #1849 and I got a shipping notification today.

I made this video a while back that explains how.

I'm aware it's not there by default, but is possible to add any clickable cockpit button or knob to the binding list, as LeCuvier has shown before I was able to get around to it. Do note you will need to make this a mod and apply it after every update, otherwise it will be deleted. I made a video a while back explaining how to add missing keybinds, the process for adding missing axes is very similar as well.

Which module? It's possible to add axis bindings to all the modules.

Config/view/Server.lua. In there you should find min/max FOV for aircraft that you can change. CameraViewAngleLimits = {20.000000,140.000000}, Find those and change 140 to 160. Keep in mind, it's possible for multiplayer servers to override this file (most don't even know they're doing it) and you will be stuck with default FOV. One of the reasons I finally went away from a triple screen in favor of an ultrawide.

I see this was moved to Huey forum, without acknowledgment. The whole reason it was posted outside the Huey forum was the get attention since ED and BST are ignoring it. Whatever.

Yup, this is clearly tied to vertical pixel count. Explains why 1440p and 4k makes the displays fuzzier, and common stacked monitor exports are even worse. Now if only ED would finally acknowledge this.

My in game displays are fine with this fix, however my values are tweaked from that post. Also because my main resolution is 3440x1440, the lines by default are fuzzier than a normal 1080p monitor, so it's adjusting my main display to be more normal, so I guess if your main display is starting from normal it's adjusting them away from that, if that makes sense. I do agree this is fully ED/BSTs fault, considering no other aircraft exports behave like this. So far they've completely ignored this issue.

This is a well known problem with the Hornet since launch. Has nothing to do with screen calibration. The Hornet handles displays completely different from all the other aircraft, really large resolutions and display exports result in fuzzy displays. Fix can be found here. https://forums.eagle.ru/showpost.php?p=3555460&postcount=117 https://forums.eagle.ru/showpost.php?p=3555530&postcount=118

This right here. You can make your own using a combination of the the default.lua and clickabledata.lua files. I made a video a couple years ago that explains this a little.

I do find it odd that the RWR doesn't show relative lethality like most of the other Western jets, it's useless for making any judgements of threats. I guess you're wholly dependent on AWACS/SA Page/Radar.