Deezle

Cannot stand surround outside of games. Thankfully I really only play DCS and it doesn't need surround to work properly. You wont get away from the distortion without using the 3 screen profile (which looks much worse to me), it comes with the territory. Zoom way out to an equivalent FOV with 1 monitor and it's just as distorted. I don't even notice it anymore.

Unless you have precision guided munitions, really don't bother with anything armored. With DCS's limited explosion and damage modeling it's just not worth doing, ideally you could severely damage and disable armored vehicles with a close bomb hit, but in DCS it's either dead or alive, no in-between. With rocket pods you can do quite a number on trucks however.

How I imagine this working in practice is for the Hog driver to find a target, they'll give you the coordinates and you'll enter them in the INS. You'll then designate the target on the coordinates given and pickle. I can't wait for more INS functionality, my A-10 CDU panel is sitting here just waiting to be used :D

At least when dropping your own bomb it doesn't actually start guiding on the laser until 15s from impact, I don't imagine buddy lasing changing that.

You need to run the install Nevada command prompt. This WILL fix it, but it's another 3gb download. http://forums.eagle.ru/showpost.php?p=2574663&postcount=8

The map sits on two different grids, 37T and 38T, if you take off from one and enter coordinates for the other without first changing the grid you will find yourself with the wrong coordinates. Type in 37T or 38T and click the corresponding LSK to change the grid you're entering coordinates for. You must change the grid before entering the MGRS coordinates.

Will the reality option be ALN, ALCM, or both?

I don't have a strong opinion one way or another, but it would be nice to have more than one module capable of doing SEAD right now. I also agree that any possible implementation should be modeled realistically system-wise.

The problem is the grease they use. You can take apart and attempt to remove the tacky grease, it's quite a chore.

I think you found the wrong files. I've muted them and made them a JSGME mod and it works fine. I'll find and post the correct directory when I get home.

I'm pretty confident this is what they'll do. It makes the most sense. Not sure why this is still being discussed.

Well aware. I didn't build my custom switch panels for nothing, so I set about making it so I could use them for the time being. I've already modded the switch functions for all the modules to make them compatible with my panels, what's one more?

Yes, I've done multiple shutdowns in a session. No curves of any kind. The only problem I ran into was moving the throttle forward during shutdown would cause it to "lock up". I hit the start button, when N1 stops at 11% I move the throttle forward about half way then pull it all the way back, works every time. There is a thrust left and right mapping as well as the single thrust mapping, is the problem that you guys are mapping the wrong thrust axis?

If you place these lines in the default.lua located in the keyboard folder they will be mapable to the keyboard.

Yeah I thought about doing that one too, but I just flick the cover once and leave it up, not worried about accidentally hitting the switch in a fake airplane :thumbup:

You'll have to click the cover open.

Here they are for now. These work with 2 and 3 postion toggles, the center (or off) position of the switch is taken care of when you map the other postions. {down = 3249, up = 3249, value_up = 0, value_down =1, cockpit_device_id = 6, name = 'Selective Jettison', category = 'Armament Panel (PCA)'}, {down = 3506, up = 3506, cockpit_device_id = 11, value_up=.5, value_down = 1, name = 'Radar Azimuth Narrow', category = 'Radar'}, {down = 3506, up = 3506, cockpit_device_id = 11, value_up=.5, value_down = 0, name = 'Radar Azimuth Wide', category = 'Radar'}, {down = 3502, up = 3502, cockpit_device_id = 11, value_up=.5, value_down = 1, name = 'Radar Scan 1 Line', category = 'Radar'}, {down = 3502, up = 3502, cockpit_device_id = 11, value_up=.5, value_down = 0, name = 'Radar Scan 4 Lines', category = 'Radar'},

I've also been doing the radar azimuth and scan lines, selective jettison, ect, I can easily make them work with Warthog 2 and 3 position switches but I'm not sure how to make them incremental/toggleable for those who have other controllers. So I just posted that one for now.

Why are you pulling the throttle back so late? Push it forward to start the engine then pull it back. You also don't need to shut down to refuel or rearm, only repairing. Still no issues on my end. I also don't bother with the vent switch, I turn the battery on and start the engine, this is in 2.0.

In the mods/aircraft/m2000c/input/m2000c folder there will a folder for the keyboard and folder for the joystick. Inside each folder is a default.lua file. I'd recommend opening these in Notepad++ as to not screw up the formatting. The one in the keyboard folder contains the commands. {combos = {{key = 'S', reformers = {'LShift'}}}, pressed = iCommandPilotSeatAdjustmentUp , up = iCommandPilotSeatAdjustmentStop, name = _('Seat Adjustment Up'), category = _('Systems')}, {combos = {{key = 'S', reformers = {'LShift','LAlt'}}}, pressed = iCommandPilotSeatAdjustmentDown, up = iCommandPilotSeatAdjustmentStop, name = _('Seat Adjustment Down'), category = _('Systems')}, Delete the default keybinds so it looks like {pressed = iCommandPilotSeatAdjustmentUp , up = iCommandPilotSeatAdjustmentStop, name = _('Seat Adjustment Up'), category = _('Systems')}, {pressed = iCommandPilotSeatAdjustmentDown, up = iCommandPilotSeatAdjustmentStop, name = _('Seat Adjustment Down'), category = _('Systems')},And put it in the default.lua file in the joystick folder. You will lose this every time DCS updates. I recommend doing any mod like this with JSGME so it can be easily reinstalled after every update. I've gone ahead and attached the modded default.lua file, just replace the one in the joystick folder. default.lua

This was just covered a couple threads down from this one.. You can take the commands from the keyboard default.lua file and copy them to the joystick default.lua.

You can do it right now by copying the commands from the keyboard default.lua to the joystick default.lua.

Don't worry about it, the 2000C is quite easy to land, nothing like the Fishbed.

Doesn't the knob in the cockpit have both ALN and ALCM? Why not always have DCS assume that the plane hasn't moved since the last time it was parked and if you want the full 8 minutes put in ALN and if you're in a hurry, put it in ALCM.

IMO a 4 minute memory alignment won't be too bad, that's what most of us are used to in the A-10C.