Reflected

I'm not expecting not to touch the brakes, I know how taildraggers work. What I'm saying is that the US Warbirds' rudder has absolute zero effectiveness at taxi speeds right now.

Ok, so I'm not just imagining things...

thanks

I just saw this video and it reminded me of something. With the exception of the Spitfire I can't make any of the other warbirds turn on the ground or stop turning by using the rudder only, without differential braking. When I taxi the Spit, and add a burst of throttle, say 1500 RPM, the rudder can initiate a turn or stop one. In combination with the brakes it's a nice experience. In the P-51, P-47, 109, there is absolutely no point touching the rudder, the only thing that can make them turn are the differential brakes. Stopping a turn requires so much braking that the plane just stops (if I taxi at the recommended speeds) I wonder why it is so? Please please don't turn this into a generic 'taildraggers' thread, and yes I know about tailwheel locking mechanisms. Don't hijack the thread with those. It's about why the Spit's rudder has some (little ) effect, and why others don't at all.

@MAESTR0 beautiful update, thank you! Can you please confirm if any of the parking spots changed at any of the existing airfields? Placement or numbering, anything. Such changes can potentially break missions and campaigns and it would be nice to know if I need to check/test anything. Thanks!

+1, I'd also love to see some Iranian bases on the map. So much historical potential for mission makers...

Yeah, happens a lot with the ground AI. They deviate from their path so much, they basically have free will... they deserve to die…

The Tomcat has 2 radios. If you're on the same freq on radio A, but you're telling him stuff on radio B, he won't hear it.

In any case ED acknowledged there is a problem and they’re looking in to it. The best everyone can do is to provide simple tracks showing different aspects of the problem. Keep them coming!

I just replayed mission 3 of the Wolfpack campaign, to see the extent of the damage. It's a big 16 vs 12 dogfight. This time I was the only one opening fire at straight flying 109s. Nobody else fired a shot

Let me officially announce my next project: Red Flag 81-2 Campaign for the DCS F-4E Phantom. Period correct maps and charts, dynamic debrief, interactive checklists, hand signals and formation signals, and basically the same study level realism that you can see in my other campaigns.

Let me officially announce my next project: Red Flag 81-2 Campaign for the DCS F-4E Phantom. Period correct maps and charts, dynamic debrief, interactive checklists, hand signals and formation signals, and basically the same study level realism that you can see in my other campaigns.

Please keep the tracks coming in the public thread. I can keep bumping my reports in the closed sections, but that's just me whining alone. If a lot of people post a lot of different tracks (preferably simple ones), it's more likely to get fixed.

Oh and one more weird thing I noticed. E.g. in the last mission of BNBOB. The fight starts on the deck, but after 5-10 minues, the AI is turning in circles around each other at contrail altitudes. So instead of descending fights, running OUT of energy, they somehow get to higher and higher energy states. Weird. Never happened before July 2024, not for the 5 years this campaign has been out.

I also find that when I do a big AI vs AI furball, they score way less kills against each other than before. In this track 4 AI were shot down and it took 10 minutes. The other problem is sometimes when 2 AI flights merge, one or more flight members just break away, do a lazy 360 before - maybe - reengaging. Mostly 190s. See track. And the WW2 AI's spotting/ detection range has severely deteriorated too. In the track, trained AIs only detect each other head on at 2.5 miles. ww2engage5.trk

Thanks, I also forwarded to Nineline, he agrees that something is defo wrong.

Something definitely changed, but the people who did it, and who can fix it are not checking this section of the forums. Can you please report it here? https://forum.dcs.world/forum/104-western-europe-1944-1945/

Hey, thanks a lot for the feedback! Happy you enjoyed the campaign As for the ATC chatter - I wish I could have included a wider variety of comms, but it's just not publicly available. That's all I could find on the web.

Thanks! Yes, that’s possible. It never happened to me for example. So I haven’t been able to report it without a log file. Perhaps you could try running a slow repair and see if that helps.

Please report these to ED along with your log files. Their load mission triggers are quite unreliable it seems

We’re all hud cripples aren’t we?

Yepp, you just need to hover low enough for them to be able to climb in.

1) what does it have to do with the supercarrier AI pathfinding? 2) the next item is 'controls' and it's only checked when you go to burner/ mil power depending on the model before launch

Hmm, good call on checking for a larger ambush! I never though of that. FSB Berlin…what happened there is something I read about in many Huey pilot memoirs so I just had to include it in the campaign Randomization is difficult because then you need a whole new set of voice overs, new rescue helo to land somewhere else, etc…the more you randomize the less details you can add, it’s always a tradeoff.

Check the kneeboard. It should go to standby.