[Dragon]

That third issue reported by Androgeos makes me hope I will run into it when haveing Infyrnos loaded.  
In fact, I did. When playing ToT demo Seraphims approached from a huge distance and when they reached station they were flying like that. Direct hit and one hit kill.  

[Fury]

I know, that's why I created a Turreted class which keeps the settings of the retail Captain class, in order to preserve balance

When you open a ship to ship editor in fred, AI classes in turrets do nothing at all. Flags that affect turrets do so through pilot AI. This means that you cannot have different AI classes for pilot and turrets on same ship, turrets will use pilot AI regardless of what you set in fred. So whether you actually specify ship AI class in ships.tbl or change pilot AI in fred, the end result is same.

Hopefully this would be corrected to 3.6.14, probably too late for 3.6.12.

[Dragon]

Hopefully this would be corrected to 3.6.14, probably too late for 3.6.12.

What with 3.6.13?
Is it that complicated, or maybe you'd just like to skip the unlucky number in the numeration?  

[FUBAR-BDHR]

Even numbers = release builds.  So there will be no 3.6.11 or 3.6.13 etc. 

[Dragon]

So 3.6.11 and 3.6.13 will have only Nightlies?
I thought there was a 3.6.9 final, but it most likely was just latest, most stable 3.6.9 nightly.

[The E]

Errm, no. 3.6.9 was as official a release as it gets.

However, the numbering scheme was changed recently, so from now on, dev releases will have an uneven number, stable releases an even one.

[Fury]

Link in the first post updated once again. Sorry for quick update, but I think afterburner issue needed to be addressed ASAP.

Turns out that $Afterburner Use Factor is not really flexible. It only accepts integers where values are 1 = 100%, 2 = 50%, 3 = 33.33% and so on. So there's a huge drop between values 1 and 2. I fixed this by editing values across the board to 1, which makes the AI to use afterburners as often as they can, within their own logic. Hopefully Sushi can address this problem and give us the missing range between 100% and 50%.

Another more minor change is that there is higher chance of AI firing a missile at player especially at lower difficulties.

[MatthTheGeek]

When you open a ship to ship editor in fred, AI classes in turrets do nothing at all. Flags that affect turrets do so through pilot AI. This means that you cannot have different AI classes for pilot and turrets on same ship, turrets will use pilot AI regardless of what you set in fred. So whether you actually specify ship AI class in ships.tbl or change pilot AI in fred, the end result is same.

Hopefully this would be corrected to 3.6.14, probably too late for 3.6.12.

Are you sure of that ? It may be a placebo effect, but I'm pretty sure that my bombers have their turrets firing at retail rate, much slower than if they used the same improved AI than the pilots. But I might be mistaken though.

[Fury]

Yep, tested it today and results were same by Wanderer.

[MatthTheGeek]

Alright thanks, that will make implementation of new AI even quicker with my modified versions, cause I now just have to modify the default class of all turreted ships (excepted bombers) to Turreted and that's all.

And with further testing, I must say that the most noticeable part of customized AI is really the standardized turn rates. Believe me when I say that you don't want to fight a wing of Dragon with a General AI in Hard

[Fury]

I would like to ask people to test this attached ai.tbl (this is based on v4). Compare this ai.tbl to the one in ai_v4.zip and tell me which one has better dogfights and why. Thanks in advance.

Edit: Obsolete attachment removed

[Fury]

Umm, anyone? (excluding QuantumDelta)

[Macfie]

It seems the AI is less agressive than in the version 4.  I liked the version 4 better because it seemed your wingman were more proactive in what they did.

[Fury]

Thanks, that's what QuantumDelta said too. So I guess that's how it is.

[Fury]

If someone still has any interest into AI testing, here's some work for you. Open ai.tbl in ai_v4.zip
Find

Code: [Select]

$Stalemate Distance Threshold: 300, 300, 300, 300, 300
Replace all six lines with

Code: [Select]

$Stalemate Distance Threshold: 150, 150, 150, 150, 150

Once you've played and tested above values, please try these

Code: [Select]

$Stalemate Distance Threshold: 100, 100, 100, 100, 100

I'd appreciate if you would tell me what values you found best for typical FS2 dogfights. Thank you very much.

[Fury]

Link to v5 in the first post in this topic. This will quite likely be the last release unless I receive notable feedback or Sushi fixes/adds more AI stuff.

This release contains minor tweaks mostly, making very easy and easy difficulties easier and moving YES/NO flags to ai_profiles.tbl.

[Commander Zane]

This is the AI used on the WiH trailer right? I'm trying out Into The Lion's Den on Medium and there is some slightly higher aggression here and there but I still see a lot of "clueless" Shivans.

And Apocalypse was utter bomb-rape, I lol'd.

[General Battuta]

You need a recent nightly for it to work. You'll also need to set the AI profile in the mission in FRED. You'll also want to check the AI classes assigned to the ships.

I just tried it out on WiH m07 and holy crap it makes a difference.

[Commander Zane]

Unless the Antipode#4 build doesn't count, and aren't the three missions in this .zip already altered to use the AI?

[General Battuta]

Dunno, haven't tried 'em!