markom

Sad there is no 737 mentioned here.

+1 for this. had it happen yesterday, as well. i died, so wasn't too upset about it, but just adding to the voices. EDIT: I just successfully completed this mission, and had the same. It looks like something is broken in this mission.

To add for the next step... Once you arm your laser, and you set the codes to match, you will once more see this same exact thing, and at that time, that will be normal. You will at that point need to do one of the two things: Manually trigger the laser (on FLIR, select TRIGGER; then use gun trigger on the stick) Press and hold the weapon release button for a few seconds. That will fire the missile and laser.

I know this is all virtual and gameified, but it DOES feel good, doesn't it? A big win for me is that I no longer have to avoid all those wonderful campaigns. I can now fly and enjoy them. Onto figuring out how to not get killed the moment someone looks at me.

If your launch bar is down, ground crew will not remove the chocks. Make sure it's retracted before you ask them to remove the chocks. Your parking brake should also be on, but I am not 100% certain it's the operation blocker. Launch bar is.

Well, Viper in DCS is, essentially, a giant single-cell nylon fuel tank with engine on one and cockpit on the other side. If you even look at it sideways, bingo

Oh, if *that* upsets you, you should see how deadly accurate they are with a diving F-16...

I have not looked at the sound to the coalition, but "radio transmission" feature, which also plays sounds, has a delay option. Using that feature, combined with multiple transmissions, and some fairly trivial timing may do the thing you want.

So, a few weeks after my previous post, I am off the ATTH button, and can refuel from 2500 lbs to 10700 in about 4-5 minutes, even with the tanker turning. No curvatures, no changes to the controls, just a bit of practice in almost every mission. AAR is now the part of the mission I most look forward to. It's really great and easy once you go over that initial hump mountain. Key points are really, gentle control inputs, one millimeter at a time, keep in mind there is a reaction time between your inputs and aircraft, as well as aircraft and you noticing it. Don't over-do, cut your inputs in half (I think Spudknocker had this advice in his video). You can do it. It's hard. Probably the hardest thing in DCS, but... it's doable. Patience and dedicate time to it.

If you have Marianas map, I may have one for you to play. Would love the feedback, since I have a storyline I'm thinking of developing into a campaign.

Every landing is an aborted go-around.

A bonus points for those who can land their Hornet/Viper on Harris Ranch for steak

I... swear this is how it worked yesterday. I was going nuts. Sadly, I was unable to reproduce it. Here are my two attempts and the mission. Apologies for wasting your time, I suppose. In this mission, there are 4 aircraft: Player, F/A-18 Lot 20 Flight-1, AI F/A-18C Flight-2, AI F/A-18C Lot 20 AWACS to aid in locating other aircraft. Flight-[12] are both configured to fly straight ~20 mile legs forming a rectangle, at 15,000 [F1] and 20,000 [F2] feet MSL and 350 kts (groundspeed). The goal is for Player to attempt to fly a close formation with both other flights for 60 seconds. Player aircraft is set-up a few miles behind Flights-1 at the same altitude and speed initially. After completing this, the Player should proceed and form-up on the other flight. To aid the mission, there are triggers that display the "formation" status (within moving zones of Flight-1 and -2, as well as their altitude). Expected behavior: * Flight-1 and Flight-2 fly their "pattern", as configured, with minor deviations. FA18C.trk FA18CLot20.trk Formation Test.miz

Wilco. Coming up later today.

Interesting. Did you use "F/A-18C block 20" for the AI? That's the one I specifically had a problem with. I need to pretend to work for now, but I will send the track later today.

[ this is trivially reproduced - I don't have a track file availabe, but am happy to add one ] I was trying to set-up a simple mission in which I am supposed to fly formation with the AI, where AI would not be a wingperson, but just a plane flying on a predictable path. Since I fly "F/A-18C block 20", I set-up the AI plane to be the same. AI was configured for altitude of 20,000 ft and 300 kts speed, and I was set-up a few miles behind. The simple goal was to form-up and fly with the AI. As soon as would approach the AI, it would slow down and keep slowing down to the point where my aircraft would start stalling. I could never position myself behind the AI, only in front. They would somewhat follow, but never "permit" me to form up on them. After spending a few hours, and realizing that I had a similar mission where I successfully formed up on Su33s with my Hornet, I changed the AI from "block 20" to just a regular AI F/A-18C... and whoa -- it no longer did that. It flew a predictable path, at a predictable and configured (to my utter surprise - ground) speed. To me, this does not sound like an expected behavior of the AI.

Sounds like you had... boatloads of fun

Did you hit something? This sounds like the way DCS renders "pilot unconscious due to sudden G-force change".

Never tried A10, but I spent some time in DCS F16 before playing with Hornet. Really, you need to forget all about the SPI as a concept in '18. It will not help.

Or... you can treat this as equipment failure on the carrier and proceed with the mission. You should always be able to find the carrier (ground radar + flir are your friends). While, yeah, things failing is annoying, but all sorts of failures happen irl all the time :-)

Perfect - thank you for your patience in explaining. It's a lot more clear now.

For underlined section: used... when? When doing what other thing - or at any time?

Sorry for bluntness - this is great, and I will re-read it one or two more times because of curiosity, but... it doesn't actually answer my question as to what the chart is showing. You are wonderfully explaining why X is happening, but not what X is

I remember seeing this chart in the past thinking that this is great, but something is missing. What is missing is... what is this chart showing? I.e. it shows some channels degraded, but... under which conditions? Is there a wider context/post that explains it? Specifically, are these channels that are degraded when Link16 is used, or something else? Further more... if those channels are in use, are they themselves degraded, or Link16 (in reality, it should likely be both if they overlap, but may not be modeled in DCS).