20,741
edits
Talk:Scripted AI Objects: Difference between revisions
Jump to navigation
Jump to search
m
→Specs and Requirements
m (→Merging the latest changes: stripped (obsolete)) |
|||
| Line 56: | Line 56: | ||
: I think what we should do first is to put down stuff that affects the missiles specs, such as guidance types, seeker type, etc., then split these into categories, such as FDM, Seeker, etc., and work from there. | : I think what we should do first is to put down stuff that affects the missiles specs, such as guidance types, seeker type, etc., then split these into categories, such as FDM, Seeker, etc., and work from there. | ||
: [[User:Red_Leader|Red Leader]] ([[User_talk:Red_Leader|Talk]] | [[Special:Contributions/Red_Leader|contribs]]) 16:52, 28 October 2014 (UTC) | : [[User:Red_Leader|Red Leader]] ([[User_talk:Red_Leader|Talk]] | [[Special:Contributions/Red_Leader|contribs]]) 16:52, 28 October 2014 (UTC) | ||
:: I've looked at the fox2.nas file and all those missile specs there are usually based on defaults provided by the aircraft-set.xml file - thus, I've extracted those portions to a separate XML file and using io.read_properties() to read in specs in an xml-configurable way. All those values will end up in a key/value map (hash), so can be easily accessed. For now, it's just a stub, but I'll probably generalize this a little more and move it to some sub-class, so that we can reuse the same mechanism for other missile. The commit can be seen at [https://gitorious.org/fg/hoorays-fgdata/commit/8f52be90eb615a29e16b9ed6b5d19f7c42ac503b].--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 13:05, 2 November 2014 (UTC) | |||
== Generalizing the existing code == | == Generalizing the existing code == | ||