Chipwich

Did you use the F10 menu per the docs? I'm through mission 13 and not having a problem at all with this. I usually giving Transport command via the F10 menu, then my four ship element as usual, via VAICOM. You have to also be on the right channel, A. If you were chatting with the control tower on D, don't forget to go to A to talk to Transport or your element.

I wonder if the is map related, since it seems to work fine on the Channel and Normandy maps.

I'm through mission 11, and one thing that I've learned is to keep White flight away from flak, at least at low altitude. I had to fly the low altitude ingress missions again at altitude to have a chance at not getting killed by a cold bore shot approaching the target. One shot one kill of my Mustang for two of them. Unrelated and not high priority, but on the topic of AI I've noticed that in the large bomber formations, a few get taken out on the way to the RV. I'm going to assume due to collisions.

Yeah for me the last 2 or 3 updates have required me to edit that file. But VAICOM does the same if you are running the open beta version, so after every update I fix those 2 at the same time.

I think for the F10 commands , you have to use the Options command. F10 is for mission builders to expand the DCS coms menu and therefor is usually customized. Otherwise, you can use the regular VAICON commands like, "Request start, taxi, departure." <- not needed, but I do it anyway out of habit. "Flight join up." "Flight engage bandits." "Flight engage ground targets." "Two cover me." <- use this one a lot "Flight return to base."

Keep your speed up. Be very aware of your pitch attitude in turns. If you get sloppy and pull your nose above the horizon, you will bleed speed pretty quickly and the controls will get mushy. This is easy to do at altitude because your normal visual queues are different. You must be more reliant on your attitude indicator to monitor pitch. A little trick that you can use is when in a turning fight, is keep your pitch attitude slightly below the horizon. If the bandit is not using the vertical and just trying to turn with you, being slightly nose low will allow you to gain some airspeed for a small loss in altitude. Once you gain an advantage in the turn, be mindful of your altitude with regards to the bandit. Your goal should always be to keep him in front of your 3-9 nine and remain above him. It’s a subtle differences in energy management, but WW2 aircraft performance are close enough that the little things are important. It’s easy to want to pull harder once you get the bandit out in front to get your guns in him, but you’ll usually get a better shot if you are patient and stay in lag pursuit as long as possible. Google lag and lead pursuit for diagrams and explanations.

This bug appears to be fixed now. Just tested a 4 ship departing the Tarawa and all got off fine. Thank you.

Yes, I should have stated that I'm aware of the aircraft limitations and that IMHO, you should be able to keep up with climbing AI at something like max continuous, 46/2700. But since it's a known bug for all DCS WW2 aircraft, chose to push the engine a little harder, something in between max continuous and military. Once you reach the bomber stream, you can throttle back to max con and easily patrol in your assigned position, then go to military when engaged. I do keep an eye on temps and adjust MP, RPM, and coolers as necessary. My philosophy is that since it's broken for all of us and the AI, I can either fudge a little and enjoy all of the missions and campaigns while waiting for an update, or watch them fly away. The AAA are too accurate too, but that's another discussion.

Strange, I’m flying Reflected’s Blue Nosed Bastards campaign and not having trouble keeping up with climbing AI. I do trim to keep the ball centered, pitch to 175 kts, MP between 51 and 56, RPM around 2900. This is to about 24k-25k to get just on top of the bomber formation.

For the logbook edit method, follow the steps in this video. It's about 3:44 in the video in case my link doesn't work. Stating the obvious, but it's always a good idea to back up your logbook file before tinkering with it.

I'm listening to the Audible version on their cloud player while flying the missions. If you are enjoying this campaign, you'll most likely find the book compelling.

FWIW, I just finished Mission 03 and the coms worked perfectly. I use VoiceAttack with VAICOM and for whatever reason I had to transmit on radio 2 (TX2), but A, C, and D channels worked fine. I was able to listen to the bombers on C, command my flight on A, and chat with the tower on D. No problems. Enjoying the campaign and the vintage radio programs are a nice touch. Thanks for another great campaign.

Host a multiplayer server and add one of the two co-op missions from the campaign folder.

I noticed this as well. They drop their flaps to STOVL, then the nose wheel gets chocks preventing the plane from moving.

May be related, but on all of my carrier missions, the AI Harriers get wheel chocks right as they are ready to takeoff. You can see them put their flaps in STOVL position, turn on their landing light, then the wheel chocks appear, preventing them from departing.

SSS right x 2

No. I cycled the STO stop a couple of times to make sure. The animation showed it moving completely forward to 35 and completely backward, but the nozzle lever would stop at 75, which also matched what was indicated on the cockpit display and HUD. I wish that I would have captured video. Anyway, it worked fine the next flight.

I had a flight the other night and during a case 1 recovery could not get the nozzles passed 75 degrees. I caught it while in the grove, executed a wave off, flew a longer approach, but no joy. I was able to recover doing an abbreviated VL to short landing roll with the nozzles at 75. I had never had this happen before and wondered if I had damaged the flaps during the flight somehow that was preventing full nozzle travel.

Good luck getting your mobo replace @joey45. Nothing like having to rip your whole rig apart, but perhaps you can use the time to tighten up some cable management or replace any other parts that need a refresh. Does anyone know if the '81 version works with a 4-ship in multiplayer? I see that #3 gets placed off the deck, but that might be an ME convention. Would like to launch 4 clients off of '81 if possible. Thanks.

Thanks @Wizxrd. Just what I was looking for. I had seen the END MISSION action but unsure how to implement the time part. Also like the way you've shown how to use the F10 menu. - cheers

Is there a way to program a MP mission to either end after an amount of time, or before via the F10 menu for clients, so that a dedicate server could load the next in a list? Thank you.

Poor choice of aircraft by the author it appears.

To me it looks like the aircraft are configuring for a STO without the ski jump and when the aircraft reaches a certain pitch attitude, using default logic to reduce pitch input. I have no idea how aircraft are programmed, but it appears that they need a 3rd takeoff profile, for lack of better phraseology, for a ski jump takeoff. I.E. 35 degree nozzle and maintain appropriate pitch attitude for STO until the aircraft is cleaned up. Anyway, like you said, either a RAZBAM or ED issue. FYI, just tested AV-8B on Kuznetsov 2017 from parking hot and all AI ended up taking a swim.

Yes. It doesn't seem to be a problem with the ship, but with AI pilot behavior. Everything looks good until they leave the ski jump, but then they don't hold their pitch attitude. Instead they lower it, the plane begins to loose altitude, and the AI ejects. If there was a way to have them hold their pitch attitude, I think that they would be fine. Another thing that I noticed, which might not have impact, is that their nozzle setting looks more like 50 than 35. I think that I remember in one of the Harrier books that 35 degrees more common when using the ski jump? It seems right to me when I use it.

Some troubleshooting steps I might take are: 1) try using the default port, 10308 to make sure 10311 is not conflicting with something else. Unlikely, but worth a shot. 2) Review the port forwarding on your firewall. You should be forwarding from your server's LAN IP, both TCP and UDP on port 10308. Share a screenshot of your port forward setup if you like. 3) Is the check box for Public server checked? 4) Are you double NATed? Like your firewall has a private IP instead of public. What's the WAN side IP of your firewall? It can be dynamic, just not private. If you go to wtfismyip.com, does the result match the WAN IP of your firewall?