95
edits
Talk:Scripted AI Objects: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(→missile.nas feedback: new section) |
No edit summary |
||
| Line 163: | Line 163: | ||
* how to proceed from here depends on who's willing to collaborate - otherwise, I may simply rewrite large portions of it, which would obviously take longer than providing feedback on what to change... | * how to proceed from here depends on who's willing to collaborate - otherwise, I may simply rewrite large portions of it, which would obviously take longer than providing feedback on what to change... | ||
--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 23:20, 4 November 2014 (UTC) | --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 23:20, 4 November 2014 (UTC) | ||
------ | |||
I'll have a look this week end and will try to work of some points of the roadmap. I think the whole things goes in the right direction.The point here from what I can see is to follow the roadmap. Perhaps (as we all have complex schedule) we could splitt more the work in tiny little task that we can do in 1 hour... | |||
If following the roadmap we could come up with : | |||
1)Creating the ai object (done) | |||
2)display it (done) | |||
3)Creating the initial position of this objec, depending of the "source"/launcher paramters (this involve trigonometric calculation if I remember right... | |||
4) Also we have for the "missile/bomb/lanched drone case" think how manage the pylon positioning issue. (Do we put it in the source object ?) | |||
5)Detection:this is a big part : the ideal would be to have the "radar" object that we discussed once Hooray. This object could do Infrared detection, radar detection, could make the target disapeared if there "terrain" etc... and then if there is detection, it should provide command to the FDM (wanted pitch, wanted Roll, wanted heading). But Perhaps just a radar object could not be enough for al ai object (like tanker, drones, terrain following missiles etc).I don't really know how to do this but the idea would be to have both a kind of autopilot & a radar ... | |||
(Anyways the autopilot should also include the tanker behaviour : with base returning, virage ?, dialogs ?) | |||
And also we have to make a prevision script : just following a target isn't enough for the detection part. Some of missile should predict the next position(s) of the target and anicipate, in order to be more precise. This is important when a aircraft come from the front. a "simple following detection" will make the missile avoid the target. | |||
We also let the code open enough to include tomorrow a "flares sensibility" (MP player would love that) | |||
6)Then comes the fdm. This should be the tough part. I don't see how make this generic. Cause we have : terrain following (simplified), sea level following, aim54 High altitude cruise missile, other cruise missile/ai (drone and tankers), vectoring thurst missile (wich become less agile with no fuel), breaked bomb (with parachute), and simple missile | |||
7) the proximity detection & detonate the "missile" | |||
If we subdivise it perhpas we could go forward. Anyways...perhaps I can not have a suffisant big mind or stand back to make something generic enough...So do not hesitate to show me the way :D | |||
As I said earlier, I will look this this week end. | |||
—[[User:5H1N0B1|5H1N0B1]] ([[User_talk:5H1N0B1|Talk]] | [[Special:Contributions/5H1N0B1|contribs]]) 10:40, 05 November 2014 (UTC) | |||