EinsteinEP

jessi1, can you post a track? Maybe we can see what's going on in your recording.

With the latch on, it's possible the laser was activated and then not de-activated, but it's hard to guess without a track. Do you have one you can post?

Mik75, I had the exact same issue on my first X52 Pro. In addition, sometimes the axes would go hard over (full left/right or up/down) even when I wasn't touching the stick. I ended up tracing the issue to to the PCB connector on the stick. Luckily, it was within warranty, and they replaced my stick free of charge.

The nose/tail setting uses both the nose and tail fuzes. If the tail fuze is set, the ballute on the Mk82AIR will be armed to deploy after release, so the N/T setting will also drop the bomb in a high-drag config.

Kellerman, Looks like a laser, but it's really an IR pointing beam. The Litening pod can produce a laser or an IR beam (or both). The NVG in the sim can detect up low wavelength light like infrared, but not the same wavelengths as the TGP designation laser.

I have the X52 Pro and it works great with A-10C. I'd say it's not much different, functionally, than the "vanilla" X52. The trick, in my humble opinion, is laying out your buttons and functions to get the functionality you need/want.

memento, Rep inbound for continuing your search and then posting your results after you found what you were looking for. Well done, and thank you!

Never too soon to start! [edit: I had posted an image I thought was a screenshot but was not. Apologies! Now, where is that foot-in-mouth smiley...]

FYI the Situational Awareness Datalink (SADL) transmits over Link16. Think of the SADL as a radio and Link16 as a set of frequencies (much more complicated than that IRL, including message formatting, timing, etc., but works for an explanation). There are many different radios that use Link 16 (The US uses the "J" messages in the Link 16 architecture, so, for US users, "TADIL J" is the same thing as "Link 16"). Situational Awareness Datalink Decent one-page summary of Link 16

Don't know about what we'll get in DCS:A-10C Warthog, but here's some additional info on fuzes: http://www.ordnance.org/fuzes.htm

Yikes! I meant to emphasize that the pods can ALSO be carried on stations 2 and 10 - this was an intentional upgrade. I don't have any literature that confirms one way or the other, but I would think stations 3 and 9 still retain the capability to carry the targeting pods, like they are carried on the A-10A+. It's entirely possible that in real-life practice it's never done, but I have no reason to believe this capability was purporsefully removed. According to this contract mod' date=' 1760 was added to stations 1, 2, 10, and 11 for the A-10C and according to this document the A-10 has 1760 capability on stations 3,4,5 and 7,8,9, so I'm confused as to which stations really have 1760 or not. Remember that MIL-STD-1760 specifies an INTERFACE: you can think of it like a specific kind of cable with a special connector on the end. Just because a station has 1760 doesn't mean it can carry and deliver weapons that also use 1760! The pylon needs to be able to handle the weight, have ejection mechanisms/cartridge capability, etc.

kM Without a mission file to look at (hint hint), I could only suggest verifying that the SAM unit was 1) not a static object, 2) active, 3) of an opposing faction, and 4) didn't require additional units in the group (e.g., search radar + launcher). I've heard that some SAM units have relatively high minimum altitude limits, which means it's possible to fly beneath their killzone, but I don't know for sure. Post the mission file here and you'll get much better (and more accurate!) help.

omgomgomgomgomgomgomgomgomg

A 2 second delay is pretty standard in pickle-release weapons (AIM-9s, CBUs, etc.). Perhaps this delay wasn't modeled in previous versions of LockOn but is now correctly modeled?

omgomgomgomgomgomgomgomgomg Can't wait!

DCS: Legend of Zelda

AP Disegnage turns off all AP channels, including damping. It is more than FD.

My $0.02USD: The Flight Director is a great tool to use to learn how to fly with the Trimmer and should be encouraged as a learning device (as GGTharos mentioned earlier). Once you get that down (and don't scoff, the Trimmer is a lot more complicated and unintuitive than people seem to realize!), you can fly smooth and controlled with the autopilot on ALL THE TIME. Personally, I leave it on when I takeoff, cruise, attack, evade, hover, land, etc. I fly without Flight Director because I prefer flight with the autopilot, not because it's the Right way. IMHO, using the Flight Directory or turning autopilot channels off enables and enforces bad flying habits. Yes, you're not going to fly perfect your first few flights with the AP fully engaged, but you're not going to get better by turning them off. If you *really* want to learn how the Shark flies, learn to use the autopilot features without your workarounds. If something weird is happening to make you lose control, ask around here: there's lots of folks who went through the same learning process and would gladly share their $0.02USD. Now, that all said, this is a game (yes, I said "game") and folks are welcome to play however they'd like. I, for one, get much more enjoyment out of learning how to fully use all the systems available, but I can see how other folks may not enjoy that challenge and encourage them to enjoy the game in whatever manner works for them.

Absolutely true! Which is why I used the USAF TO 1A-10A-1 (Change 8, dated 15 March 1988) to generate this checklist. There is a ton more info in the manual that is not (yet) in the checklist document I generated. And note that this checklist is for the A-10A, not the C. I expect there will be a lot of common items, but the checklist will need to be updated once I get more info on the A-10C. Anybody have an A-10C checklist/manual they can share?

Tangolima600, just listened to the Matt Wagner interview: I didn't know there was an AI FAC capability coming to DCS: Warthog! Way cool! I'm hope it's as awesome as it sounds! It would also be cool if something like that can get ported to Black Shark so we don't have to do the mission trigger "workarounds".

Doh! :doh: Correct attachment uploaded now.

In anticipation of DCS:A-10C, I started creating a checklist. I don't have any A-10C docs (yet!) so I started with the A-10A, but thought I'd share. A10A_startup_rev001.pdf

In DCS:Black Shark mission editor you can set triggers to request CAS support just like they were coming from an observer. Simple mission example: 1. An observer group stationary at point A. 2. An inactive enemy group is at point B, set to advance on the friendly observer once activated. 2. A trigger is set to activate enemy group once the player in Ka-50 enters a zone around the enemy. The trigger also sends the message "CAS requested at coordinates ###, target type ###, friendlies at coordinates ###". (you can download a joint pub 3-09.3 to get the full 9-line message if you want it to be by-the-book accurate) 3. Pilot Ka50 reads the message, flies to given coordinates, and opens big ol' can of whoop ass. Voila, JTAS/FAC observer in DCS: Black Shark.

CAS (Close Air Support) is a type of mission, not a piece of equipment. The Ka-50 can perform CAS missions just fine as it is now.

Still present in 1.0.2 for me. FYI - your doppler nav needs to be up and running (see third item in this post). All the speed readouts work just fine for me in 1.0.2. FYI - the ground speed readout in the hud comes from the doppler nav system (see third item in this post). Sounds like the doppler system warmup issue. I don't think it's a bug, but you have to let the doppler nav initialize before entering auto hover. Here's just one thread - there are others. Just guessing (a track would help) but it sounds like you did a cold start then immediately took off and tried to enter auto-hover before the doppler nav was up and running. The doppler nav takes about 2.5 minutes to warm up, so it is possible to complete a startup sequence and be ready to fly with no doppler nav. I don't know of any positive indication that it's working other except for checking to see that there's a ground speed indication in the HUD. This won't show up until you're in the air, though, so I still don't know of a positive indication while sitting on the ground.