Razor18

Can't open you lastmissiontrack.trk. Did you make it before the latest update?

Isn't the right engine the first to crank in the Hornet?

Yes, it is working for CASE III running MT.

Sorry to say, but looks to me the problem is somewhere in your setup rather than being general problem...

The paddle switch generates in fact two values: one, when you "pull" and do not reelease it ("JOY_BTN8"), the other one when you release it ("JOY_BTN 7"). If you look carefully in the binding screen after pressin "Add combo", you can see how the two values are used. The same thing borked my paddle switch (AP disengage while held) usage in the F-16, because when I bound it, I pressed and also released the paddle switch, whic made my bounding using "Paddle switch release" instead of "Paddle switch pressed".

Well, without a track it is a bit difficult to tell. Do you turn by looking at the boat, or by looking at the HSI? At least a screenshot about either one would help a lot. EDIT: do you happen to have a TacView track maybe?

Oh, my bad then...

I don't know the T-45, so sorry if stupid question, but did you try to tune the radio to the carrier's frequency and call ATC using the comms menu?

I have the same problem after checking all the possible sources of fault mentioned above. Just start a free flight. You can activate Auto Pilot by switching to ALT HOLD, but after you depress the Paddle switch once, you can not activate the auto pilot again by switching PITCH to A/P OFF and back to ALT HOLD again. Anyone else?... EDIT: Nevermind, I've found the source of trouble. It is the key bindig for the Winwing Orion 2 joy, where the paddle switch has both a PRESSED and also a RELEASED button in The SimAppPro, similar to the 2-stage trigger button. So if you want to bind the PRESSED button to any function, then you need to right click the proper cell, choose "Add combo" in the control binding screen, and hold the Paddle switch pressed, when clicking on OK. If you just press and release the Paddle switch, then casually press OK to confirm binding, then the key you will bind for AP override is the RELEASED state. So then while using the joy, when you press and hold Paddle switch, you did in fact not even override ther A/P yet, because the override starts when you released Paddle switch. And then it stays overridden, and in fact never returns to active A/P again, because RELEASED button stays RELEASED forever, after releasing Paddle switch. Sorry if complicated, much easier to implement,

If you undesignate, TGP will jump way off. So rather just designate by pressing TDC then adjust as necessary.

Thanks !

The Guide was updated on August 14. I didn't find any change log, anyone knows what's new in it? EDIT: Nevermind, I just found it, it's the datalink...

Hi There, apart from sifting through miles of change logs in recent months, is there any place where you can find the most recent/current procedures the way they are supposed to be done "as of today"? For instance the MIDS startup, the NAV alignment and all other minor things that are just a bit different lately, than it was? Or is the guide updated to all the latest fine tunings and little nuances to avoid or work around little bugs? Thanks for pointing it out...

OK, what is the requirement of a "tight orbit"? A radius of...?

Not to hijack the topic from Z0mb13, but in my latest attempt I also had some weird behaviour by Matrix. See TacView file attached. Tacview-20240828-161622-DCS-SYRIA M11 ZERO HELO.zip.acmi

Hay Badger, Tacview-20240825-181458-DCS-SYRIA M11 ZERO HELO.zip.acmi

Yeah, thanks, I was looking it up everywhere, also in the document "we don't say the name of", and it also said, after aligment says "OK" and switching to IFA, if there is no GPS data when switching, HSI goes to IFA RDR. Thanks for coming back though...

Oh yeah, when you realize you have rain on your canopy inside a hardened shelter... (I now it's ED...) Just a minor side question: I usually take off from carrier, so I didn't remember when finishing GRD alignment and you switch to IFA, on the HSI the message "IFA RDR" appears with a countdown. I did not find too much info about it in either guide, what is it...

Tried to re-run it. Now problem was, if selected AUTO, and was heading straight towards the TGT diamond, the AUTO ASL was on the right edge of the HUD, so totally off. If I switched to CCIP, then the bomb fall line was not vertical, the cross "pointed" about 30 degree angle to the left of the HUD bottom (towards 7 o'clock from the center). Probably DCS bug, I think I have read about it sometimes earlier. I still could CCIP them all on the runway, but with AUTO it would have been totally impossible.

I guess you mean 1400 barometric, right? Because I was at 300 feet AGL. So you mean I have to drop AUTO, strictly from 2000 feet? Should I use some intervall to success, or any more requirement?

Hay Badger, planted 4 RET'D bombs in the runway, still fails me in Mission 9 on the climbout off the TGT. MODE was CCIP, MFUZE was NOSE, DRAG was RET, streched them along the RWY manually. TacView attached. Tacview-20240823-160053-DCS-SYRIA M9 MILK RUN.zip.acmi Oh, shoot... Just occured to me, when checked at start up on ARM screen, ARM DELAY was 2 seconds but I dropped from around 300 feet, bomb fall time could have been around 1.5 seconds... Dang...

Sorry, it was M4, TacView attached. I'm not sure I understand: "If i set the zone at 7Nm radius you will get the trigger when Ford is 7Nm from the Carrier as measured using TACAN..." Wouldn't it be exactly the point to set the trigger when you are 7 NM from the Carrier/TACAN, and WP0 should not play any role?... Sorry, I do not know too much about Mission Editing... Tacview-20240819-151945-DCS-SYRIA M4 NIGHT MOVES.zip.acmi

No, I boltered and went around. No way I ever dropped below 40 KTS, I wouldn't have been able to take off again I guess... ED probably knows their Case III departure picture to be wrong, as in their text above the pic in the SC Guide, they also write: "Following the launch, climb straight ahead at 300 KIAS, crossing 5 nautical miles from the carrier at 1500 feet AGL or above." And in fact if you look at AI Case III launches, they also don't do clearing turns. I understand, but maybe you can set the TACAN distance as a trigger? Other recent F-18 campaigns did the same feature flawlessly, "release" message came exactly at 7 NM TACAN distance. But it's not that big problem after all...

Hi Badger, some small things just FYI: At least on Mission 5(?) (wondering if on others too) mission is declared "completed" as soon as you touch the deck, even if you bolter and have to go around. Case III departures do not have any clearing turn (as shown on the kneeboard graphic), just climb straight ahead (on BRC), crossing 5 NM at or above 1500 feet. On Case I departures, messages triggered by crossing 7 NM come way too late, sometimes even beyond 8 NM. Just a feedback...

Sorry, I guess I mixed up something. I also set GSPD to 410, maybe that threw me off...