Hulkbust44

Well MSI trackfile processing/extrapolation wouldn't stop until after the track MEM limit has been reached right? This would be if the radar was the only contributing sensor. I mean, it can't just drop everything right? Look at 1Look RAID. Your in a STT but can still see the system trackfiles as they continue to exist. This makes sense as you can have a separate STT, L+S, and DT2 per the docs. Mobius708

I would have a button for A/P button, then the pilot select buttons on the UFC. not sure how changing the modes works, if I am let's say in ALT and switch to ALT/HDG, it would probably disengage the ALT option in autopilot panel? No, once selected altitude is always referenced until RALT or BALT is deselected or A/P is disengaged. So I probably need to start each sequence with disengage AP, AP Button on UFC and then select the options? No need, press A/P then select what you want. Could also be a deselection. I am not convinced that HSEL replicates the real Hornet... it feels counter intuitive that I need to set a heading before engaging HSEL. I would really expect it to use current course, unless set to something else, who would want to fly north as a default? It is almost as if I have Altitude Hold and AP will set the target altitude to 0 unless I set it before engaging... It is very much common practice in all aircraft to set the heading bug all the time. You must input a heading, otherwise heading select has nothing to do. When BALT or RALT is used there is an automatic heading hold function, no need for HSEL to keep course. Also seems that I can not use UFC to tip in the values (unless I first use the the HDG switch with a longer press - there I get a HSEL option which I can tip in), for altitude there does not seem to be any option to tip in anything, it seems contrary to the whole purpose of using UFC for the autopilot in the first place...is it certain that this is the way it is in real Hornet? It would really turn me off from buying one and I would consider a M2000C instead. Very few combat aircraft can command autopilot to adjust altitude. Only one that comes to mind is the M2K. There's also a whole coupled autopilot system where the aircraft will fly to a navigation source, and even do radial intercepts. The only way to completely disengage A/P is via the paddle switch. Otherwise the jet remains in CSS (A/P ADV-) CSS is control stick steering. CSS is engaged in every autopilot mode. This allows you to use the trim hat to fly pitch and roll adjustments. This can be entered independently of a hold via A/P then ON/OFF. Mobius708 Edit: aw, how do I do multi quotes?

It's not even a cheat, it's a hindrance... Do you have a split throttle? If so it could be the the physical controls are still commanding off when the start sequence is attempting to move the virtual throttle to idle. Mobius708

Can you un select and reselect A/A? Upon takeoff the jet is forced into NAV master mode. I believe this logic might still be at play when the gear is not up and locked thus the MC attempting to remain in NAV. For a possible fix try cycling the 2nd mission computer off/on. That should reset the SMS as the weapon computer comes online. Mobius708

Oh now you're claiming random crap over on the Viper side... Mobius708

With proper implementation you can designate any track. From a STT you can even have a separate STT, L+S, and DT2. I'm pretty sure even from RAID, if you have a track file you should be able to designate it, might not have radar contribution. Just can't do all this in DCS right now. Mobius708

Lmao. Also, initially the Rhino and Hornet shared the 73' Mobius708 The version we have actually is the best legacy Hornet. This specific aircraft was the second to last legacy produced, and the last one to go into service. Mobius708

So you're saying that the Viper radar *must* be better because the jet was initially designed for A/A and had more versions? There is literally no data in this post, it's pointless. It's not physically possible for the Viper to have a more powerful radar when the talking about mechanically scanned arrays. The aircraft is just too small. The radar is focused on MPRF with no selectable HPRF. It will always have a lower maximum detection range. This is still true even if the 16 had the v9. The v9 would bring the 16 much closer to the 18, but that's about it. The Hornet just outright has a more powerful radar with better signal processing and multisource integration which the Viper just does not have. There's a lot more to it but I don't have the time right now. Maybe you should come back and try again when you know a bit about each radar system, or just how different radars work in general. Mobius708

We understand that, but it would take less time if developers weren't prematurely reallocated to another project... BIGNEWY, just so you know, we understand that you don't have a say in what the devs do, I'm sorry that you receive so much flak for their decisions, but people just like to shoot the messenger. Mobius708

Do you use track IR? I believe that is a system reserved key. Mobius708

Set L+S, yes. you just can't command a STT. Mobius708

You need to select TACAN as the navigation source via the HSI. Top left, click TCN. Mobius708

There are even graphics in the DCS Hornet manual showing things such as radar contribution circle. Mobius708

In that case, why was the majority of the team moved to the F-16? If you want to actually get something done it's best to keep your people working on that one project it. Or at least, don't take people from it. I understand that the Viper is missing a lot of features, but I'd argue that the Hornet's major bugs should take priority. It's the bugs that make users skeptical about purchasing a module. Mobius708

I basically do all my radar work with NWS to step between tracks, SCS to attack format to STT via AACQ/FACQ, and raid to focus on groups. I also use the AZ/EL since I can break out tracks by altitude. SA format designation can't come soon enough... Mobius708

Another tiny detail, AACQ has a submode, FACQ. (fast acquisition) Same SCS logic, but rather than getting a STT on the current L+S, the system commands a STT on the target under cursor.(TUC) This can be quite usefull. Always happy to help! Mobius708

Well yes, it's a bug... The datalink should be frequency hoping so TACAN should be a non factor. Mobius708 Well yes, it's a bug. (DCS limitation) The datalink should be frequency hoping so TACAN should be a non factor. Mobius708

SRS already takes care of most of the voice systems. Even MIDS and KY-58 to some extent. We would need a native DCS global radio system to rival SRS in the near future. Mobius708

For 73 data, I wish. I believe there was a document I found that detailed the radar performance of the AN/APG-65 in the Harrier and Hornet. I explicitly remember reading 55nm for a 5m^2 target in a look up. Knowing that the 73 made significant improvements upon the 65, I'm placing 55nm as an absolute minimum of what the 73's high end detection range should be in DCS. Mobius708

Hornet has the same Azimuth bumps, but better because you can actually control it. Only hindered right now due to the stupid slow slew rate. As for ease of use, just press NWS to step the tracks, no need to slew and designate anything. Really can't beat that. Even to STT it's just a castle towards the attack format. Mobius708

It is most certainly not performing realistically. The AN/APG-65 of which was replaced by or Hornet's AN/APG-73 had better performance than our DCS Hornet radar. The detection range is lacking. (It was absurd before at 97nm, but it should realistically be at an absolute minimum be 55nm for a fighter sized target. Right now maximum range in DCS for a fighter is 48nm...) And what you mentioned about the brick timeout is a workaround for a major bug. Tracks are being dropped because someone thought that the brick timeout should influence trackfile deletion...they have nothing to do with each other. This issue also stems from a lack of MEM mode. As for comparison, the Hornet radar should out perform the Viper's radar in nearly every metric. Especially detection range/capability. The 16 has a slight advantage in MPRF detection, but that's mostly because It can only search in MPRF. Now, the Viper radar is DCS is absurd right now and should be fixed in the next patch according to ED.(in detection range) Mobius708

Okay, 15 kts ship speed plus 15kts wind speed works out. Mobius708

15kts is way to slow for a carrier landing unless you have some serious wind down the angle. Mobius708

Nope, the MIDS LVT is a built in terminal. The datalink pod is only for man in the loop weapons. Mobius708 For the link 16 datalink, you just need to press the D/L pushbutton on the UFC and the press ON/OFF to turn the system on. (also interconnected with TACAN) Most likely you don't have SAMs or an AWACs in the mission to populate/clutter the SA format.

As a crutch, people say to put the velocity vector on the crotch if the ship so that you are "leading" the deck. Mobius708