Ballinger French

Hi Ian, I've now managed to get a ATGM Stryker to work with IR pointing, but like you I've no real idea why one mission works in particular whilst others do not. Thank you for uploading your working mission! I will look at your .miz file to see if I can find some common ground.

Well, the good news is I finally got the Predator to IR mark a target for me. Nighttime target designation is one of the more cooler things you can do in DCS IMHO. Not having any luck with any of the ground vehicles at night though, including either version of the Stryker, unfortunately. Perhaps, as you say Ian, getting all the JTACS and targets situated in the right alignment/range is critical here. The Predator is awesome though, especially with EPLRs and unrestricted datalink range - ground JTACs require line of sight to aircraft for datalink to work, and EPLRs can be obstructed in a valley or urban settings with high buildings. Will play around with ground JTAC vehicles some more and see if I can't make progress. Thanks again for your insight.

Hi Ian, I will definitely give the Stryker a go, thank you.

Hi, I can't seem to make my JTACs use an IR pointer to mark targets during night attacks in my missions. I assign the IR pointer to them, but they always tell me, "no mark" during the nine line. I've also tried using various unarmed vehicles as FACs, including all types of Humvees, as well as armed vehicles like APCs. I've also tried adjusting the range from anywhere to 1 mile to 1000 ft, but FACs still won't give me an IR point. Also have tried using a Predator drone as FAC, but same thing - no IR pointer. Also, in nighttime conditions, my JTACs are always giving me a Type 3 attack profile in the nine line and I'm wondering if this is because they can't 'see' at night for some reason? With the same mission in daytime conditions, my JTACs will always use a Type 2 profile. Is this a known bug with the current Open Beta or am I just not doing something correctly? Thank you and Happy New Year.

I'm seeing the same thing, but also in SP mode. Latest Open Beta Patch.

Hello, After further testing on my part, the current HUD symbology actually appears to be correct - I sincerely apologize for my mistake in reporting a bug. With the newer A10CII product, HUD symbology for IAM employment has changed somewhat (in comparison to the older A10C version) in regard to the steering cue, inclusion of a range staple, and also the weapon release indicator. The A10CII now uses a flashing 'RDY' label on the HUD when dropping an IAM in CCRP mode, rather than a flashing 'MAN REL' label as was used in the older A10C verson. So, all is well. Again, I apologize for the error in reporting a bug here! Thank you.

Hello, Utilizing the A10CII sim before the DCS World OB Patch 2.5.6.59398, the "MAN REL" label on the HUD would flash when the bomb release button was pressed and a IAM munition came off the rail in CCRP mode. This served as an indication that the selected bomb successfully launched from the aircraft. With the newest 2.5.6.59398 patch however, the "MAN REL" label no longer flashes during bomb release. I believe this is incorrect behavior? The only way to verify a successful bomb release under present conditions is the monitor the DMS stores page during a bomb release. Thank you and Happy Holidays!

This stuff is golden, thank you for sharing.

After flying a couple of missions, I really like the way the new HUD looks - much easier to read than before. Also, the HMCS font seems to have been enlarged as well and now MUCH easier to read.

Hmmmmmm. Perhaps the Georgian Government finally put their foot down and enacted a noise ordinance? We haven't exactly been quiet neighbors these past few years.

Who doesn't enjoy watching stuff blow up from the target's perspective, right? The real CBU-87 submunitions do make a satisfying sound though, however: <youtube>

Hello, With the latest patch of DCS World Open Beta and the A10CII, I don't hear any explosion sounds when CBU-97 bomblets explode on the ground at the targeted location. I do hear a brief 'clink' sound when the canisters open, but no sound of the actual explosions. Thank you.

Precisely. Our JTAC currently has a few laser guided weapon deficits in his vocabulary. :pilotfly:

Yes, true. In my original mission described in my first post in this thread, the JTAC did have a clear line of sight to his target (both were in the same valley). My aircraft, however, was about 20NM out from the valley when I first contacted the JTAC. He was able to relay the correct target coordinates over comms, but his datalink apparently could not 'see' my aircraft beyond the 'walls' of the valley, so to speak. Once my aircraft was over the same valley as the JTAC and target, I could begin to pick up his location on my TAD via EPLRS. So, comms work beyond a valley in this situation but datalinking does not. Realistic feature I'm sure, but one should definitely be aware of this limitation when designing a mission if EPLRS connectivity is needed or desired. :thumbup:

Okay, in regard to my original post above, I've found that the JTAC's datalink is constrained to line of sight, which is realistic actually. In my original mission, both the JTAC and target were both situated inside a valley with steep mountainous terrain all sides. My aircraft was essentially datalink signal-masked by terrain in that mission. I had noticed that, although I was picking up the JTAC's EPLR location beacon, I wasn't seeing it on my TAD until I was right on top of him (over the same valley with an unobstructed signal path). I'm astonished that DCS modeled terrain influence like this, but it's very cool. :thumbup: One certainly must be aware of this realistic limitation when designing a mission. I made another mission wherein both the JTAC and target were situated on flat terrain and EPLRs datalinking worked perfectly. Yay. Thanks! :megalol:

Right you are here. I noticed the same thing in regard to the JTAC not specifying a weapon when I have the new laser JDAMS (GBU-53?) on the racks. :thumbup:

I know this is probably an ongoing issue after doing a forum search here on the subject, but I thought I would ask veteran simmers here about the status of JTAC and EPLRS in the latest open beta with A10 II. Specifically, I'm making a mission where I have a Humvee designated as a FAC, along with data link/EPLRS capability, and assigned to a specific enemy ground target group. Flying the mission, I contact and communicate with the JTAC correctly during the 9-line, but when he sends data I don't see a red target triangle on the TAD, nor do I receive a copy of the 9-line on the cockpit message display. I do however see the 'x' location of the JTAC (from his EPLRS) on my TAD as I begin an attack run. Obviously, the JTAC and I are on the same NET as I'm correctly getting his location on my TAD as mentioned. Is this just something we have to learn to live with or I am perhaps designing my mission incorrectly? Also, the JTAC will not select a weapon for me to use during the audio brief - he starts to say "use....." but then does not actually tell me to use cannons or bombs, etc. I've tried assigning the weapons select to cannon in the mission profile for the JTAC as well as leaving it set to AUTO, but the JTAC never specifies the weapon to use. Thanks!

Are the new sounds available only in the open beta version of DCS World?

Not a bug - this is the 'Break Lock' mode of the Maverick, and is one of four available: Boresight, Target Lock, Ground Stabilized or Break Lock. In Break Lock mode the Maverick seeker basically looks ahead in whatever direction it was last slewed to, irrespective of any particular point on the ground. If you stop manually slewing the Maverick seeker without a target lock, the tracking gates will automatically disappear (to give you a more uncluttered field of view), and the seeker will automatically go into Break Lock until you either start slewing again or boresight the Maverick. Ground Stabilize mode lets you slew the seeker towards a potential target and keep the seeker in that position over the ground before actually locking-on. For instance, if you are targeting a group of armored vehicles, you can slew the Maverick seeker close to the group and ground stabilize it before actually singling out an individual target and locking on to it.

I'm definitely firing the laser maverick at less than 8nm, well within the launch WEZ for a laser maverick. I seem to notice that the problem is more pronounced when a flatter trajectory profile is flown at the time of missile launch. If I fly a steep vertical profile at the time of missile launch, the laser seems to reliably fire throughout missile impact, even though I'm firing the maverick at the same distance from target with either a flat or steep trajectory.

I just noticed that when you land and shutdown, the pilot raises his visor and you can see the HMCS monocle over his eye. Cool. :pilotfly:

In Wags' recent tutorial video for the A10II, notice that he fires a laser maverick in latched laser mode and the time to impact on the TGP times out before missile impact. His laser stops automatically firing about that moment (the 'L' stops flashing), and I'm assuming he starts to manually lase at the that point right before his missile impacts target. If I don't immediately start to manually lase under the same conditions, the missile will impact off target, which one would expect. The problem is not missile accuracy or a laser malfunction as far as I can tell; rather, it's the countdown to impact time out that seems to automatically turn the laser off under a latched on state. Thank you guys. ${1}

Okay, I was confused (sorry, I'm the top official in charge of the U.S. election and it's been hectic lately). ;) TMS aft short makes the IFFCC SPI. TMS aft long makes the current flightplan steerpoint SPI. When the IFFCC is SPI, however, I cannot change steerpoints when HUD is SOI, and that's what was confusing me. I assume this is normal behavior?

Yes, this is behavior of the DCS 10C, but A10II goes to IFFCC as steerpoint/SPI when weapons are still selected (thus displaying the predicted impact point of the weapon) after attacking a TGP designated SPI and reverting back to a regular steerpoint via TMS AFT short. In other words, when weapons are selected active on the DMS page and you TMS AFT short to go back to a non-TGP designated steerpoint, the system automatically reverts to an IFFCC steerpoint. This is apparently newer and more realistic behavior exclusive to the A10II. Only after deselecting weapons on the DMS does the system then accept regular flightplan waypoints as a steerpoint. Thank you.

Aha, this makes sense, thank you. I'm assuming this is new and more realistic behavior with the A10II?