MARLAN_

An absolutely huge part of MSI is being able to designate (L&S) offboard track files, I hope they at least can implement this.

PB10 in STT will enter TWS AUTO, sadly, DCS currently clears all memory when you exit STT, hopefully ED will fix it sometime... If all of the bugs and missing major features of the F/A-18C were fixed/implemented, A/A would be much much more fluid to navigate. You get a wide search volume (140 degrees) as opposed to the more narrow one in TWS, and if it was implemented correctly, depressing on the RDR ATTK in RWS would center the scan volume. Typically RWS is used during the sanitization (pre-commit) phase of an intercept. You would switch to TWS during MELD & SORT.

https://forums.eagle.ru/topic/285366-exiting-scan-raid-back-to-tws-centers-your-scan-volume/#comment-4870857

In DCS, while in SCAN RAID, your scan volume is centered straight ahead (0 degrees ATA) when of course it should be centered on your L&S designation (the display is correct, but functionally it is not), thus any sort of crank/maneuver will lose your radar SA to that designation. I believe I reported this somewhere, or someone else did, might be able to find/merge it.

For example, if you launch at M1.1 versus launching at M0.9 (35K 20d Loft), the AMRAAM will accelerate to M3.8 versus M3.6 (there's of course more to this, like drag) The 20% extra launch velocity equates to about 5% extra missile velocity. As a different example, if you decided to shoot a rifle while standing still, or while sprinting, how much do you think that will affect the bullet's range? What about while shooting in a speeding car? A Viper isn't going to be able to take advantage of the 5% further shot range if their radar is 10% lower range. Even if it could, 5% range is barely noticeable, any sensible BVR timeline factors in some "slop". (and the Viper radar is still significantly over tuned) In addition to a slew other other factors such as fuel, less weapons, less SA, etc., and when/if ED ever properly implements F-18 features the gap will be even wider. "go fast" is hardly the most important factor to the BVR arena, especially if simulating realistic fights as opposed to the "airquake" arenas where you take off/shoot all your missiles and RTB in 15 minutes (and even then, I'd rather have a Hornet)

To note, top speed has very little to do with A/A. The F18 is significantly better as an A/A platform.

Without getting into a wall of text, if you want motivation to fly the F-18 again, know that the F-18 is superior to the F-16 in nearly every single way, notable advantages to the F-16 being acceleration/top speed (which is mostly irrelevant unless you're doing drag races) and slightly better at SEAD/DEAD. There is a lot of opinionated misinformation about the two aircraft, but if you want to start flying the F-18 again and put the hours in you won't be disappointed.

Real world yes. There's a LOT the real Hornet can do that is yet to be implemented into the DCS Hornet.

Would be great if there is also a "tank on the ball" or "trick or treat" radio menu option where if you bolter it will swoop down and meet you

You are not understanding. Just because a bug happens to emulate real life does not make it suddenly not a bug. While these sort of clouds could be something ED should look into, it is currently unintended behaviour and should be fixed. Image 1 is the F/A-18C AIM-9X PG Mission - Clouds at 0 feet. Image 2 is me setting the cloud deck to 0 feet with density 10 in a new mission. Image 3 is the same F/A-18C AIM-9X PG Mission for comparison. Old missions have weird behaviour that can only be emulated by opening old missions, you can't reproduce it with a new mission. Additionally, @Doughguyplease point out those sorts of cloud formations at 0 feet found in the Persian Gulf as opposed to what the mission's obvious original/not-bugged intent was is to be clouds overhead.

Lots of missions that haven't been updated to the new clouds (A lot of the instant action for example) has clouds at ground level, fairly sure this is a bug and not correct as is. Mist may be coming (and that's awesome!) but I'm fairly certain it's a bug as they are clouds (as per the DCS implementation) not mist. If this is correct as is, how would I go about implementing mist into my missions with the current clouds? Can you just set the cloud value to 0? If I recall it has minimums, but maybe I am not remembering right..

Unfilled commitments and not fully delivered products is not a sustainable business model. Users will leave or switch platforms at the first opportunity whenever competition appears, or even if there is no competition, users will eventually become fatigued from the undelivered issues and pursue something else entirely. A business would do well to fully realize their products even at a loss for that one particular product, lest they risk any future growth or increase in users & purchases. A case like COVID while of course disastrous overall, was generally a huge boon to niche companies - this growth won't stay forever. As users become power users with their product and learn what was not delivered attitudes will change through even the average user. The fallout will not be immediate. Foresight is required in such cases - especially when a business only has a limited amount of products they can eventually create, user trust is paramount for long term success. - This is a general statement, not directed at ED, DCS, or the F/A-18C module.

@NineLine In my opinion (and I feel like others would agree) the #1 priority for the super carrier should be (in no particular order): - Adding Night Wands to Night Crew - Allowing a way for users to control boat heading & speed, and a way to cause the boat to set a WOD (20-30 knots, 30 knots default), maybe a menu command, or adding a Mission Editor trigger would be great too. - Fix issues with F-14. Maybe it's seen as not high priority because it's not an ED module, but F-14s integrate with F-18s and is a MAJOR issue when deck crew refuse to launch F-14s. - Fix LSO grading and PLATCAM angle. - Add NV to night time PLATCAM - Add ability for users to activate CUT & Waveoff lights IN VR. (Unless I missed the way to do this) - Deck markings not visible in mission editor. All of the extra stuff could come in 1+ years and nobody would mind. Things like the Ready Room/Greenie Board, the squadrons who would use this stuff they already have their own ways to deal with it. Discord/screen share for briefings, Google Sheets for Greenie Boards, and both of those arguably work better anyways. Improved deck crew that actually start up your jet, or taxi you around/etc would be sweet to see, but the critical issues need to come first before more features!

GLORIOUS

Reproduce: Set TOT for the next day. EG: Current time is 23:55:00 ZULU, set TOT for 00:05:00 ZULU and TOT will break until day rolls over. TOTNewZULUday.trk

Adding the weight is so helpful! Thank you!

F/A-18C can do A/G all day if that's what he wants to do. You only need A/A depending on the mission, if the mission calls for it, he could find get an escort, AI or human, but that would be the same issue you'd have in an A10

The Navy likes sticking their probes into things. The Airforce prefers probes being stuck into them.

If it wasn't obvious already from Tholozor, we should be able to, depends whenever ED have time to add it. IIRC this would be set on the MIDS page. Could set your Datalink ID (EG CT11) and your flight letter (A,B,C,D, etc) it goes past D but I forget how far, maybe up to H, I'd have to ask.

Sorry, I realize the image is cropped, but that is taken in air.

As you can imagine, it would be near impossible to find a document as proof that says "the TDC should slew up to this many pixels per second" - the following video shows an example of up to how fast the TDC can slew. If this speed was increased it would greatly help in the ability to utilize the RDR ATTK display, such as bumping for azimuth/scale or selecting PRF/TWS/RWS/etc. @19:12

As title. NoWindHSIDataAC.trk

Pitbull is Medium Pulse Repetition Frequency Active (MPRF) Husky is High Pulse Repetition Frequency Active (HPRF) HPRF/MPRF modes for the missile work the same as for your aircraft radar, being that HPRF has more range but is better for high closure rates, and MPRF has less range but is better for low closure. For F/A-18C only (I don't know how the F-16 works, but it's probably similar to some extent) On your RDR ATTK display for the F/A-18C you should see a solid A indicating HUSKY/HPRF active, and a flashing "A" indicating PITBULL/MPRF active (currently in DCS we only get a solid "A" incorrectly indicating PITBULL/MPRF active) The HUD would act the same as it does now in DCS, your dynamic TTA (Time-To-Active) cueing would display time to active for either HPRF or MPRF based on the MC calculation for which mode the missile would enter. Note that it doesn't necessarily step from HPRF to MPRF, it depends on closure, the missile could go directly to MPRF active, but an HPRF active state would eventually switch to MPRF active as the missile closes in range. Also, as far as I'm aware, avionics set up aside, it doesn't appear to me as far as I can tell that any HPRF active state is implemented in DCS yet (in the Hornet at least). ED mentioned it's in the pipeline but who knows how long it'll be until released I guess.