AcroGimp

Sorry, didn't realize there was a setting to keep the Discord invites from going invalid, here is a new one: https://discord.gg/EnB8UyA DISCO

With FlyingIron Simulations announcement in February that they would be bringing the LTV A-7E Corsair II, affectionately known as the SLUF to the DCS ecosystem, I am potentially willing to establish VA-97 Warhawks if there is enough interest. I currently fly the F-14B Tomcat, and have previously served as Ops O, XO and CO of Hornet and A-4E Skyhawk squadrons. The possibility of a full-fidelity A-7E Corsair II is very exciting as the SLUF was the origin of so many of the capabilities we take for granted in the single-seat attack role today, highly accurate INS, moving map display, advanced A2G radar, CCIP, modern HUD and more - all coupled into a very capable yet compact frame - able to distribute freedom up to 15,000 pounds at a time. If you would be interested in helping to establish VA-97 Warhawks and the A-7E Corsair II drop me a line. DISCORD here - https://discord.gg/XTwWZ4 SLUF - she may not be fast, but she sure is slow. Joker One One, out.

I recently took the time to put together Voice Attack profile with 120 commands to have more granular control over where Jester is looking with the radar, specifically the range-at-altitude commands. In testing on a SP development sortie I found he seems to be working OK, in that he does seem to find targets faster than in auto, and I can combine it with directed azimuth as well, i.e., Center-Left, or Right, etc. On MP though it only seems to confuse him - the range markings rarely change, even the azimuth commands are not reliably indicated on the TID repeater. I am not sure however if I recall the range markings changing on the TID repeater when giving him specific range-at-altitude commands during the SP tests. I know we all know a human RIO is the preference but I think we all also know it is not as easy to have a guy in the back office as we would like. So question is, should the range markings change to nearest normal setting (e.g., 50, 100, 200) when we give him a specific spot, or are we commanding a different mode (e.g., Pulse Search, etc.), could be I am changing more than I thought/intended and it is just not presented to me up front as I am expecting, but I would expect to see the scan cone and range markings reflect the combined directions I am giving. Thanks for any clarification. DISCO

Method for using the WMD-7 targeting pod to find and designate ground targets as Markpoints, transfer them to the nav database as Pre Planned waypoints, and then employ a ripple attack of LS-6 glide bombs for a simultaneous strike on mobile targets before they can disperse. Hope you enjoy! DISCO

This, so much this ^^^^^. The Tomcat crew is all bout shared resources and shared responsibilities - and those change substantially moving from BVR into close-in and then the merge/WVR. DISCO

Follow-Up, The Map issue may have been a one-time issue, appears OK now. SRS and no power on spawn still remain.

Confirming warning lights are harder to read after 12/18 patch.

SRS cannot connect for JF-17 in MP but works for other modules Power not available on spawn in MP still occurring. Map not showing on HSD in MP - when MAP selected display brightness drops by over 50% and all imagery is blurry on MFCD. Sorry no track, not on my gaming rig.

Confirming this today. DISCO

The real gear and flap lights are incandescent bulbs under a plastic cover, checked real quick and looks visually correct. DISCO

The MiG-23 will not keep up with the Tomcat in the vertical, they always drop out before I do, typical merge is nose/nose angels 10 and about 350-450 KTAS - 1/2 loop, unload shortly before level and extend out, wait for him to fall out and then roll in behind him for easy guns kill. And I am giving him weight advantage (I have 2 x Fox 1, 2 x Fox 2, empty tanks and 80% fuel) where he is 80% fuel guns only. Make a smooth pull to 15 units AOA and hold it with Max AB, you'll level off inverted at about 200-ish or just under, Flogger is bingo energy and flopping out, extend towards him a bit and then roll into the control zone. The Flogger is a sitting duck vs a Tomcat. Tomcat can be flown as a rate fighter, a radius fighter, or an energy fighter, take your pick, but most importantly know what your strengths and weaknesses are, and of course know the same for your opponent so that you fight your fight and refuse to give him his. DISCO

For the design of my prototype QuickPit I used the dimensions of the real F/A-18C Instrument Panel as a guide to bound the panel and glareshield and then figuring out what Force IPD Distance setting in DCS combined with placement of the QuickPit, Stick and Throttle in 3D space lets me make 1 to 1 movements. Once that is set I will say that VR, a realistic instrument panel and HOTAS layout and SimShaker is incredibly immersive. DISCO

Interesting, since all the images of NAV GRID in the NATOPS (NAVAIR 01-F14AAP-1) are only shown in reference to the PTID, and with reference to PTID data entry and the expanded waypoint database and Mission Computer that was part of that upgrade. See Section 25 of the NATOPS. NAV GRID only appears to show up one time, in copy-paste text (from the NATOPS) in the HeatBlur manual, it does not appear to be addressed as a planned HB function, and BULLSEYE does not appear in the HB manual at all. I'd be happy to see that functionality since PTID brings JDAM capability, and improved flight planning among other things but I don't think we see it unless HB bless us with a -D model (yes I know later A+'s had PTID). DISCO

I thought the Defended Point waypoint (DP) could be used to establish a rudimentary Bullseye so that you can see it on the TID and interpolate bogey/bandit/friendly location using aircraft or ground reference display. And again, I am under the impression NAVGRID requires PTID which is not part of our A+ (nee F-14B) configuration. DISCO

Doesn't NAVGRID require the PTID which we don't have and will not get? DISCO