Bankler

VERSION 7.4.0 You can now download version 7.4.0 in the Original Post! Spring update time! It's spring, and it's time for a new update. I can't believe it has been 6 years since I first released this mission. It has been downloaded 33,025 times across the different versions. I wonder how many traps you guys have done by now. Fixing the auto-cockpit-setup A while back, there was a Hornet update in which they revisited the INS. This gave us a special state for the HSI page when you start airborne with the INS knob set to IFA, that you see for around 8 seconds before the HSI shows the old familiar set of button functions. Unfortunately, this change caused the timing of the auto-setup to fail, and instead of setting up the time in the HUD (TIMEUFC/ZTOD) engaged the RALT A/P. Not ideal. But this is now fixed! Discord and Patreon When I first headed out on this journey, I had no thoughts on such a thing. But enough people have told me"You have supported this thing for 6 years(!), and it has helped so many people... maybe you should let people give something back if they want to?". So, here goes! Please join the Discord to talk about DCS and carrier stuff. Maybe we can get some flying going on as well? Also, join the Patreon for some exclusive extras. Check it out! I wonder who's going to be my first patron, probably my mom... Discord: https://discord.gg/bYB4jXQWQW Patreon: https://www.patreon.com/banklerdcs CHANGE LOG 7.4.0 * Fixed a problem with the auto-cockpit setup for F/A-18C, where the RALT A/P was engaged. This started happening after a recent INS update to the module. * Tweaked the limit to what counts as a downwind extension during SHBs. It now gives you a little more room. * Updated Moose. * Started a Discord server. * Started a Patreon page. Enjoy!

That is brilliant! Good work!

I finally got some time to look at the issues with the RALT being engaged during the cockpit auto-setup. It turns out that some new feature sets the HSI in a certain mode for around 8 seconds when you start airborne and the INS is set to IFA. This removes the TIMEUFC and replaces it with a SEA button, until it's done with... whatever it's doing. Hence, the auto setup failed to press TIMEUFC, leaving the UFC in the AP menu instead of going to the TIME menu to set LTOD. Meaning RALT was pressed instead of LTOD. The solution was to delay that button until the INS thing is done. This is a temporary beta version. I'd be super happy if you can test it carefully, and let me know if anything else seems off. If everything seems okay, a proper release will soon replace 7.3.0 on the first page. Thanks for the patience, everybody. Yours Bankler nullPing @Hecate_Megami etc TrapTraining_MP_SC_T-45C_Fix.miz TrapTraining_MP_Fix.miz TrapTraining_MP_SC_Fix.miz

Yes, you are free to make a custom version and release it, as long as you leave the briefing text in there (but you can also add some text explaining what you have done). No, you can't see that from the cockpit. Normally you get that info from Marshal as you check in. In DCS, the easiest "cheat" way is to press alt-f9 to see the LSO view, and look for what it says next to SH (ship's heading). Thanks for the pointer!

Correct. And for clarity, the mission will say "fast" if the AoA is off. (The mission doesn't measure airspeed)

Thanks for the heads up. I will look into it! Probably ED changed some button IDs. Did you also noticed any button now NOT getting pressed?

@Vyrtuoz It looks like the AGM-84 SLAM-ER is not being properly recorded in multiplayer. On the server tacview it seems to just carry on forward, while on the client of whoever fired the missile, the path is properly recorded and you see the missile connecting with its target.

Instead of picking another slot, restart the mission. The auto-setup can only happen once.

Representing Master Arms DCS community. I can verify these issues. We are typically around 10-14 client Hornets on a missions. No AI planes on the carrier. Almost every single time, there's an issue with the ground crew not reacting when someone approaches the catapult, and the "Request launch" command does nothing. It's sometimes resolved when another jet that is already hooked up takes off. Example: Cat 3 doesn't react. Aircraft on Cat 1 takes off, and suddenly Cat 3 dudes start waving you forward. As it appears in mp with lots of players, it requires lots of organization to record a trk, that is also small enough. Also, I haven't found an exact pattern when it happens. However, it's so easy to reproduce, that you should easily be able to do it internally, as long as you have around 10+ players available. Just spawn everybody, cold start, decide on a time when to start taxiing and take off, use various cats, and see what happens. If you already know what you need, that's awesome. But if a trk would be of actual use, I could try to organize a session and record it. If that's the case, do you want the server or a client trk file? @NineLine

Hmm. I had a look, and to me it looks like it's the CVN-74, which I imagine is the legacy carrier? Maybe I'm missing something (early morning here), but can you please take a look just to make sure you didn't download the SC / T-45 version or something? Just there, in this case. I think in other missions, they have positioned the ship as reference points. Imho this isn't a great way of getting a feel for the break, as you will make yourself dependent on where those are. So think of them as decoration, nothing else. Except from the one at the carrier's 6 o'clock. That is a reference point to where to fly over to start the script.

With the Sinai map out, it would be nice with the quite unique looking Egypt liverie for the Viper. Just like we got the nice IAF ones when the Syria map came out, I think this would make a lot of sense. I realize it's available as a user file download, which I appreciate. This request is to have an official one, not requiring extra downloads (which is quite a hassle for big communities).

Already located in the top of this thread.

Ok, good, then we are on the same page. As described in the bug report above, and as showcased in the tracks I provided, that's not how it currently works.

If you do that, in DCS (currently), your first bomb will hit vehicle 3. Is that correct or not?

I'm not sure then what you mean by "group"? Are you referring to the group of bombs? Let's say you set QTY to 3, and interval to 500. You put the CCIP reticle on a tank and hold pickle. Should bomb #1 or bomb #2 hit the tank?

Ok, nice research! Then that means it's currently bugged (at least for CCIP), unless I'm mistaken.

Just to clarify. I don't think this is an AUTO exclusive issue, but goes for CCIP as well. But I'm certainly not sure by any means. It's just the way I remember it working after ED fixed/adjusted it last time. In some ways it's confusing how this is even possible to implement for CCIP. But I guess by extrapolating the currently calculated aimpoint by, ehm, (QTY setting * Intervall setting) / 2, in the direction you're flying, and drawing the reticle there, would get it right. Would be nice if a Hornet guy could chip in on how it works. Weapons questions are always tricky, but could very well be such a trivial thing that it's not a confidentiality issue. And then again, the way it works now (aimpoint always on the first bomb's estimated placement) is absolutely fine and makes just as much sense. Just not sure if it's correct compared to IRL Hornet. Have a nice weekend!

Okay, here goes! Three tracks, though all show the same results. CCIP, AUTO (explicitly set) and AUTO (automatically set by being in CCIP when pressing WPDSG). Note that I'm aiming on the middle building of the five. That's where the first bomb go. I'm not sure what's correct, but AFAIK it was like this when the Hornet came out. Then it was changed so that the bombs did bracket the aimpoint (i.e number 3 out of five bombs on the aimpoint, two before and two after), but now it's back to the original implementation, and I'm curious if that is intended or not? Hornet_Interval_Bug_CCIP_to_AUTO.trkHornet_Interval_Bug_CCIP.trkHornet_Interval_Bug_AUTO.trk

@BIGNEWY Do you happen to know anything about this? Cheers!

Yes. I can confirm, that at least around a year ago, and at least when dropping in CCIP (I'm quite certain it was the same for AUTO though, since it would make sense), if you dropped 5 bombs with a interval of say 500', it would put bomb number 3 on the aimpoint. Doing the exact same thing today, will put bomb number 1 on the aimpoint. I don't know what's correct. In my world both make sense and are just about equally functional. As long as you know what to expect. Not sure if this change was intended or not.

It is most likely (I'm speculating, but I'm approx 80% sure) because Wake turbulence is enabled in the missions where you're struggling. I suggest you disable it for now. While some aspects of the effect are really nice, there are a couple of massive problems with it. One is the thing you're experiencing. Another one is the extreme amount of time it takes to fade away, even making ordinary (multiple aircraft) overhead breaks dangerous. Hopefully ED solves the carrier issues, and implements two sliders for wake turbulence intensity and duration.

VERSION 7.3.0 You can now download version 7.3.0 in the Original Post! Fixing what's broken! Due to some DCS scripting changes, all missions using Moose stopped working a while back. The guys over at Moose were quick to find the problems and publish a new version. Thanks to them, and thanks to you who helped out testing the little test mission I posted in the thread, we are now back on track. Thank you so much! Happy landings! Have a nice holiday later this month! //Bankler CHANGE LOG 7.3.0 * Updated Moose, in order to get the mission working again after ED's scripting changes. * Changed overhead tanker TACAN band to Y. Enjoy!

Here's a very quick test version with updated Moose. I haven't tested it more than confirmed that the score starts tracking and I don't get any weird warnings in the log. Please test it if you have the time, and let me know if anything seems off. @zildac @captain_dalan @japagi @speed-of-heat @Richard Lim @Cobalt135 @Mad_Taz @Iriya @Cepheus76 @marcoy Thanks a lot for the reports. Much appreciated! TrapTraining_MP_SC_2_7_3_TEST.miz

I will try to find some time to look at it. I know that there was some problems with compatibility between 2.9.1 and Moose (which I'm using), so maybe it's related to that.

I haven't tried 2.9 much, so I'm not claiming you're wrong. However, since other people say they're not seeing this, I was thinking about a certain common issue when you mentioned that you can no longer trim to correct AOA: If you have used autopilot at any point during the flight, be sure to disconnect the AP using the Paddle Switch button on the stick. Simply pressing "BALT" (for instance) again will not take you out of autopilot, even though the : thingy disappears. You will instead go into CSS mode, and if that's what happened, it could potentially explain why you couldn't trim. Just tap the paddle switch and you will be alright. "The most basic mode of the AFCS is Control Stick Steering (CSS). CSS will attempt to maintain the pitch and roll of the aircraft without manual stick input. Roll input is dampened and pitch input is severely dampened. The trim switch is repurposed in CSS to command roll and pitch. Forward or aft stick deflection beyond a certain point will disengage CSS. CSS is engaged manually by pressing the UFC ON/OFF button in the A/P menu and also engages with all other autopilot modes." Again, not sure, if this is what caused your issue. So sorry if this doesn't help one bit. But it's a very common mistake.