Smashy

After months of sandboxing around in the Hornet, I finally started a campaign and chose OitW as my first. I just finished the second mission, completed both primary and secondary objectives and splashed a F-5E. Didn't have to tank and ended up with a cut pass on recovery :D. I'm having a blast. Thanks for the great work @Bunny Clark!

Exactly the same here but instead of Auto/Man I have RESET mapped. I find myself never hitting RESET and sometimes having to press my MFD button for AUTO/MAN, so I'm going to copy your setup. Also, elevation is a defined HOTAS function and the same binds can also be used to zoom the ATFLIR/LITENING. No OSB mapping needed. I'm positive you knew that but just clarifying!

I can verify this is how it currently works. I don't remember it being this convoluted. IR MAV seeker will not respond to TDC input if there is a designated target on the FLIR. I vaguely remember being able to move the MAV seeker and FLIR reticle just by assigning TDC to the relevant display, no undesignate needed. Or maybe I'm not remembering this correctly?

A lot of the allure of the Hornet for me is nostalgia. I spent countless hours with Graphsim's Hornet 3.0 and Korea and to a lesser extent Jane's F/A-18. It's awesome to see the Hornet realized in DCS today and I'm constantly amazed and entertained by this module.

Thanks for the info. It helped me set up a test with a neutral aircraft and the surv-donor track was indeed that yellow rectangle. IFF or asking for DECLARE did mark the track as hostile. That's a little confusing.

Does anyone know what the yellow rectangle in this screenshot indicates?

The manual was updated with the latest open beta update. Here's what it says about the F/C option on the DL13 format: Force Correlate. Cycles between centroid tracking and forced correlation. Centroid tracking attempts to track bright or dark shapes in the image and is more effective against moving vehicles. Forced correlation attempts to track part of an image and is more effective when pinpointing part of a larger structure. I've only tried it against structures and either mode work fine for that purpose. I'll try some test shots at some moving targets later. One cool thing I discovered was that you can box/unbox the F/C option on the DL13 by bumping the SCS switch in the direction of the DDI that already has TDC assigned and displaying the DL13 format. Pretty handy and I don't remember seeing it documented in the manual.

I finally got around to playing with the ALE-47 and think that manual is the best for me too. At first I thought S/A would be the best but I ran into a couple of problems: with an advanced threat like the SA-10, S/A mode pumps out chaff at a high rate and will continue to do so until lock is broken. I found that my chaff was depleted fairly quickly when approaching an SA-10 site. It's easy to grant consent to dispense earlier than intended when the RWR is deedle-deedling at you and you see that solid "10" line on you. while dispensing in S/A mode I found I can interrupt chaff f I press the forward dispense switch. However, pressing forward dispense switch will not do anything until I cycle the ALE-47 mode through AUTO, MAN and back to S/A. This was pretty easy to do in the heat of battle and less than optimal for obvious reasons I also tested AUTO mode and found it to be too wasteful of my expendables. I'm still playing around with my manual programs but so far have this: MAN 1 flare (one flare, 0.75 second interval, 4 times) MAN 5 chaff (same as above) still trying to decide on program settings for MAN 2, 3, 4, 6. I'll likely configure MAN 6 to dispense both flare and chaff and assign it somewhere to my HOTAS BTW, using the ASPJ with expendables really seemed to increase survivability. Not really an objective test, but I was able to defeat 8 of 11 SA-10 missile shots at me from various ranges. With the ASPJ off, my success rate was much lower.

Does this still work as expected with 2.7.1.7139? I spent some time playing around with OAPs today and found that I could slave the ATFLIR between a waypoint and its O/S using the WPDSG and O/S buttons on the HSI but trying to assign offset coordinates to a GPS/INS weapon in TOO mode was not working. For example: with a JDAM in TOO mode, pressing the WPDSG button on the HSI will successfully plug in the waypoint coordinates to the weapon but pressing the O/S button does not change the coordinates seen in the JDAM MSN page. Offset data also remains blank on the MSN page. The only way I've been able to get this to work is to assign the TDC to the targeting pod after pressing the O/S button on the HSI page (assuming one is loaded on the plane). The TOO coordinates then get updated. That's a kludge at best since now the weapon is getting coordinates from the pod's designation and not from a waypoint designation. I tried this with GBU-38, SLAM and JSOW. Same results for each in TOO mode. tl;dr - the ATFLIR responds as expected when toggling between waypoint and its offset. TOO mode with GPS weapons don't get the hint when you select a waypoint's offset.

You can edit the following file to set the initial position of the kneeboard to your liking: Scripts/Aircrafts/_Common/Cockpit/ViewportHandling.lua Look for the following line and modify accordingly: local x0 = 0 From experimenting, the value in the variable represents the offset in pixels from the right edge of your monitor(s). For example, my second monitor has a resolution of 1920x1080 so I changed this value to: local x0 = 1920 That pushes the kneeboard 1920 pixels to the left and puts it on the left edge of my first monitor.

I think this problem is affecting me right now, Open Beta version 2.7.1.7139. The LSO Main Screen Window as described in the Supercarrier Operations Guide is not displayed. I'm using 2 monitors and exporting MFDs to the second monitor. I tried testing with a single monitor setup but the results were the same, no LSO PLAT cam window. Resolution is 3840x1080, "Scale GUI" option set to 1. I'm attaching my multiple monitor config file. FWIW, I saw something similar with a few of the Huey panels (AI and cargo view) and was able to tweak an associated LUA file to get the AI panel where I wanted it. It almost seems like the LSO Main Screen Window is being displayed off a screen edge somewhere where I can't see it. Just a guess. update - I just tried it after running a repair and moving my Saved Games folder out of the way so DCS would run using defaults and no luck. I have no mods installed. 2 Monitors, Main + MFDs.lua

I'm not sure if you want non-reports but the fly-an-empty-mission-first method worked for me really well. After today's patch, I tried 5-8 missions without flying an empty mission and experienced no crashes. I'll report back, submit logs if crashes to happen again. Thanks to @Flappie, the beta tester team and all the devs for all the hard work. I've been following this monster thread and it can't be easy staying on top of all the various crash reports.

Same here. It's like Christmas morning reading changelogs!

Just in case you haven't noticed yet, 2.7.1.6430 increases flare count so now the Hornet can carry 120 expendables in any combination.

First _OK_ landing ever! Super excited this happened.

Same here but it was Hornet 3.0/Korea, EF2000, Jane's F-15E, and Flanker 1.5 and 2.x for me. I dabbled with Jane's F/A-18 but never got too far into it. Hornet 3.0 and Korea were some of my favorite games back then and I'm thrilled beyond words to have something like the DCS Hornet module to enjoy these days.

It looks like the 2.7.1.6430 patch released today mentions a fix for this in the changelog. I just did a daytime flight in the Mustang and can confirm that it has been fixed, hopefully for all aircraft. Thanks for checking @NineLine

Thanks for the summary @Bunny Clark. I briefly played around with the new HOTAS/TDC features and found them marginally useful. I have my TDC axis sensitivities relatively low to help with fine adjustments when targeting so it's too slow for me to move it edge-to-edge on the DDI. This is made worse by the way the cursor resets to the upper left corner after hitting the TDC depress when selecting something like the range arrows. Some questions: anyone know what is "TA" mode on the A/G radar format? what is EXP: FAST? I'll be digging around the docs and experimenting so if I figure anything out, I'll post here if no one answers. I also need to find info on the new RAID features (SAM and 1LOOK).

That's some crazy public school math LOL. (j/k, I think the use of the word "ratio" saved you)

Ah, thanks. I don't think my post was very clear as the responses from @=Panther= and @Shimmergloom667 did not address my actual question. I already understand about cycling through tanks and setting date/clock/TZ. What I was trying to figure out was what "SP" signified and the various numbers that are displayed next to "SP" when you press QTY or up arrow after MODE is pushed a single time. It seems like this is something that is cosmetically implemented but has no real impact on operation of the plane?

When the MODE button is pressed once, "SP" along with 3 digits is displayed. I've only seen "888" on the first press. If "QTY" or the up arrow button is pressed, the number cycle through different values. What does "SP" mean and what do the various values that cycle though indicate?

Welp, crashses while loading 2nd missions are back.

I was having consistent second-mission-load crashes today. I saw maybe 6-8 of them. I saw the latest posts here and installed Windows 10 20H2 KB5001391 and did about 4-5 mission reloads with no crashes. I'm cautiously optimistic that this update has done something to help. If the crashes return, I'll update here.

I bought the P-51 on the last sale (April 2021) and noticed that daytime flight hours for the P-51D and P-51D-30-NA are not logged. Nighttime flight hours are. The weird thing is, I could have sworn this was working before. I noticed this when I checked to see how many hours I had in the Mustang because I was starting to get more consistent with my takeoffs and landings and was wondering how long it had taken me. The TF-51D appears to log day/night hours properly. So do the other modules I'm currently using (Huey, Hornet, and starting Bf-109). I tried creating a new pilot and even deleted the logbook.lua file to start from scratch but neither action helped. This is not a big deal but I was wondering if anyone else has seen this problem.

Thanks @Flappie for collecting all these troubleshooting steps. FWIW, I tried all relevant ones and no luck. I still get the frequent second-mission-load crash. Sometimes even the first mission load crashes. In summary: Empty fxo, metashaders and DCS temp folders (done) Remove ReShade from DCS (n/a) Installing the latest Nvidia driver 466.27 (n/a, AMD GPU here) Reduce preload setting to 100000 (done) Set V-sync to "application controlled" in NVIDIA options (n/a) (more radical) Reset all NVIDIA settings (n/a) Remove mods and run a DCS repair (done, ran the full repair) Update Windows 10 to the very latest version, including optional updates (done, digging the new dark mode Start menu) Manually setting pagefile size (done, set to min 16GB, max 32GB. No effect, reset to default) I'm confident you guys can find and resolve this crash. Thanks for the continued support and hard work to get this resolved!