Nealius

Upon further inspection, the defautl C-47 textures do not have a description.lua associated with it at all.

Standard version. I'll check the code for that explode on death feature and see if I can change that. I'm guessing it has a true/false line like the other features. So far I only have tracks on Marianas WW2 in the Corsair.

The bombs mounted on the trollies scattered around airfields appear to be CBU-52s, which wouldn't have been around during WW2.

The C-47 default liver has no name associated to it, being blank in the drop-down menu. Thus when the user has user liveries installed in their Saved Games, the default livery is unselectable:

The layers from the template seem to be missing. There's just a wireframe and that's it.

There seems to be something amiss with the logistics trucks when using 3.4. While strafing with .50cal the logistics trucks explode with a massive plume of dirt as if hit by a bomb; the standard DCS dirt explosion, not the VBIED mushroom cloud. They also detonate after only 1 or 2 bullet impacts.

People who like the Zero and want the challenge. People who can fly with teamwork and tactics instead of lolgitgudskillissue min-maxing mouth breathers. The Japanese community in particular would literally throw their money at ED if an A6M were developed. People also show their ignorance of history with these discussions. Sure the Zero was inferior on paper, but a large part of the IJA/IJN failure was stubborn doctrine and forcing good pilots to fight until they died, then throwing undertrained pilots into the meatgrinder. The Allies, on the other hand, had flexible doctrine and cycled their best pilots through as instructors to train the next cohort of new pilots, passing on vital knowledge instead of letting that knowledge die somewhere over a jungle in the Pacific.

I don't get any tailhook feedback. Only gear and flaps.

What standards? We have an F-35 in the pipeline.

Is there any way to tone down the lighting on the Fletcher class? They're super green.

If only we could hack in the hook physics from the Corsair.

Is this a recent change? In the past I've had Ju-88s using torps to sink LSTs no problem.

Do you have "hear like in helmet" checked? That tends to hide a lot of sounds due to it simulating the pilot wearing earplugs+skullcap+helmet.

But only Korea and after. WW2 USN/USMC nunbers are all over the place too.

There's also a loud clunk when they lock into place.

I saw those as well, 7A, 7B, 7C for example. I couldn't find any resources for any of them, even the tail letters, except for suggestions to buy a book called "The Squadrons and Units of the Fleet Air Arm" by Theo Ballance. Which of course is out of print and $200 for a copy if you can find one

So in the example of the last Seafire, 115, the aircraft number is 15? I wonder which bureaucrat in the Royal Navy made this system because splitting the aircraft number with the roundel (and only on one side of the fuselage) makes zero sense whatsoever. Zero logic. Zero consistency.

The port side is wrong. It should be showing 1-20 not 12-0 when "120" is put into the mission editor. Did you look at the first two images? Only the starboard side shows "single seat" then aircraft number properly, while the port side splits the aircraft number with the roundel instead of keeping the same format as the starboard side. What would the numbers be in this case? I've seen "2" "5" and "7" on Seafires despite being single-seat, as well.

I'm still trying to wrap my head around the Fleet Air Arm numbering method as it seems to have changed frequently during the war, but for 1834 NAS as depicted in the livery we have the format should be thus: Starboard side x ( ) yy Port side yy ( ) x Where, from what I can see, "yy" is the aicraft number and "x" is some larger organizational structure number; perhaps ship or squadron. ( ) is the roundel. However the in-game system only works for the starboard side of the aircraft, and the port side format is corrupted to xy ( ) y. In this example the number should be 1-20 but is corrupted to 12-0: If I try to get the port side to work by inputting 021 I get the correct format on both sides, but the number is wrong, and the starboard side has an errant "2" that appeared out of nowhere.

If my landing speed is too high I will bounce every single time.

The legacy weather system still works. Select "nothing" for the cloud preset, increase cloud density to 9 or 10, then "thunderstorm" will appear in the precipitation drop-down menu.

There's also a lot of uneven taxiways on the south side of the airfield, where starting cold will have you rolling away if chocks aren't placed by default. I've also tipped a CH-47 over due to an invisible bump at the intersection of two taxiways.

Most of that isn't in the current build. Is that fixed for the next update? There's no statement clarifying whether this is a changelog or an internal fix list, though it seems internal since a lot of those items are not in the current build.

What about the AI A-6E? That was slated to be released around summer 2023 per HB's official Facebook: