Bowie

Have several maps loaded w/ livery appropriate A-4E's on the USS Forrestal (CVA 59), CarDiv 2, TF 77, 1967. Unusable with the current issue as 1/4 of every flight goes swimmin' off the #3 Cat. This is not Rocket-surgery. Bowie

Load a flight of non-augmented trust A/C on Heatblur's USS Forrestal, and see what happens to the #3 Cat shot. Why is this constantly a search for a problem that doesn't require a solution? The slow #3 Cat is documented in the post above. It needs to be corrected to operate non-augmented trust A/C. The USS Forrestal was an A-4 era carrier. Currently unusable for that mission. Bowie

"They are augmented thrust, Afterburning A/C. This enables them to tail-stand and accelerate to flying speed even w/ the #3 Cat's low-speed shoot. The A-4E-C is not." And you are? @IronMike Bowie

They are augmented thrust, Afterburning A/C. This enables them to tail-stand and accelerate to flying speed even w/ the #3 Cat's low-speed shoot. The A-4E-C is not. The #3 Cat shoots slow. That is documented in the post above. It needs to be sped up to match the other Three Cats, to accommodate Non-augmented thrust A/C. It is a Heatblur product, and unusable for general use w/ those A/C in the mean time. Just up the force value on the #3 Cat, or all the Cats if they are of common use, to a value that produces the current results of the other Three Cats, and recompile. This is not Rocket-surgery. @IronMike Bowie

"- Uninstall/throw out P-51D folders/reinstall." Including the user/controller folders. They are regenerated w/ the reinstall, with the proper serial numbers, same as the functioning A/C. Bowie

As Documented in the post above, the #3 Cat is shooting low. This will affect Any AC, including the ED modules. Heatblur's boat, with a low #3 Cat. How can this be an A-4E-C problem, or not be an easy fix, literally increasing a force value in a file and then recompiling. And you are? @IronMike Bowie

P-51D-25 - Joystick/Keyboard & Briefing/Load screen image... gone. Just the mouse. Just the ESC and Pause keys. All other A/C are functioning perfectly. The default Controller tab for the P-51D, that was several scrolling pages long, like all the other A/C, is now a coupla mouse related lines. Loads normal in mission builder, routes/liveries/weapons load-out. But the mission briefing screen is the digital camo 'missing image', as is the mission load screen, instead of the P-51D 364th FS, 357th FG (C5) image. And then, run the mission, and only the mouse works, no joystick, and only the Esc and Pause function keys. Controller/keyboard serial numbers match the functioning A/C, and are regenerated. Have been working w/ the jets of late, so not sure if it was post or prior to either the latest update or F4U-1D release, both of which were installed during the jet mission building program. Have tried so far: - Start Menu DCS 'Repair'. - Uninstall/reinstall P-51D. - Uninstall/throw out P-51D folders/reinstall. - Uninstall/DCS Repair/reinstall. - Uninstall/move folders to Archive ships/planes added during the jet mission building program/reinstall. No joy. Like an important folder/file is missing - but the P-51D, as a prime and well used A/C, has never been subject to Drive Space 'Hanger' time, save the liveries, that have never been a problem, the ones used being in the user/liveries folder. Have not messed w/ the F4U-1D as yet, but is the next thing to consider. This is new, and very weird. P-51D - Dead Stick&Keyboard.trk dcs.log EDIT: added dcs.log @BIGNEWY Please Advise. Bowie

Good, general advice. But believe this is an issue that was preexisting, and simply manifested itself as a result of the non-afterburning A-4E-C's low launch power. Have you loaded an A-4E-C onto the USS Forrestal and shot it off the #3 Cat into a 32 kt WOD? @IronMike Bowie

It's the USS Forrestal #3 Cat, as documented in the Post above. And that is on Heatblur, as it is their USS Forrestal. Bowie

Is this "USS Forrestal #3 Cat Bug" issue (poster above), something that Heatblur will pick up and solve? And, if so, will there be notification, as the carrier is in mothballs until it is resolved. Great product otherwise. Please advise. @IronMike Bowie

Ship Disposition/Formation Save for Way-points: Like the preloaded Aircraft formations, but modifiable/saveable for ships. A mission Carrier Strike Group will typically operate on a 1+15 Cycle (75 min.), and consist of the following disposition: 1 - Carrier (center/guide) 1 - CG (300°R at 3,000 yds) 1 - Plane Guard DDG (171°R at 4,000 yds) 1 - Lead Destroyer DDG (010°R at 14,000 yds) 1 - Picket Destroyer DDG (090/270°R to Threat Axis at 30,000 yds) Fine for Foxtrot Corpen and the initial launch/Recovery phase of the cycle. But, after the 180° turn and sprint down wind to regain sea for the next cycle? - Carrier is fine, on reciprocal heading. - CG is on the opposite side but corrects quickly. - Plane Guard follows and corrects fairly quickly. - Lead Destroyer is 28,000 yds out of position to a Carrier sprinting at 27 kts away from it. - Picket Destroyer is 60,000 yds out of position and racing Away from the Threat Axis. A Waypoint Disposition Change - would allow: - Carrier to proceed. - CG to proceed, or remain on the same side. - Plane Guard could become Lead Destroyer, now only 10,000 yds out of position and ahead of the Carrier. - Lead Destroyer could become Plane Guard, now only 10,000 yds out of position and behind the Carrier. - Picket Destroyer could remain on the Threat Axis and simply reverse course. Pretty slick. Please consider. Bowie

Offering to upgrade my 7700K/1080 rig, or just spend my money? Works fine w/o the don't need. Bowie

Have a 500 GB SSD, w/ ~ 20% free. 50 GB is a lot. Until the next build, it works fine, sans the don't need. Bowie

Hey TC, Attempting to install "VS-30 AA" from the "S-3B Viking Skin Pack Version 1.6 - updated" D/L, into a Saved Games/Liveries/s-3b tanker folder. Get the name in the Liveries option window, but no livery. Is this still the problem? Please advise. Bowie

Have a cull (DCS Hanger) file system on a storage drive for unused and archived stuff, like liveries and entire modules, w/ a "Deployed" text file in each folder. Takes a few minutes after every update to toss ~ 50 Gigs of don't need. Bowie

AI Iron Bomb Release Sequence Issue: All and Four/Half are fine. Pairs: 8(Mk. 82 slicks) + 2 drop tanks - C/L-C - C/L-L - L/Wing+C/L-R/Rear -R/Wing+C/L-R/Forward Asymmetrical - after the third drop, until the final. Please advise. Note: Have not tested the player sequence. Bowie

A Two-holer like the Heatblur F-14... would be awesome. [holding_breath] Bowie

Found this as well... https://www.largescaleplanes.com/reviews/review.php?rid=426 Bowie

VMFA(AW)-121 "Green Knights" were a MAG-11 F/A-18D Squadron (VMFA-314 and -232 were the F/A-18C Squadrons). Be an extremely cool addition to the stable. Bowie

Thanks for the HU. This is really great work. Bowie

AI Dive Bombing Issues: They roll-in nice from 12-14,000 feet, pull through to a good dive angle and onto the target, very sharp. Then they undershoot the dive angle/target, pull off target, and climb back to altitude. Several times. Veteran/Ace pilots. Please advise. Bowie

It's a thing needs attending to. FW190_wing_damage_model.trk @Flappie Bowie

AI F-4E goes stupid. They go into an orbit at low speed and altitude, until they run out of fuel and crash. Happens after extended engagements involving both MiGs and SA-2s, where they spend a lot of time in full burner. Could be Bingo Fuel related, maybe that it occurs during engagement. This is a great F-4B track. (F-4E w/ AIM-7E/-9B, sans 20mm ammo) F-4E Goes Stupid.trk Excellent performance, until after the last Enfield 01 kill, at the 28:15 mark. Then, all remaining F-4E's go stupid. EDIT: Apparently can't, b/c the POS Track function tracked the lead MiG, instead of the F-4E. Bowie

Thanks for the response. This is a great F-4B track. (F-4E w/ AIM-7E/-9B, sans 20mm ammo) F-4E Goes Stupid.trk Excellent performance, until after the last Enfield 01 kill, at the 28:15 mark. Then, all remaining F-4E's go stupid. Bowie

AI F-4E goes stupid. They go into an orbit at low speed and altitude, until they run out of fuel and crash. Happens after extended engagements involving both MiGs and SA-2s, where they spend a lot of time in full burner. Could be Bingo Fuel related, maybe that it occurs during engagement. Bowie