Deezle

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?

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.

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.

You can try the setting "Synchronize HOTAS at mission start". I typically find this causes more problems though, such as the throttle being all the way forward and the stick being full forward/left at mission start, really annoying for air starts. Easiest way is to just start the mission with your throttles in the normal place then move them back into the cutoff once you hit "fly".

I can usually get the jump on Skilkas. Haven't tried SA-9. I did get a kill on an SA-8 earlier while it was surrounded by a bunch of tanks and BMPs:joystick:

So far my tactic against a group of trucks/troops/BMPs is to come in low 100-200' at full burner and drop a pair of snake eyes ~100' early or so. It's so fast they don't even have time to shoot at you, including manpads, and the bombs usually take out at least most of the troops.

I figured if OP didn't know that the engines weren't started electrically he might not understand what bleed air means. Compressed air (which it technically is) was a simplification.

The APU starts the engines with compressed air.

You're not using the "3 screen" profile, are you? Mines runs fine.

Servers can limit what you can put on your plane. Have you tried it in single player?

HEAT would be neat :)

It always worked fine like that, the green vehicles on a white background is a lot of contrast.