Nealius

Pretty much as per title.

Regarding the E-2s and tilly, carts etc. When I place those in the junkyard and between the Junkyard and the helo parking, the directors will park clients there, rotating them so that the tail is colliding with any statics in that location.

Not fixed with directors update. Tomcat director waits for Hornet to launch before handing off the Tomcat to the cat, when there should be enough wing clearance for both to be on the bow cats simultaneously.

This has come back again with the last two update cycles.

Why is this being ignored for 8 months?

Page 55 of the updated manual claims that aircraft will be directed forward of the superstructure if there are parked aircraft or statics port or aft of the superstructure. In real life, Hawkeyes, cranes, tugs, helos, and other equipment are parked port and aft of the superstructure. The taxi directors, when parking, ignore these statics, contradictory to what the manual states.

I'll need to test it with the Viper so I can get a wind readout. I did one flight in the Tomcat with 21kt winds at 33ft, 0kts at 1600ft. There were winds aloft but I don't recall what they were. I do recall a decent crosswind until I hit Platform at 5,000ft so you may be right.

I've frequently had the X appear after firing my bursts as well. Never understood why. I've also never had an accurate gun solution either. I always have to Kentucky-windage it after the first burst or two.

They apparently do not recognize static tugs, forklifts, and cranes. I put those and a Hawkeye around the junkyard, with two static aircraft on the patio. Directors led one client to park on top of the tugs/forklifts in the junkyard, and tried to lead the other client in such a spot as to collide with the parked client in the junkyard. Recovery is an absolute mess.

The new fog update has broken this mod. The lines need to be updated. Comparing the two luas I am unable to find which line(s) need to be removed to again decouple the winds. EDIT: I think I fixed it. I couldn't find the "added lines" that were referenced though, only lines that were commented out. me_weather.lua

No, there is only one Stennis. The Supercarrier module only controlled whether the deck crew appeared on it or not.

I was using "height" interchangeably with "thickness" though I see now how that could lead to confusion. As far as I know there's no way to set actual height.

We bough it, and got the feature for the Stennis. Then that feature was taken away from us after we paid for it.

The whole crux of the issue is that the Supercarrier's spawn behavior is bugged with the Tomcat, reported by Grimes here two years ago and still not addressed:

Adding another timelapse demo. The fog will automatically transition without requiring the user to micromanage fog keys to recreate the effect of fog lifting. My parameters in this video: Mission start: visibility 6000, height thickness 1000. After 10 minutes: visibility max, height thickness 0 After 20 minutes: visibility 6000, height thickness 1000. The fog will automatically transition to reach programmed visibility and height at the specified time.

The video states that dew point affects the auto fog, however we have no method of setting the mission's dew point.

We'll probably have to block off spawn points in order to force-spawn jets to whicher point corresponds to the desired catapult. Problem with that is that it severely reduces spawn points and in particulary causes issues with the Tomcat "delayed to start," which is an issue that's been around for at least three years now.

But they’ll give us simplified TDC slew for F Mavs. The commitment to balancing realism, gameplay, and hardware limitations is wholly arbitrary.

Being an option, is there a way to turn it off?

They could have at least kept the basic deck crew and only deleted the directors.

So it's not the fuze, but the code for the nose well that has to be the same for all bombs of the same type? Follow-up question to that would be why the DSU-33 needs that code at all when it isn't a fuse nor is the burst height adjustable from the cockpit...or can it be? To me it seems like that DSU-33 code could be bypassed (e.g. inputting the code for a plugged bomb instead of the DSU-33) and the bomb (and DSU-33) would still function as advertised so long as the tail fuse is set.

In late November I tried to set real world temperature of 4C, as reported that day at Incirlik, however the editor won't allow any temperature below 10C for the month of November.

I haven't had time to test in-game but had a thought: Should it be possible to mix DSU-33 and plugged nose bombs? Since the DSU-33 is a sensor and not a fuse, if both bombs have the same tail fuse they theoretically should work as they technically do not meet the MC-FAIL criterium of "different fuses;" i.e. both noses are plugged, both tails have the same fuse. If this still triggers an MC-LOAD error, what is the condition causing it?

Massive issue in MP. The entire carrier will flicker in-and-out like that as well.

It seems the IFLOLS is a bit busted as well, at least on the Washington. The ball itself is visible from a mile out, but the datum line doesn't appear until you're at the ramp.