Meyomyx

Check your pitch axis dead zones. You can often allow engagement by just touching the stick in the pitch axis to centre it again. Try increasing the dead zone by 1. My Warthog needs a deadzone of 3. Other sticks may need more

OSB’s .... or by selecting the profile “on”, all 4 display white in the status page. I cycled through the master modes as well. By the look of it, I could have tried an airborne realignment of the INS although I'm not sure what would have made this necessary. I'll keep experimenting

Thanks for responding! I tried this (by default) and after trying to wake them up, I turned 180 degrees to re-attack the target (when the images were taken). I also tried re-loading the weapons.

I'm not 100% sure this is a bug but These GBU 38's were ready. A target was designated and displayed green. Then I decided to tweak the target point. From then on, the Profile page shows green but all the stations show safe. I can't seem to find any way to change this. They're permanently stuck in "safe" mode but ready. I made no attempt to release the weapons so it isn't a "quick pickle". The track file would be too big ....

Familiarising myself with the A10 at last. After working out the full alignment requirement (and having success with deploying the GBU38), I now discover that a "long " press is required to pickle so I have a couple of unusable GBU38's on board. Cool - all part of the learning process! However, I now seem to have 2 GBU38's that I have "trashed" and 2 that report as being "Ready" - yet their status is coloured white. I can't seem to find out why (thus far). I've tried re-creating a profile and re-loading the weapons. Hmm. Still white. Anyone know why? I'm sure it's something simple. Back to scouring the manuals/guides :)

Maybe I'm missing something but there seems to be no difference in the F2 View Effects settings ....

Please consider installing documents to .../<user>Documents/DCS/<module> (or similar). A single library would be handy rather than having to find them in various subdirectories

Please introduce an amount of damping to the exterior camera movement. Zero damping looks horrible!

As your post suggests, rearward firing weapons would have to initially cope with travelling at -250 knots at release before having to accelerate to a positive velocity. Challenging ... but there are some clever people out there! I'm not sure that hoping your attacker will fly into your "passive" weapons would work ;) A10's are never really expected to engage air targets. That's what CAP is. Sidewinders were only fitted as a last ditch defence in case a lone wolf manages to get past. Your chances of winning that one are not good. I'm not a hog driver IRL but I understand the HOTAS is well though of. I suspect the variety of different methods reflects an airplane with a long history undergoing many systems upgrades. Your next generation aircraft have a good deal more systems integration. https://www.digitalcombatsimulator.com/en/files/573565/ ... might help Also, check out the A10 episode of The Fighter Pilot Podcast

Frequently, I'm unable to move the targeting pod track point. It merely flashes. It often seems to happen when a weapon (JDAM) has been released ... but not yet impacted. It seems as though the point has been "hijacked" by the weapon. After impact (it seems) the target point can be slewed as normal. On other occasions it works as expected in that you can slew the target point between the release of each GBU38. Obviously you can undesignate and re-designate but often you've spent 20 minutes searching for the ground target in the trees! TGT.trk

I have TrackIR but don't seem to have any problems of that kind. As an aside - if you plug in TRackIR after DCS has started (so it doesn't work), you can reactivate it again by unplugging and re-plugging a DIFFERENT USB device. Any one. I don't know why but it works. In your instance you might need to re-plug TIR first I guess, but then replugging any other USB device will get your head tracking back without having to restart DCS.

It might be me ... but I can no longer invert the mouse zoom axis. For me it now operates in the opposite sense. Ticking the "invert" option makes no difference. Oddly, with the Super Carrier Alt F9 view, the zoom operates in the correct sense .... but not in other views.

Windows HID device drivers pick up on any standard analogue input (joystick axes) you plug in. It will do it's best to assign any other axes and buttons. If your joystick has a wide range of buttons/controls though, the driver provides the correct allocation - and with the associated software usually the ability to tune/amend/modify individual switches and controls instead of the default behaviour. In general, if it works, you can leave it alone. If there are drivers, however, it's a good idea to use them.

Not really a lot of point. Deploy weapon. Game ends. Alternatively - weapon deployed against you. Game ends. I think you'll find that's the reason that ED have repeatedly said it will never be modelled

It's a mistake to try to assign too much to HOTAS. Guard your buttons and switches and use them strictly for things you NEED to have as HOTAS. For example, you don't need a switch for gear. It's a flipping big lever on the panel. Simply use "G". Then you can map a LOT to keyboard. You can map the entire UFC to your numeric keypad, Use Insert/Delete/Home/End/PgUp as line selection 1-5 and PgDn as "Enter". Map common MFD buttons to sursor arrows (Left = button 18L, R = button 18R. Up = "Stores" Map heading bug to Z and X, Course to A and S. Etc. So HOTAS is just that ... and your keyboard becomes an easy route to UFC functions etc. If there's a switch or button you use only rarely, leave it as a mouse click. There's no point in wasting a switch for OBOGS for example. No point in assigning a switch to APU - you use it once at the start of a flight.

Yes, HSI, SA and AMPCD all reflect the same range. I have a feeling that's the way it is although I would agree that individual range settings would be useful

When "Auto" waypoint mode is selected, it will always make WPT 1 the next waypoint, wherever you are in the sequence. Typically I'll deselect "Auto" at a target area to loiter. If you then manually select the next waypoint, all is well and "Auto" re-selected. At the next turn, WPT 1 is always the next waypoint. WPT bug.trk

There's a massive thread I posted a while back. It seems to be wind. There's a huge discussion about "compensating" for the effects of wind, but the weapon should track the laser, whether calm or 150kts of wind. The trouble is it's always when you have a giant track file .....

Same mission flown 3 times. Every pair of 12's missing by 100-200 meters. All tracking the laser to the ground. All 3 missions a waste of time. I've posted before- there's definitely something wrong with ... well at least GBU12's. Precision munitions in this instance are anything but.

Be quite useful in real life too :smilewink:

Heading and earth rotation. but that resultant movement could be replicated at any longitude. Imagine 3 aircraft all pointing due North. One at the North pole, one at the Equator and one at the South pole. The gyros on the one at the north pole would experience "yaw left" with no heading change. The one at the equator would experience"roll right" with no heading change and the one at the South pole "yaw right" with no heading change. So there is only one point of latitude that will give a certain combination of gyro inputs. BUT, if you think about it, that could happen on any line of longitude. Maybe it would be quicker with a clock and a sextant ;D

With the stick hidden, the hotspots that would be there with the stick visible are present, interfering with the ECM rotary hotspot. Conversely, with the stick visible, the HOTAS hotspots are missing Stick bug 1.trk

Even the Warthog can bust the dead zone. I use 2 but even then, on rare occasions it needs a tiny waggle to get it in the zone.

:smilewink:I'm not sure you should be anywhere near the brakes before or during a cat shot. Unless you want the nose gear removed....