kengou

It's correct. The flight computer system coordinates your turns for you at all times. In flight, rudder is only ever useful in very slow speed high AOA dogfighting situations, where you can use it to do some cool maneuvers. Outside of that, it's limited by the computers.

Auto steerpoint mode can be enabled or disabled on the STPT page of the DED, if my memory is correct. Just hit the SEQ button (dobber right) on that page.

AOA is indicated during landing configuration by the location of the E-bracket in your hud relative to the flight path marker (velocity vector). A perfectly trimmed aircraft for on-speed AOA has the E-bracket centered on the flight path marker, at which point you can fly without touching pitch on your joystick, since the flight computer will hold that AOA for you. The only other way to know your trim would be to look at the stabilator position using the FLCS DDI page, or I think the checklist page as well. Trim sensitivity cannot be changed, except perhaps in LAU files, but I've never looked into that. Airfields can be input via waypoint coordinates as any other waypoint, if you know the location of the airfield (via F-10 map for instance), on the HSI Data page (HSI > DATA > UFC SEQ). You can also put in the TACAN of the airfield if one exists using the UFC. The Hornet doesn't really know what is or isn't an airfield and it doesn't have a database of airfields (it's a Navy aircraft after all). You have to navigate to the airfield using coordinates or TACAN, then you must know the runway heading via ATC communications or other means, and then use the course line knob to adjust the course line on the HSI to help you orient yourself appropriately. Hornet ILS also doesn't work on airfields, only the carrier, in case you didn't know. In landing configuration, the HUD has markers on the bottom in an arc, and a bank indicator as well. The marks correspond to 5, 15, 30, 45 degrees, I believe. Move the TDC cursor over the radar contact and press TDC depress once to select it as lock-and-steering (L&S), if LTWS is enabled in RWS mode. Press TDC depress again to STT lock (hard lock) the contact. Nosewheel steering button will undesignate. Alternatively, place the TDC over the contact and press sensor select switch (SCS) toward the DDI screen with the radar, to STT lock it immediately. Alternatively, press SCS toward the DDI screen with your cursor anywhere, and it will lock the highest priority target, indicated by a cross on the radar screen. To lock multiple targets, you need to switch to TWS mode by clicking "RWS" on the top left to change modes. In TWS mode, TDC depress once on two contacts to select both at once. Undesignate button will toggle contacts in this mode. If you have two contacts bugged, it will toggle between them. If you have no contacts bugged, it will cycle through all contacts in order of priority I believe. You can launch missiles at any bugged target in TWS and keep bugging new targets and launching on them, and you'll keep updating the missile on each target's location, so long as you keep them on radar scope. Regarding elevation: This might depend on how you've bound the elevation axis. Real jet uses a spring-loaded switch on the throttle that returns to center (a two-way hat works well on our PC joysticks). If you bind it to a slider or encoder wheel, it will keep going in one direction, up or down, until you manually center the axis. I'd recommend against this. Elevation scans along a series of "Bars". 1, 2, or 4, selectable at the top left of the DDI. You'll see the elevation carrot on the left moving down in sequence through each bar, then back to the top again. This is normal. Keeping a target in your radar scope is a skill for sure. Most lost contacts are a result of altitude changes. If you are in a mission with AWACS or other Hornets, you can keep track of contacts using the datalink on the SA page on your DDI (sensor select toward the HSI screen to toggle this). Make sure datalink is on (UFC > DL > ON) On the SA page, cursor over a contact to see its elevation, then match your radar's scan elevation to make sure you're spotting it. There are other possible reasons why a contact may be lost. It might be flying away from you at roughly the same velocity, in which case the doppler returns are filtered out by the radar. It also may be flying perpendicular to you and the radar thinks it's part of the ground clutter since it has the same velocity as the ground relative to you. Hope this helps some.

In auto mode I find it pretty dang accurate. Just gotta keep the plane REALLY steady so the pipper doesn't jump around.

I just installed WW2 Assets and Normandy for the free trial, and began seeing this glitch. Never saw it before I installed those modules. I have had WW2 aircraft before and played with the new damage model before, and never saw the issue. Latest Open Beta build. So far only experiencing it on Normandy using the included instant action missions for various aircraft. Edit, tested some more: Definitely coincides with explosions or weapon impacts. Directly coincides with Flak bursts, but is not limited to that. Happens anywhere WW2 assets or damage model are used, not just Normandy. I haven't experienced this when flying any jets.

I'm experiencing a weird and very distracting graphical glitch that I've only ever seen in Normandy. Happens across multiple planes. It looks to me like a bright flash, in the upper half of my screen, that occurs every few seconds, but only occasionally. It makes me think I'm being lit up by tracers and is very distracting! I'll try a repair this evening but wasn't sure if anyone else had experienced this. Edit: Came across this post which is exactly what I'm experiencing. Seems to be a persistent and widespread bug, possibly related to WW2 assets in combination with new code for clouds or damage model. Hope it gets fixed soon!

I have my eye on this campaign, I really want some realistic Mustang missions. I’ve heard talk that this campaign can get really heavy on resources at times. An anyone comment? I play in 1080p with trackir, my specs are in my sig.

Unfortunately I really doubt we'll be able to draw on it. I just don't see it in the cards. But I imagine it should be easy enough for the map to be a file somewhere that can be edited. If that's possible, then mission makers may have a way to incorporate drawings on a custom map.

I love the Jug but it's not that popular for the same reason it's often underrated in real life history too. It's big, and tough, and numerous, but to a casual observer, it doesn't do anything really exciting. It's not super nimble like the Spitfire. It's not super fast and long range like the Mustang. It's not gorgeous looking like a P-38. I know to many of us who know better, it's an aircraft with a rich history and lots of capability, but its merits are more subtle to understand or explain.

If you know where the vehicles are, add a steerpoint with the coordinates. If you don't have coordinates but know the very rough vicinity, use snowplow mode on the targeting pod (SP button on the right hand side) and a FLIR view, and just fly around looking. Won't be very efficient though, and you better have a decent idea where to look first. Or fly low and use your MK I Eyeball. Right now our Viper doesn't have the air to ground radar to look for moving targets over a wide area, so this is about the best you can do.

Casmo with an excellent video on this topic:

Could this be a waypoint set on top of the carrier? If you spawn into a clean mission with only a supercarrier placed and no waypoints, do you still have the square?

This is the standard way every new piece of content releases in DCS. I would really recommend switching to open beta, there's not really any downside to doing so. It gets new content, new features, and even bug fixes earlier than Stable does. And every multiplayer server uses it. Very rarely (more in the past but seldom nowadays) a large bug hits the latest beta version. I've personally never had a problem with this; ED always puts out a hotfix in the next day or so and it's easy enough to not update until that hotfix comes out. Plus a big bug almost always only affects one aircraft in which case I just don't fly that aircraft for 1 day. Not a big deal. Benefits far outweigh the risks.

Worth noting there is a rudder trimmer on the left side on the trim panel. If you're out of yaw trim for whatever reason try using that?

My only complaint about the look so far is the scroll encoder + pushbutton low on the right side, making it entirely grey plastic is not very appealing. Easy enough to change though, certainly not a big deal.

I have no idea what's realistic regarding chaff resistance, maybe it needs more tweaks. But I see no evidence that SD-10s are "broken" as your post suggests.

All the examples in this video occur when the enemy is notching and chaffing. Seems from this evidence the SD-10 just got spoofed and the bandit successfully defended against the missile.

Looks to me like that SD-10 just lost lock there.

I definitely think that it ought to, but I haven't tested it yet. It definitely worked pre-patch with locked contacts in MAP mode.

So if you're inside burn-through range, say 10 miles, and the bandit has you STT locked, your jammer will continue to attempt to jam it constantly, which silences your own radar and prevents you from using it to lock them. So in this circumstance be sure the jammer switch is no longer in XMIT or you can't use your radar. Outside of burn-through range, once I hear an STT lock, the jammer turns on, my radar silences and says "JAMMING", and after a couple seconds the STT lock ends and then the jammer shuts off. Against the AI, they continue to re-lock you, which will reactivate the jammer after a second or so. In between those cycles of lock-jam-break, I can sometimes get a scan or two on my radar screen to see the target, but it's not very reliable. I recommend having the target on datalink so you can continue to monitor the contact while you jam them, and you're ready to switch off the jammer and attack them at a moment's notice.

I tested it some just now. Jamming only works in front of the Hornet, and does appear to use the radar itself to send jamming signals. Jammer became ineffective vs modern Russian jets at around 20ish miles, sometimes a little less. However, it will continue to jam and silence the radar at any range as long as it is locked. 20 miles is roughly a good AMRAAM launch range, so it seems fine to turn off the XMIT button at around this range. Leaving it on as you close through this range is bad! Jammer only does anything vs STT locks. Against SU-27s and older this will be really good, not to mention all SAM types. Against modern 4th gen fighters with fox 3 missiles, this won't do much at all. But then, the Hornet is no worse off than it was before this patch. Remember, in the real world, the Charlie Hornet was never the main air superiority fighter for the Navy - the Tomcat and then Super Hornet were. And the Navy has dedicated jammer aircraft. I have no idea what's realistic, but I wouldn't expect the Hornet's built-in ECM to be able to shut down aircraft as modern as itself (or newer). So I'm not disappointed.

I've read unsourced claims that the jammer silences the radar while emitting because it is in actuality the radar doing the jamming, and it can't jam and track targets at once. Can anyone confirm or deny this? If it's the true reason, does this mean the jammer only works to the front? I haven't had time to test it yet. Are there HOTAS commands to activate or deactivate the jammer (I'd hate to lose a lock in a heated BVR fight because the jammer switch was on and I had trouble reaching it)

Can you speak any more about the modular button system (cost? options?) and the mechanical detent on the standard version? Fingerlift, push through, adjustable?

I would only ask that canopy fogging and defogging is as realistic as possible.

If you look up how-to videos on the Supercarrier Case I and Case III, it's the same radio comms you're getting in the Harrier on every boat.