Gliptal

Then you're most probably too wide or too high (can't remember if there's a height trigger as well) in the pattern. Make it a tight racetrack pattern, not a typical VFR pattern; immediately turn at the end of the runway, and fly over the small village at the East of Vaziani when opposite the runway heading.

I'm quite convinced it's an issue with 1.5.5's AI. Operation Piercing Fury is having similar problems with wingmen not starting their engines or not taxiing. How close were you to lead while taxiing? Try keeping your distance a bit more. Is the last dialogue you're hearing before the touch-and-go or before the second full-stop landing? In the former case you're probably too wide with the pattern.

Some AI taxi issues were introduced in 1.5.5, the campaign was somewhat tested on that version but those bugs are quite hard to replicate. What do you mean "everything broke? Are you flying the pattern as per diagram? Would you mind sharing a Tacview recording?

Make sure you're really sticking to the flight plan, don't cut corners. At WP2, you should have an F-10 menu option about being on station. Does that appear?

Future Nevada DLC Campaign by Baltic Dragon previewd by Bunyap:

I know exactly the feeling. :joystick:

Probably better to open a new thread in this subforum for each bug. This may sound stupid, but if I remember that correctly the switch has three positions. Have you tried all three? Should be tied to a cockpit action, I never recall having the issue.

Are other modules working fine?

Did you fly the pattern correctly? You should have heard some chatter with ATC while turning on final. If not, you probably went too wide and missed a trigger zone. Keep the briefing images close, the last one shows a couple of references for the pattern; they're also available on the kneeboard. For everyone having problems, consider using Tacview and posting an .acmi file as well: I'll take a look and see what is wrong. It's easier to spot issues that way.

Since a few updates ago there should be no need to first select a radio and then comms. If I had to guess it's probably an issue with the triple monitor setup: try and revert to a single monitor and see if the issue persists.

Yes keep the distance: it's mentioned either in the campaign notes, in the briefing, or by the IP in the mission istelf.

BMPs used to be more effective than Shilkas, but they toned them down lately. Other than ZSU I can't recall there being anything.

What stations are you releasing from?

No, although it has a few blind spots.

What happens with two consecutive launches at less than 10 seconds apart? Are two lines drawn, or does the second launch override the first one visually? Also, why was a line chosen instead of a symbol like the A-10C does?

I also can't recall ever having an MWS launch from a friendly Maverick, which is strange since it detects ground ATGMs as well. If I had to take a guess, the MLWS is notified you just launched a Maverick by the IFFCC and ignores any contact within a set of parameters that identify your own launch.

Since I saw an influx of new pilots lately, I thought about bumping this thread. Having a custom cartridge has always helped me immensely (especially with countermeasures and TAD).

Right sorry!

That's correct. The current SOI is generating the SPI at all times. This is cause of confusion for those that approach the concept, since it's common to believe a SPI is a fixed point in space and time (e.g. "setting the SPI" with the TGP and expecting to return to it after a slew).

Maybe? You say SOIs are the HUD and the two MFCDs, and SPIs are TGP, MAV and so on. Actually SOIs are those I listed, and SPI is always a 3D point in space. For example, the TAD hook symbol is neither the SPI (not unless you count inference) nor a SOI. The TAD is SOI in that case, and the 3D point the hook references is the SPI.

@twistking: I think we're delving more in IRL versus simulation here, so someone like Snoopy or Eddie would be better indicated to answer. Here's what I know: Unless the mission is flown against pre-planned immobile targets (and that would be a strike mission, something other platforms do better), the flight plan is more of a rough indication rather than a structured set of WPs. In CAS situations and even more killboxes A-10s would just enter the general area and then switch to some remarkably complicated attack run patterns, foregoing any need for multiple WPs. Visual acquisition is also more common than TGP usage, since there are no limits tied to monitor resolution, FOV, situational awareness, and so on. I expect real flight plans that don't involve some fancy NOE stuff to be takeoff airport, navigation to target area, target area, navigation out of target area, landing airport. I'd be surprised to even see approach waypoints, since IRL ATC is much more prevalent. I believe IRL the current suite has more complex and versatile functions to save waypoints, flight plans, markpoints and so on. That's the way to do in the sim. Another solution could be to place a WP in the target's general area, and use the TGP to find it and aim the JDAM; or get the coordinates from elsewhere (JTAC, FRAGO) and directly drop a bomb on them, skipping the mission editor part. Since JDAMs are really different in reality to what we have in DCS, real procedures are quite different. If I had to take a guess they'll probably load the coordinates in some special WPs in the cartridge, and then have those WPs transferred to the bombs' guidance system at some point during the flight.

SOI stands for Sensor Of Interest, there's no Object there. :D Besides, that's what I wrote, HUD A-G and HUD A-A are seen as two different SOIs, which accounts for the AIM-9 in the second case. It also seems like you are confusing SPI (the 3D point your SOI is looking at) and SOI, the source of the SPI. That's why the MFCDs aren't SOIs, they're not producing the SPI directly but are rather showing the sensor (e.g. the TGP) that is producing it; the HUD on the other hand "directly" produces the SPI. A source of confusion is the HUD indication in the lower left being not the SPI but rather its source, although it's usually referred I believe somewhat incorrectly as "setting your SPI to". If you ever have the opportunity of taking a look at the real -1 for the C you'll find confirmation.

These are the defined Sensor(s) of Interest: - TAD - TGP - HUD A-G - HUD A-A - MAV Here's hoping I don't get Swatted.

Sure! I'll be using the DDM always anyways, so having it a default ON optional OFF is better as far as I'm concerned. I was speaking more on the behalf of those that see it as an unrealistic addition.