4.11 - AI debugging

[jameson]

Lonestar, see 3'40" on:

http://www.youtube.com/watch?v=n-PwT...eature=related

It's normal behaviour apparently

[Lonestar]

Oh, interesting!
I've never seen that before, then all back!
Many thanks for the vid, jameson!

[Derda508]

Hi there,

as some people before mentioned, the "stealing" of kills by friendly ai is a real nuissance esp. for offliners.

Otherwise I love the new ai!

[Treetop64]

Gotta love the white text over the white clouds...

[Whacker]

Two things to add, one a comment and other a behavioral oddity.

First, I've noticed the AI crashing during some dogfights that others have mentioned, it's only been average or below and when they're pulling very hard at very low altitudes. While I'd agree that *some* of this should be "buggy" behavior, I disagree that it should be taken out completely. Historically un/less-well trained pilots often did crash their aircraft while trying to perform acrobatics. I wouldn't expect a veteran or ace to have an accelerated stall, but a rookie definitely could.

Second, I apologize if this has already been reported. I've noticed the AI will sometimes perform some rather odd, extreme maneuvers at low altitude in a turning fight. The main thing I see is them maneuvering wildly while upside down for a good 2 or so seconds while 100 ft or so above the ground. If I had to make a guess, it looks like they're trying to roll inverted to dive and separate, but they can't because the planet earth is in the road.

[IceFire]

Interesting. I will look for that behavior on my next several flights.

I have noticed the AI pulling too hard and crashing but it's been on the lower AI levels and I think this is in the realm of feature rather than bug. It's nice to see the AI pull too hard, screw it up and stall out. It looks very natural and realistic.... and it doesn't happen so often as to be regarded as artificial. At least not for me.

[Whacker]

Originally Posted by IceFire

I have noticed the AI pulling too hard and crashing but it's been on the lower AI levels and I think this is in the realm of feature rather than bug. It's nice to see the AI pull too hard, screw it up and stall out. It looks very natural and realistic.... and it doesn't happen so often as to be regarded as artificial. At least not for me.

Agree. It needs some tweaking but historically there were plenty of deaths and aircraft losses due to pilot error in all aspects of flight. I just read something not too long ago about when they switched from P-47's to P-51's in Europe, there were more than a few deaths right off the bat due to pilots trying to dive like they did in the jugs, which the Mustangs couldn't handle. I don't necessarily expect that level of AI modeling, but stuff like rookie mistakes are a welcome change IMO.

As for the acrobatic weirdness, try it against mainly veteran or above pilots, in airplanes with good roll rates. Bring the fight down the near the ground and get behind them. If they decide they want a turning fight, you should see what I mentioned. There will be lots and lots of hard rolling, and some of that zany upside-down flying. I'll try to get a screenshot, since the track saving and replay seems to be broken as of now (4.11hotfix).

[Luno13]

It has been acknowledged that .trks no longer work. DT is unlikely to fix this. Instead, be sure to record an .ntrk. Set a key, or press ESC and click "start recording" or similar.

[Whacker]

Well that stinks... What's the difference between a .trk and .ntrk? So you have to decide when a mission starts if you want to record it or not? Seems kinda silly.

[IceFire]

Originally Posted by Whacker

Well that stinks... What's the difference between a .trk and .ntrk? So you have to decide when a mission starts if you want to record it or not? Seems kinda silly.

TRK was setup to record the inputs from the player (and AI) into the flight model. It's an extremely unreliable format as slight or minor changes to the flight model and AI modeling over the years has made saving anything in TRK a near useless endeavor. The NTRK format is a very different beast in that it records more information including the actual positions of aircraft and damage states so that the playback is virtually identical between versions no matter how much has changed.

It's why the BlackDeath.ntrk or the Kamikazi02.ntrk still work many years after they were created.

I know what you mean about deciding to record later... and perhaps there is a solution using NTRK that would be possible but TRK was always problematic. As soon as IL-2 went from version 1.0 to 1.01 things started to go astray.