tstorey37

Bump

Glad you found an issue, what did you find? I will gladly give it a try. Did you repost the campaign on ED?

Sandman, Twice now after receiving the knock it off message and RTB, the mission freezes and I'm unable to complete mission. I wanted to complete your training mission in NTTR before attempting your new campaign. I've enjoyed your work to this point.

I think that would be a great option, the more the merrier. But the practicality might be a little wanting in the online environment. In the real-world that is how they operate, but when you have an hour to fly are you going to wait for the next launch cycle? I would love to come back to the boat and have to wait for the next recovery cycle, but if Ineed to wrap up my play time, I will probably just exit. Again, great idea just not sure how long people will use it before unchecking it in ME.

I noticed that when I went back to get you pictures that it wasn't a static. I watched both of them drive all over the helo LOL I just figured if there was something you could do, then you would. Thanks for an amazing campaign.

Here are three shots, I believe this is Chevy 1-3 with the biggest problem.

Reflected, Not a major problem, I just finished #8 Alpha Strike. There were a couple aircraft fouling the landing area, and a F-14 was right on top of a SH-60. Not sure if something changed since you made the missions, but I just wanted to let you know. Tom

Thank you, I guess not seeing FL was throwing me off.

In the October 20, 2021 Update, this was entered for the RWR database: "AN/ALR-67 threat database updated to version RBA1: added Forrestal as FL, 19JS as TS, and SA-5 as 5." Where can you find the latest database information, hence the RBA1 database list?

Sabre- Only in the Qual mission

Sabre...Finally gave BFT 9 another go since 2.7 dropped and I read you all fixed this mission. On my missed approach, on turning to 040 at 260kts, mission was terminated for speed. At the time my HUD speed was reading 264kts. Again if I need to read Ground Speed somewhere just tell me. But I don't remember having to do anything out of the ordinary when I flew this mission in the A-10C version. Thanks for your help!!!

Why so serious!!! Enjoy what you got

Sabre...you have provided a very in depth training scenario for the A-10C II. I completed the basic training campaign in the C. But I wanted to do it again in the II, and I can see where you all have added some new material. I'm very happy, we'll just help you iron out the bugs.

Thank you Sabre!!!

This flight is getting very frustrating! To me the funnel we have to fly through is too small. I learned long ago to follow the waypoints, not the heading calls by the IP. It seems I am unable to follow the IP's directions on the missed approach. I stay 50 to 100ft above 7k so I don't get terminated. I stay around 250-260kts, cause I got terminated for being at 270kts. So for the Nth time today, I got to the 040 turn, at 255kts...terminate, terminate, terminate! What do you have to do to complete this flight? I read some where it was said to follow ground speed, but none of the other speed restrictions are so sensitive. I appreciate tight restrictions, but this is ridiculous. Is it a bug or just VERY tight windows?

I've been hook skipping for months! Maybe you got left out of the update for biting the hand that feeds you too many times! Why don't you just be happy you are still able to fly the Tomcat? My understanding is that after every update from ED, HB is franticly fixing a new problem. Then I am sure with 2.7 on the horizon, HB is again making sure the Tomcat will fly when that update happens. Either show a little respect, or go get your programming credentials and help HB solve your obviously immediate concern. I suggest you just show some respect for a service that they are providing all of us.

Also, check in DCS and make sure keyboard bindings still exist in DCS. I have keyboard button 3 mapped for Toggling the Taxi Light, and it stopped working. I checked in DCS and it was not mapped anymore. Take a look, maybe?

Gents, do you think some of the major problems with the deployment of 2.5.6 may be because of the Super Carrier? So maybe the sooner they come out with it, the sooner 2.5.6 becomes more stable. I would hope they are figuring out how to adapt the super carrier code to make the free carrier work, considering that is what's got us Navy boys in a tizzy. The carrier isn't working right! My $0.02

I just tested an incident that happened last night, and it repeated today. In an MP server, I can not use the radio with SRS while the Rearm and Refuel window is open. With the R&RW open, Comm1, Comm2 and ICS do not work while pushing Z. Thank you!

Thank you sir, appreciate the detailed response :thumbup:

Thanks Gyrovague, You had the loadout correct, 4 each on stations 3&6, 1 each on stations 4&5. You said after dropping the first two pairs that the single was expected. Is that cause of a release sequence or something in the WCS IRL? If the real Tomcat acted the same way all :thumbup: Thank you for looking into this, if you need more information let me know.

So on 9/14. I actually thought this was fixed, but last night I went up for some night training and the problem is still there. I went up with 10 Mk-82s. Intial setup was, pairs, as usual, two runs both drop pairs. On the third run only one bomb drops with pairs still selected. This time for the fourth run I set ripple quanity to 6, just to dump the rest of the bombs. Only three came off. I'm not sure where the problem might be, but it's not good if we can't drop bombs like we want in missions or training. I believe there is a bug, that needs to be looked into. Thank you

So I went out today with 14 Mk82s and they all dropped in pairs. Did HB sneak this fix in during the last update?

Bumping to see if you have had a chance to look at this issue. Listening to some Wing mates last night, I wonder if this could cause other issues as they were talking about bomb release order problems they noticed from the backseat.

IronMike, did you have time to test this issue? Yesterday, I went out with 8 Mk-83s to see if a different bomb would have different results. In short, same glitch, dropped 2 pairs and the last four came off as singles. I tried recycling Jester to pairs for the last two with no avail. So it definitely is a pairs issue not associated with the type of bomb.