Spring RTS Engine

Played with myself one pre-spring afternoon, and found to my dismay that JCai.dll (yes.. Jcai.. D:) dosen't seem to work with final frontier, infact the act of shooting the command cruiser crashes the global ai, as seen in above picture. (Yes my gpu dosen't support fragment programs (wtf))

JTAI, or JCAI? I have never heard of JTAI. If, however you mean JCAI, it does not support the FF mod. It only supports XTA. You should use one of the other AI's to play with FF, most of them work with all the mods.

We really need an AI page with infomation on compatibility, versions, warnings and links for the various AIs

We have a wiki page, but nobody bothers updating it.

I would update it, but i dont know enough about the AI's. Ill make a new thread asking for information about AI's, so someone (probably me) can add it to the wiki.

i added a little bit of information about aai a few weeks ago...

i dont know about the other ais but aai lists all compatible mods in its readme

i've added a ton of info here, why not update it and put in blank sections where that need to be fillin like

TODO:: describe how x works

TODO:: list compatable mods

check out my section wiki is easy to use not excuse not to use it.

http://taspring.clan-sy.com/wiki/Greenai

submarine wrote:i added a little bit of information about aai a few weeks ago...

i dont know about the other ais but aai lists all compatible mods in its readme

you do realize that your ai crashes for instance at FF or Xect v Mynn, dont you ? (at the very start(frame 0))

doesnt it support them or did i forget to configure something ?

Are those versions of Xect/Mynn and FF that where the latest versions at the time of the last AAI release? Or versions released sicne then? If so I suggest submarine put version numbers next to those mod names.

view aai_faq:

Q: AAI crashes right at the beginning running mod y

A: Some mods like FinalFrontier crash AAI for some reason. It could also be possible that one of the learning
files has been corrupted, try to remove the files in the learn and/or cache subfolder

and the readme says:

By default, AAI has cfg files to support the following mods:
- XTA 0.66
- TA:WD 5b4
- AA 1.42
- OTA Shiny 5.5
- OTA Classic 5.5
- KuroTA 0.47
- Star Wars 1.0
- TLL 1.04

So all other mods either crash the game due to their structure or you will have to set up a config file first

submarine wrote:view aai_faq:

Q: AAI crashes right at the beginning running mod y

A: Some mods like FinalFrontier crash AAI for some reason. It could also be possible that one of the learning
files has been corrupted, try to remove the files in the learn and/or cache subfolder

and the readme says:

By default, AAI has cfg files to support the following mods:
- XTA 0.66
- TA:WD 5b4
- AA 1.42
- OTA Shiny 5.5
- OTA Classic 5.5
- KuroTA 0.47
- Star Wars 1.0
- TLL 1.04

So all other mods either crash the game due to their structure or you will have to set up a config file first

ok ok.. sorry i was posting it has a known fact for me that it didnt ran ff or so but then i had a second thought about configures , sorry about it.
(I had already read the FAQ somewhere in the past ..lol -> my memory is crap)

Oddly enough, once I updated AAI to the newest two versions, it stopped working with TLL 1.04 even after I nuked the contents of the learn folder

Not really a big issue though, just saying

EDIT: only posted this to see if it's just me, o do other people have problems running TLL and AAI.

ok good to know, i only tried tll 4-5 times...

sorry, i found the bug:

open the tllv104.cfg and look for the following line:
AMOBILE_ARTY_RANGE 1000.0

change it to
MOBILE_ARTY_RANGE 1000.0

i must have been not carefully enough when updating the cfg files for the last release; if an error occurs reading a mod cfg-file, aai uses default config (which crashes tll)

sorry, my fault - after changing that, tll works fine for me again

thanks man

I think I found the same thing in the AAspring135 cfg files which is why I could never get them running, but now they work (even though I'm still using an old AA vrsion).

ai log should look like this:
Note that i forgot to update the version string so even with aaai 0.42 it says aai v.035

What we should have is the messagebox tell us:
- The team number of the AI that caused the exception.
- What function was being called.

That would make much less headaches for all of us AI developers and the AI users, making it easier to determine what it was that went wrong.

I've looked over the AICallback.cpp file and it should be easy to add that information.

Veylon wrote:What we should have is the messagebox tell us:
- The team number of the AI that caused the exception.
- What function was being called.

That would make much less headaches for all of us AI developers and the AI users, making it easier to determine what it was that went wrong.

I've looked over the AICallback.cpp file and it should be easy to add that information.

thats also why it is advised to run spring in debug when testing , so that you can see that however if is an ai user playing and it crashes to him it'd be nice to be able to see that info from him

How do you do that? Do you uncheck the "Catch AI Exceptions" option? And if so, how do you get the function out of the dump log?

When you're in a skirmish ffa with 4/5 ai's running all from different people and it crashes, the message is totally ambiguous. At least show an aidll name rather than just ai.dll