experiments with AI

[ant0N]

it came to artificial intelligence! Two days of trying to create a simple and extensible AI and I think I did it!
I will post in this thread my progress.

this is only the beginning.

[SolarPortal]

nice one antON It seems you have got the navmesh under control.
I am looking forward to seeing where this leads.

the dofile looks like it is going to have a problem if you pass it to another user as it is hard coded.
i will have a look into this now and get back to you as i am sure there is a way of making it relative.

[ant0N]

Thank you!
Yes, dofile() I could not get it to work otherwise..

[StarFire]

Cool mini matrix!, looking forward to seeing this develop. Keep up the great work

[SolarPortal]

[Shando]

Hi ant0N,

Looks like we are working on the same thing

I've just (almost) finished some AI Behaviours ( Seek, Flee, Evade, Pursue, Arrive & Follow ), which I'm testing and tweaking. My version does NOT use any of the NavMesh, but solely relies on Vectors etc. (based on the famous work by Craig Reynolds and the AI in another engine). Though I'm sure adding in the NavMesh wouldn't be too tricky

I'll pm you my script as it is now so you can take a look ( it's not commented, so might be a bit tricky to understand in places ).

One question....... Does the "doFile" work in the same way as "requires"? From what I've read, doFile runs the entire called file in one go, and requires includes the called file (similar to C++), which allows you to call individual functions from it.

Keep up the great work!!!

Shando

[TattieBoJangle]

[SolarPortal]

its good to see everyone working together and looking forward to that AI shando.

require is like loadFile where it loads the script, but none of it is executed and running in the state. This means you have to pcall to the loaded lua and execute it manually. This doesn't work in skyline as they files need to be running in the actual "Lua_State". This method is used when you need to change or add extra arguments to a lua script which does not need done inside skyline.
Basically, these methods are not used at all unless you execute the scripts manually which is not possible as skyline is running the lua states immediately when play the game is pressed.

This is where doFile() comes in, since you are playing the game and the script you are wanting to load has the functions you need. It needs to be running inside the "Lua_State" the same as the script it is called into in order to access variables or functions.

Another way of thinking of this is; that it just adds the contents of the lua script you are including into the script you need to reference, so the functions/variables are directly accessible.

The new "sky.include()" is a c++ implementation of the dofile() and dostring() approach, where you only need to pass a single filename and it will be located between editor, game and player.

In our function for the end game, we get the contents of the lua script from the loaded resources from an archive as a string from a stream and use the dostring() function instead of dofile() which is used in the editor and player. This has created compatibility right across skyline. So in the next version of skyline, this is the function you will want to use instead of dofile, loadfile, require etc...

[SolarPortal]

[ant0N]

it is planned in the next release?

[SolarPortal]

the "sky.include()" function which replaces dofile() has been added, tested and will be in the next release, yes

[Shando]

[SolarPortal]

yes, each one has its own copy as each entity has its own "Lua_State". The code brought in must exist within the state in order to be called.

Lua files that are brought in through the include cannot have any skyline functions: e.g.
onInit(), onUpdate() as they are not called in that script. But all skyline libraries, e.g. entity, physics, vehicle etc.. can be used.