Recluse

Thanks for checking me on this. I meant to go back and check on that but I kept forgetting. That's useful to keep track of which stations are needed for which targets. I really like this Video on PP JDAMS (and I think it is up to date, at least it all worked for me as stated) He has a companion video on TOO, but I think it is JUST out of date having been made before they restored the ability to program multiple TOO without overwrites. The Markpoint method shown is still viable, though.

No apology necessary. This stuff changes all the time. AND YES, I agree that otherwise it was a great video. I was just trying to track down WHEN the last change happened, because I found some videos that were 6 months old that I thought were CURRENT, but then I read comments in them to the effect that things were about to change again. I cannot tell you how frustrated a bunch of my friends have been trying to learn all kinds of stuff from Videos, only to find that it had totally changed. It is a little crazy that, in order to keep up to date you have to not only look for the LATEST YouTube Videos, but you have to constantly patrol the Forums to figure out what is going on. For this reason, I USED to only fly with the STABLE BUILD, but then I ended up living with BAD BUGS for a long time and never saw the new stuff, so I turned to the Open Beta and never looked back. It looks like the current iteration happened on the 28-April-2022 OB release or JUST about 6 months ago DCS: F/A-18C Hornet by Eagle Dynamics Fixed:JDAM TOO - TOO will now be saved when stepping stations and TOO ½. More recently, there was a fix to the way QTY worked: 18-May-2022: Fixed: JDAM TOO / PP behaviour when using QTY. Not sure what this change was, but I know that for PP you can now select the Stations under the QTY section and I don't believe you can adjust the QTY at all for TOO, though you can program multiple stations, you drop one at a time (which was done in that Video, though I THINK at the time TOO allowed a QTY to be set)

@Phantom711 The Scratchpad works GREAT in VR... The original scratchpad had a little keyboard for use in VR, but that is not needed any more for pure COORDINATE scraping off the map. The only thing I have to do that breaks my VR use is use the Scratchpad keyboard shortcut to get the Scratchpad up and make it go away because I keep forgetting to start JOYSTICK GREMLIN and vJoy to pass the key stroke from a HOTAS button. (My WInWIng SIMAPPPRO doesn't allow direct mapping of keystrokes) Very easy to setup. Also, that is a great video, but it is a little out of date. The way JDAMS work has changed several times over the course of the evolution. - Originally, the coordinates would pass to a TOO JDAM whenever the FLIR was active. As you moved the FLIR, you could see coordinates changing. NOW you must hit TDC depress to pass the coordinates. - Earlier, if you didn't hit UNDESIGNATE when moving to an already programed station, the new Coordinates would overwrite the old ones. This is not needed any longer. Until you do a TDC DEPRESS, or a WPDESG when on a station, the coordinates programmed will persist. You can now: Select a TOO Station. Designate a target. Select another station.. Designate a target etc.. When done, you can select the station you want to drop from and there is no need to UNDESIGNATE.

Here's another tip that helped me out. LALT-Y on steroids! Especially helpful for VR, but all around useful. I refer of course to the SCRATCHPAD mod: https://github.com/rkusa/dcs-scratchpad Here's a YOUTUBE VIDEO. Really easy to grab coordinates in 2 different systems including JDAM friendly and GRID for map locations. Obviates the need to transcribe them from the map. Here's another tip that I found useful for TOO attacks to give yourself a double check that the FLIR coordinates and the JDAM coordinates are the same: HSI-->DATA--> Click PRECISE (will get you the 10 digit Grids and the expanded LATLONG) By Default, PRECISE LATLONG is in DDMM.mmmm, so to switch to DD.MM.SS.ss, go to the HSI-->DATA-->AC tab use PB15 to switch coordinate systems from DCML to SEC and now you will have a unified coordinate system of DD.MM.SS.ss for your Waypoints, JDAM and FLIR readouts. As I was playing with this, I realized a simple way to make sure I had the correct station selected. I used to just leave it alone and use the STEP command to get to the "right" station. For a SINGLE drop, I now go to QTY and just select the station I know has the PP coordinates I want. If I am dropping multiple PP JDAMS at once, then I will select all the stations dropping with one pickle. For TOO, I drop one at a time and if I have programmed multiple stations for dropping multiple JDAM in rapid sequence, then I DO have to pay attention to the Selected Station as they cycle or STEP through the stations.

So I was turning away from the target area to go back to the carrier. I noticed that even out of AG mode, TCN mode on, I couldn't get rid of the DIamond pointing to the target, and I can't recall if I even saw the TACAN steering pointer. I did indeed power down the weapon at which point I could UNDESIGNATE and get the usual TACAN steering symbology. I think this might have happened when they fixed the issue of Coordinates Over-writing the JDAMS all the time, so in exchange for that, I will gladly power down my weapon on egress. I guess I hadn't noticed it because usually all the JDAMS were off the rails by the time I turned for home. As long as there is a workaround, I'm OK with it. Moving from TOO to PP (empty) also frees up the UNDESIGNATE and I think returns the HMD symbology as well but I don't recall 100%.

@Phantom711 Apologies if I misconstrued anything. I was reacting to this line in your reply, but I get what you mean. I find WP/TOO more versatile except if I do want to drop multiple bombs against different targets simultaneously (which you also did mention, so we still agree ) In DCS anyway, if you put PRECISE coordinates in to make a WP on top of a known target, and use WP Designate to feed them to the TOO JDAM, the effect is just as good as PP, which is what I meant. In both modes I sometimes struggle making sure I have the right Station selected for the right target, so Rich Man or Poor Man, *I* can still screw it up

Thanks!!! I don't know why I failed to find that in my initial search!!

If I understand, you had WP 1-3 from the Mission Editor and you wanted to add 4-7 from Coordinates you had? Did you go to the HSI-->DATA page, and use the UFC to add a waypoint? I usually use the HSI to move to a new WP which shows all zeros, and then hit UFC and enter the GRID or LAT LONG. Then advance to the next WP and repeat. This will give you the WPs that you can WPDESG for a TOO JDAM. As @Phantom711 said, you can (if you have or have converted to DDMMSS.SS ) enter them directly into the JDAM for a PP mode. In this case you will NOT have Waypoints to follow, but when you select the JDAM, you will get steering and TMR cues to guide you in. I much prefer the "POOR MAN's METHOD" using WPs because I can use GRIDS, and I can follow the WPS, Designate and fine tune the lock with my FLIR... To each their own.

Thought I would post this here before logging it as a bug, since it might be "CORRECT AS IS". One of my buddies was going nuts the other night not being able to RE-DESIGNATE with the HMD, not able to UNDESIGNATE a target. Last night I came across the same thing trying to head back to the Carrier and engage TACAN, but I couldn't get rid of my System Designation target diamond. Here is what we found: - If you have a JDAM on board in TOO mode with target coordinates plugged in, it will provide steering cues. If you want to CHANGE the target, you can do so with WP Desg or FLIR TDC, and feed new COORDINATES to the JDAM. You cannot, however get the Targeting reticle back up on the HMD as long as the JDAM is holding a target. Similarly, you cannot use the UNDESIGNATE to lose the System Designation. UNSELECTING the JDAM will fix it. Changing the JDAM from TOO to PP (without entering any PP coordinates) will fix it Expending all JDAMs will Fix it. (I don't recall if merely STEPPING to an un targeted JDAM will fix it... have to try that, but, you would be SOL with only one left). It doesn't seem like this behavior arose until a recent OB Patch, but I don't recall anything in the PATCH NOTES specifically. IF it seems like a BUG, I'll create a TRK and post over on the BUG FORUM, but, meanwhile, to reproduce, Feed some TOO coordinates to a JDAM, then TRY to UNDESIGNATE or use the HMD to desginate a new target. Thanks!

No idea whether it is right or wrong, but I always call SPOT when my sensors have locked on (e.g. AGM-65E, LST, in a fixed wing, (F/A-18, AV8-B, A-10 etc..)or, in the Apache, when the SKR finds it in a DIR mode. Agreed that for LOAL behind cover you shouldn't get LOS to the SPOT, so it is just for game play purpose, though I imagine in Real Life, the JTAC/FAC would absolutely want you to confirm that you saw the laser IF POSSIBLE before letting go with ordnance especially if there were friendlies about. As a Memory Lane Aside, I remember always thinking in LB2 how hard it would really be for the CP/G to actually have to use the sensors to find targets without the Magical T(argeting) key with the TADS. Now I know that it is indeed HARD, though possible. Anxious to see if the DCS AH-64 FCR will be as close to Magical as the LB2 FCR/MMW Hellfire combo.

So I saw something very similar, but with PP mode. - Hot start from CVN-71 - Load with 8 JDAM (4x2 BRU-55) - Enter 4 sets of Coordinates - Select all 4 Stations - DROP salvo when IN ZONE - ALL JDAMS MISS by a fair amount. Turn back in. Make no changes to coordinates or station selection. - DROP salvo when in zone. - All 4 Hit. Reproducibly. First SALVO always seems to miss. These happen to be SHIP targets because they are big. Set to 0 speed with no waypoints. Sorry you have to watch me enter coordinates forever at the beginning of the trk Tried with TOO, 4 drops, 4 hits. No problem with RADAR or RADAR+FLIR designation Note, I also saw the other issue reported where an entry of Zero Elevation (or leaving the 0 elevation alone) results in the PP1 remaining crossed out. Doesn't seem to affect Release or targeting as the second salvo hits where it was aimed. I do have a script running to respawn all 5 ships when the group is destroyed, but, since I only drop 4 JDAMS, and one is not enough to kill the big ships, there isn't a chance that they are respawning somewhere else, and if they were it would be AFTER the first drop, not before. OOPS!!! I meant to attach this to the other THREAD about TOO JDAMS missing after Hot Start on SuperCarrier. THIS HAS NOTHING TO DO WITH THE 0 ELEVATION ISSUE, JUST SEEMS THAT THE FIRST PP SALVO AFTER TAKEOFF MISSES. GRRRR... Just tried it again for the 4th or 5th time...(PPJDAM2.TRK) EVERY JDAM IN THE ORIGINAL SALVO hit dead on. I did NOTHING different except wait a few more seconds after the initial IN ZONE cue. In the PPJDAM.trk, the Second Salvo that hit, was launched JUST as the IN ZONE was reached and hit, so I don't know what is going on now. PPJDAM.trk TOOJDAM.trk PPJDAM2.trk

As I mentioned at the start, Multiplayer might be a whole different animal due to the way the ACLS works with other humans and AI around. At least you know it works under "ideal" conditions. The one time I tried in in MP, it didn't go well...but it could have been a lot of things besides ACLS wonkiness.

I don't know, but I can only guess that in order for ACLS to take control, the aircraft has to be in the full carrier landing configuration with flaps full down. I guess I will try it with half flaps and see if the same thing happens to me. I always put my flaps down full so I don't even think about it. (of course I always check Anti-Skid too, which I didn't do this time). Lately I am used to taking off from the carrier so Anti-Skid and Hook Bypass are already set correctly when I land. LOL.. Gotta follow the checklist!

Ahhh.. I noticed that you put half flaps down very early, but I didn't pay attention to see that Full Flaps never went down.. Good catch..

Not sure why your CPL never went on. I could see you mashing the button on the .trk, so you never transitioned to CPL P/R. You were previously CPLed at other parts of the approach, so I don't know why it didn't take. Have to watch more closely again.

I just flew it. Despite screwing up royally at 7 miles, I managed to ride it down hands free. No problems with the ACLS. Caught a 1 wire which was odd for the ACLS and forgot to throttle up, but I always seem to get EG no matter what, and it was just a test of the system, so I'll take it. My TRK is attached. I commenced a minute early Heh.. now that I think about it, I may never have retracted my speedbrakes when I went to slow down to 300 at the very beginning... OOPS! Was flying silent without my headphones on, and not in VR as usual so I was out of my comfort zone Recluse_ACLS.trk

You posted the mission not the .trk BTW.. but I am going to try and fly it and let you know if I have success

Question: Single Player or Multiplayer? Seen a lot of reports that ACLS is problematic/doesn't work in Multiplayer.

If I recall correctly from my LB2 days (and what days they were!!), the symbology was the opposite of what it is now: LOBL was the SMALL box and LOAL was the BIG box. or maybe I am remembering the Radar Hellfire symbology because that is almost all I used if I could!

I've had it happen with both. I kind of thought the DRONE would be less likely to lose LOS on the target and would be more reliable. When I first started messing with it, I never got an ABORT unless I did something stupid, but lately it seemed to happen with no reason, so I switched to CTLD.

As an aside, I have recently become a convert to the CTLD Autolase script. I always preferred the built in JTAC/AFAC for the "realistic" radio comms, but there were so many times when all I would get was ABORT! ABORT! ABORT! so I switched to CTLD. Less "REALISTIC" but more reliable (and quicker to send Hellfires down range!). Great fun for the type of TRAINING scenarios you mention. I resisted for the longest time but it turned out to be just as easy or easier to do in the Mission Editor than the Standard JTAC/AFAC. Everything you need to know here: https://github.com/ciribob/DCS-CTLD#jtac-automatic-targeting-and-laser

Hey thanks for taking time to respond. Oddly enough, in my case it LOOKED like I got an ACLS lockon, but things were happening too fast and I was trying to talk others through it, so I can't be sure what I saw...until I landed in the drink We were also trying to land on both STENNIS and SUPERCARRIER at the same time, so there were a lot of variables. Gonna give it another shot one of these days, but I trust your testing.

I stumbled on this post and decided to try it out. For many reasons, I have never been interested in Voice Control software, but since it would have some advantages in VR, and the price was right, I decided to give it a try. No manual, but the author has a pretty good video on the site. One thing I struggled with was the construction of those crazy DCS multi-modifier commands. One thing that always bugs me in VR is when I need to move the Cockpit Camera View up or down, so the whole RSHF+RCTRL+NUMPAD2 (or NUMPAD8) is a pain to do in a VR headset. I COULD NOT get FOXVOX to do this, though I am pretty sure I constructed the command correctly in the software, e.g.: Happy to hear from anyone else who has tried it and made commands like this work (Active Pause LSHF+LWIN+Pause) is another one that eludes me.

Thanks! Appreciate the reply.

Hi, been awhile since there was any activity here, but I just discovered Persian Power and it's siblings. I had a few questions and a problem: - I am intending to try Persian Power in Multiplayer with a small group of friends. Still working on current DCS Open Beta? - One of our number doesn't have SuperCarrier, so I tried to add a STENNIS into the mission along with some Client F/A-18's. Also added a couple more Client F/A-18's on the CVN-71. - When I try to run my modified mission, (MissionScripting.lua commenting has been done) it hangs on the TRIGGER START message. --Same issue trying to add the STENNIS in Georgian Power. I tried both as a separate Naval Group and also tried adding the Carrier as another unit in the BLUECARRIER group. Hung on TRIGGER START in both cases. - I can load up the unmodified Persian Power just fine, and it generates missions and all seems to work. Oddly enough if I exit, and THEN start my modified Stennis mission, it loads OK...but the CVN-74 battlegroup is immediately marked as DESTROYED and I can see the smoke from the deck of the CVN-71. - If I delete the SAVE files, the modified mission again hangs at the TRIGGER START. -Is there a way to add the Stennis that won't break things? - I notice that all the CLIENTS present by default are single aircraft. When I add Client Flights, can I add them in a GROUP so we can fly as a Wing (with attendant Data Links in the F/A-18?) Thanks!! Hope you are still around! EDIT: I added a wing of 4 F/A-18's at Nellis in Vegas Power, and it worked, so I guess I have an answer to that particular question. EDIT: Thanks much to @rmk80 for helping me out with some LUA edits to allow the STENNIS addition. Working great!