Rhayvn

Yes, latest MOOSE version.

I have tried but it has some very odd behavior. Helicopters will not start on the helipads in the helicopter only bases but they will land on them. Helicopters set for vertical takeoff and landings will taxi for takeoff around certain airbases depending on which spawn point they originated at. They always use the runway for landing. A huge percentage of the first aircraft respawns all fly to and land on the Tarawa despite every RAT setting I tried. Many larger aircraft will still spawn in smaller spawn points and hit objects at the airfield either on spawn or while taxiing, also despite the RAT setting that are supposed to prevent this. Small and grass field bases will be chosen for takeoff (They air start) or landing if you don't specify the departure and destination bases. Despite RAT settings to exclude them. They work fine in the air, but not so much when they have to touch the ground for any reason.

Same bug as the SA-15. Any group a ZSU-57-2 is part of will no longer move after the 57-2 has stopped to fire.

The HVAR rocket pylons create drag and do reduce the maximum speed along with other drag effects. If you ever arm HVARs, even if you re-arm and remove them, or try a loadout without HVARs after landing from a mission you carried and fired them, you can never remove the pylons again. This means that after they are on the plane once, the pylons, and drag from them, remain until you get a new client. Can this be corrected?

Actually all of the keybinds (That I use) that were not working prior to the patch are now working. Also, on our MP server, landing gear state shows the correct up or down state for other player F4Us. The default view was moved back as well. So there were actually a lot of fixes done in this patch.

Neither did Essex carriers with zero crew on them, but thanks for that amazing info and contribution!

@-Rudel-Fully understand that. This is a MP CV where we need to takeoff and land so the deck needs to stay mostly clear. Attached are some screenshots of where static personnel were placed. We could try adding one at a time until the desk fouled error appeared, but it would be tedious to do that. If there is a diagram that shows where static can and can not be placed, almost exactly like the ones you have above, that would help. If the dashed line in the right hand diagram is that marker, then great! We can move all the statics ahead of that line.

They work fine in Single Player, in MP, their tails fall through the deck. Also, it would be good to get a diagram of where we can place static objects and not get an LSO 'Wave Off - Deck Fouled' call on final.

I did a test for a few different aircraft that I have at 5000, 12000 and 24000 feet. The speeds listed are TAS and what you can sustain pretty much indefinitely in level flight. For the clean aircraft, if there is a '/' the number before is without water injection and the number after is with water. For the GA lines, that is Ground Attack and are the speeds with a full load of rockets and bombs with the number after the / as the speed after dropping all the ordnance. It's pretty close to the P-51 in overall speed, depending on the specific altitude (Due to SC gearing most likely) and beats the 47 and D9 handily. They can only match it with water/mw90 active.

It is the same. There is no speed change after firing rockets and you seem to permanently have the drag associated with them. Bombs and fuel tanks appear to work normally.

Same, with multiple aircraft types. Current mission has at least 3 red and 4 blue aircraft doing those circles.

This is an old bug that used to permanently stop SA-15, ZSU-57 and SA-11 once they fire. It is back for the SA-15 but not for the ZSU-57. I have not tested the SA-11.

Can someone point me to the right warehouse item to enable loading the pods in the screenshot? All of the bomblets have plenty of quantity. I can find nothing else that seems related.

This is likely related to a change some few months ago where the AI will select one target to attack for each AI aircraft and the other AI aircraft, if they don't have a target of their own (Or they shoot it down) just fly around not engaging the remaining hostiles. This is most easily seen in a 2v2. Each AI aircraft will go after one of the opposing aircraft. When one of the aircraft is shot down, the other fight will stay as a 1v1 with the winner of the other 1v1, now free, never trying to assist it's group mate. It will fly around nearby, or even try to get in formation with the still engaged friendly. It will only engage the remaining hostile if the 1v1 is lost by its group mate. This is truly silly behavior because it makes all fights 1v1 duels even with multiple aircraft around.

Sent you the file. Also, the total time seems to be off randomly. Like in game for 78 minutes according to tacview but the flight in logbook may show 325 minutes or some other odd amount. I don't have an example of one of those logs.