VFA41_Lion

Hi, love the mod. One thing I would like to tweak on my end is lifetime of plane crash smoke. It disappears very quickly! Wouldn't mind making it longer, as its distinctive black column makes awareness of downed planes very easy :)

This scenario sounds like a mission design error to be honest.

Saw this tonight in MP. Own group of 4 planes did not show up on SA. Not even regular HAFU symbols.

HUD AUTO designation is just as bad using the TDC slew keys as button presses instead of axis.

I experienced the same issue, and got it working by letting it do a sweep search for one second before lasing the target.

AI SAMs are definitely that stupid. Need a mission file or track.

this is already present in the current system

Because those 2 extra HARMs are not technically able to be carried on the specific variant of F-16 that ED is modelling. All other fairytale loadouts that we have for modules is technically possible, but not 4 HARMs on the Viper. Sorry. :joystick:

You have to open the .miz file directly via winrar or 7zip and then edit the 'mission' file with a text editor like Notepad++. Search for 'failures = ' and delete the whole section.

Your .miz file has failures enabled regardless of what is actually shown in the mission editor.

1) Is there a setting to disable gun run attacks from CAS-aircraft in modern settings? Suicidal AI otherwise. 2) Auto generated cruise speed settings need to be adjusted higher, I've seen some flights stall out and crash :(

Or maybe the "floatiness" reported is pilot inputs become significantly more noticeable on the last mile of approach and small deviations become large ones. The only times I've seen myself float is when I wasn't totally calm on approach and started overcorrecting for when the deck starts rising or dropping from sea state.

the flight model isnt literally floating over the wires. Its pilot input.

There is no fix required. Its very easy to float the Hornet at the last 1/4 mile by overcorrecting on the throttle at the last second in a sort of brief panic against smashing into the back of the boat. Just keep flying the ball all the way in (remember to ignore ICLS) or wave off if you think its too high/low.

Latest OB, MavF display works fine. Not blacked out at all.

This is problematic with any controller setup this isn't an exact replica of F/A-18 HOTAS.

This post should be pinned on this dang forum. :thumbup:

Hoping those patch notes are incomplete, because its rather sparse after being told monthly patches would be focused on features and systems.

30 degrees of bank is a lot. I've found that your speed needs to be at a decent level for the system to hold or else the speed decay will disengage the autopilot.

But you can already see what designated target of TGP is from the HUD. Its the target diamond. :huh:

you.... do know trees can grow to be quite tall, right?

seems buggy that GLOC will not happen below 8G, eh?

Unless you are on the Eagle Dynamics F/A-18 development team or part of the QA testing team, I don't really care what you think. Nothing personal. :) That being said, the entire track is thirteen minutes. The F/A-18 as it stands doesn't require even remotely 30 minutes to startup and takeoff.

I prefer to do my testing sessions from cold and dark starts, so that takes a bit extra time. Oxygen knobs and switches when clicked/rotated with mousewheel dont work but binding it to an axis does? :huh:

... except when using the g-limit override. Unsure if this realistic or not. Notes: Was able to sustain a 7.0 G turn at full afterburner at low altitude for several seconds until eventually lost airspeed (or selected g-limit override to demonstrate blackout at 10 g's). Like i said, not totally sure if this is a bug or not :music_whistling: https://www.mediafire.com/file/4zg05c37jufxj97/hornet_flight_model_****y.trk/file