Talk:Scripted AI Objects: Difference between revisions

Jump to navigation Jump to search

Talk:Scripted AI Objects (view source)

Revision as of 19:23, 9 November 2014

2,169 bytes removed ,  9 November 2014
m
→‎Article renaming/focus: done
m (→‎Generalization of different fuses: Fixing broken diff link)
Line 128: Line 128:
Another thing : About bombable. I tried to install it once on missile.nas : I discoverd that the bombable variable is already implemented since fox2.nas, and after testing I rememeber shooting bombable C172 invation with missiles... So if bombable still use the same system it could be easy to keep the fox2 orignal implementation. I never tested it with bombable and multiplayer...
Another thing : About bombable. I tried to install it once on missile.nas : I discoverd that the bombable variable is already implemented since fox2.nas, and after testing I rememeber shooting bombable C172 invation with missiles... So if bombable still use the same system it could be easy to keep the fox2 orignal implementation. I never tested it with bombable and multiplayer...
—[[User:5H1N0B1|5H1N0B1]] ([[User_talk:5H1N0B1|Talk]] | [[Special:Contributions/5H1N0B1|contribs]]) 14:46, 31 October 2014 (UTC)
—[[User:5H1N0B1|5H1N0B1]] ([[User_talk:5H1N0B1|Talk]] | [[Special:Contributions/5H1N0B1|contribs]]) 14:46, 31 October 2014 (UTC)
== Article renaming/focus ==
: @5H1N0B1: About point e: I think that unguided munitions should be simulated as [[Howto:Add_submodels|submodels]], but unguided weapons (such as the {{Wikipedia|GBU-24_Paveway_III|GBU-24}}) can be simulated using this new system.  Because of this, I think that this project should be renamed "AI guided weapons," or something like that.
: [[User:Red_Leader|Red Leader]] ([[User_talk:Red_Leader|Talk]] | [[Special:Contributions/Red_Leader|contribs]]) 17:38, 31 October 2014 (UTC)
:: I don't mind this project/article being renamed - it originally started out with the missile code obviously - and that's what the original contributors were interested in, which is why I chose this name. The question is if we have enough manpower to make this sufficiently generic. I am not concerned about being too broad/generic - in fact, like I said already, it would make sense to not make things highly combat-specific: Under the hood, we first of all need an API for scriptable AI objects. The next iteration would be about script-able airborne objects, from which missiles/bombs might be inherited. In general, it helps to keep different use-cases in mind, i.e. to broaden the pool of potential contributors, which also includes UAV folks, and those not interested in combat. For these reasons, I would probably favor "Scripted AI Objects" over "AI guided weapons". The point to bring across here is that functionality will be mostly scripted - the AI system may be used internally, but most of it remains unused/disabled. Also, the odds of getting this reviewed and committed are much better if it's not too specific to a highly-narrow niche that has no application outside a controversial area like combat support in FG. I would very much like to see this developed further - but without being specific to a single aircraft/missile or weapons system - I am primarily interested in the framework side of this, i.e. refactoring, improving code reuse and so on, and would love to see non-combat efforts also being able to use the same modules (which seems doable).--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 19:34, 31 October 2014 (UTC)


== Modified tanker.nas version using ai.nas ==
== Modified tanker.nas version using ai.nas ==
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/77716"

Navigation menu