Bunny Clark

The middle point isn't really an "optimum" range, it's the No Escape range. It's the range at which if the target turns 180° away from you and runs, the missile will still be able to reach it with enough energy for an intercept. When firing against a fast target, the no escape range will be fairly short.

Right now Mav delivery modes are WIP, and the TGP is very much WIP. It'll get better as we get more completed features. It's a pretty cool system when it's working as intended. Right now it works alright for a single delivery so long as everything goes right and you don't end up in break lock. If you do, things can get janky pretty quick.

Just working on a mission this afternoon where I'm continually reminded how bad CBUs are in DCS. 4x CBU-87s dropped on 5x fuel trucks. One was destroyed.

The Viper can't carry the AGM-65E, that's a Navy version. Are you wondering about the Hornet? If so, make sure the code is right, bring up the Mav page on a DDI, point it in the right direction and hit Uncage to track.

Yah, DCS needs to tweak cluster bombs that don't have guided submunitions. Even destroying soft targets is extremely random and rarely effective.

I've had this happen as well, and it's also seemed to be related to ATFLIR in SCENE mode. Exiting Scene mode, or setting the pod to standby has allowed me to undesignate successfully. Haven't been able to reproduce it to get a track though.

The FCS itself can be powered off the battery, if you loose both generators FCS Ch 1 & 2 will remain operative, which is enough to give you full control (you will loose Autopilot, Auto Throttle, and NWS, not that those are of much concern in that situation). The bigger problem is the hydraulic system. The 4 hydraulic channels are powered by the L & R AMAD, so if the engine isn't turning you start to loose hydraulic pressure pretty quickly. Once hydraulic pressure is gone, that's it, you have no way of moving the control surfaces at all, regardless of what other systems are still operating. If you loose both engines simultaneously and you have the altitude, you can attempt either a windmill or APU engine restart. That would be your only real hope of getting the jet back on the ground in one piece. Realistically though, the question is why did you loose both engines? The likelihood of both engines suffering isolated and contained simultaneous failures is vanishingly small, there's no real procedures for it in the Hornet because it's just so unlikely. If both engines quit because of battle damage, or one engine suffers a catastrophic failure that takes out the other engine, the likelihood that other systems have also been catastrophically effected is high. Attempting to land a jet in that condition is far more risky than just pulling the handle.

Ummm, if the green gear down indicator lights are on then your gear is down. IRL by the time the gear is lowered the NVGs are usually off and stowed.

Here's what NATOPS says: "With the wing handle unlocked and nosewheel steering in the low mode, pressing the nosewheel steering button causes the nosewheel steering to go to the high mode where it remains without holding the button pressed." So yah, it's the wing handle that determines how NWS works. I didn't know that before, cool.

That is the correct behavior as described in the Hornet NATOPS. It's how it's always worked for me in game as well.

How does a post about the ARC-210 in the A-10C II module confirm we're getting it in the Viper?

My understanding (not a real Hornet guy): COM1 = Pri, COM2 = Aux. "Push Button x"

That's the date the file was originally uploaded, not the date it was last updated. I have no control over that field.

I'm aware, and it's why I have my axis saturation at 20 plus a curve. It works just fine for antenna elevation and controlling zoom with the Lightening pod. It's only too sensitive with the ATFLIR.

Yah, some people seem to have a lot of trouble with that mission. I've always found it pretty easy. If you can splash the two MiG-29s right away the rest of the mission is a turkey shoot. The state of the Hornet radar right now certainly does not help, but I tend to favor STT in most circumstances anyway. The wingman can be a bit stupid sometimes. Make sure you're transmitting on the correct frequency, and then make sure the wingman acknowledges the call. If he doesn't respond with "Two: Roger. Two: Engaging bandits" then resend the command until he does. In what sense? Are you referring to the supported game version in the file listing? That hasn't been updated with an option to display DCS World 2.7 yet so there's nothing I can do about it.

The Swiss Hornets are quite different from the USN ones. Specifically in regards to the different Swiss pylon that can carry single AMRAAMs, I believe it also can't carry any A/G ordnance.

Alright so I did a side by side comparison, using the same mission in the same location looking the same way. DCS 2.7: DCS 2.5.6: I realized that the mission I was flying took place at a time with no moon. Changing the date to a night with a full moon makes a pretty significant difference: So something is clearly different with DCS night lighting in 2.7. I've never flown a plane with NVGs in real life before, so I can't say which is more realistic. But right now in DCS if there is no moonlight you're better off flying without NVGs than with them.

Also still having this problem. Actually, it's worse. I used to be able to launch the same mission multiple times in a row from the mission editor, so long as I didn't switch missions it was fine. Now my game is crashing the second time I launch a mission regardless of it it's the same mission I launched the first time or not.

One thing to keep in mind is that, indeed, the MavF is something of an afterthought for the Hornet. And the Navy sees it primarily as an anti-ship missile. The idea was to primarily use the MavE in the CAS role. Compare the Maverick implementation in the Hornet to the Viper as well. There's a massive difference.

The reality is a bit more complicated than that, as the pods don't simply throw the raw image up on the screen. This goes a bit to what sc000tch was saying. I don't know how the inner working of a targeting pod function, but I do know quite a bit about optics, cameras, and image processing. You loose absolute resolution as you zoom in, but that raw image is processed and then up-sampled to a higher resolution to match the display resolution. You'll never make it look as good as a full resolution image, but you can make it look better than an unprocessed crop. Plus there are optical, lighting, and environmental factors which can degrade image quality across the board, but are more noticeable at higher resolutions. All of this means that, overall, compared to "pure" examples of image resolution scaling like what Harlikwin did, the higher resolution images won't look as good while the lower resolution ones will look better. This will serve to lessen the visible quality disparity between 1X zoom and 9X zoom. But, either way, the Lightening II in DCS right now looks too good at 9X, and I suspect looks too good across all zoom ranges. And while the Lightening II will always have a narrower field of view at NAR 9X it will look considerably worse than the ATFLIR at NAR 2X. When the USMC was trying to decide between Lighting and ATFLIR for their Hornets they determined that the two had widely similar capabilities. Which is further evidence that the Lightening having significantly better target spotting ability is probobly unrealistic.

Not only for large multiplayer missions. It would be great for achieving a realistic deck atmosphere in single player missions with a bunch of AI aircraft also spawning in, plus static deck planes. Right now trying to setup a mission with 8+ AI spawning in with a flex deck configuration can lead to some pretty weird things happening with spawn locations and taxi routes.

I don't find the Hornet to be difficult to trim out at all. I also don't have much trouble with the Viper either, but the Hornet does feel less squirrelly.

Standard practice is for the flight frequency to use the VHF (COM2) radio, so the UHF radio is free.

Hmmmm, or maybe there's something else going on? Now I'm having this problem as well with one of my missions.

Well hey, since the Super Hornet doesn't exist in any way in our DCS universe, I guess it just means our Hornets snagged all the ATFLIRs instead