20,741
edits
Talk:Scripted AI Objects: Difference between revisions
Jump to navigation
Jump to search
m
→Modified tanker.nas version using ai.nas
| Line 143: | Line 143: | ||
Like I said, before you told me you were interested in exploring this, I already started some work related to this - I'd suggest you wait until I have committed those changes so that you can take a look - it's mainly structural stuff ensuring that the existing GUI dialog can be used to instantiate a new tanker using ai.nas - everything else is "as is" and still needs to be adapted, but I thought this could help lower the barrier to entry. It's up to you obviously to decide if you want to use or discard those changes. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 17:19, 2 November 2014 (UTC) | Like I said, before you told me you were interested in exploring this, I already started some work related to this - I'd suggest you wait until I have committed those changes so that you can take a look - it's mainly structural stuff ensuring that the existing GUI dialog can be used to instantiate a new tanker using ai.nas - everything else is "as is" and still needs to be adapted, but I thought this could help lower the barrier to entry. It's up to you obviously to decide if you want to use or discard those changes. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 17:19, 2 November 2014 (UTC) | ||
Ok, I've committed those additions[https://gitorious.org/fg/hoorays-fgdata/commit/c61effba1a8e0f80b4acf5c48de8c19d94218fbc] - it isn't yet using ai.nas though, it's just a slightly modified version of tanker.nas that is loaded into a different namespace, and integrated via the tanker.xml GUI dialog, so that the actual file doesn't need to be modified. We can now easily replace existing functionality without there being any chance to break anything. Even though reset/re-init handling may still need some work/tweaking, because I haven't reviewed tanker.nas for any hard-coded namespace references yet.--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 18:14, 2 November 2014 (UTC) | Ok, I've committed those additions[https://gitorious.org/fg/hoorays-fgdata/commit/c61effba1a8e0f80b4acf5c48de8c19d94218fbc] - it isn't yet using ai.nas though, it's just a slightly modified version of tanker.nas that is loaded into a different namespace, and integrated via the tanker.xml GUI dialog, so that the actual file doesn't need to be modified. We can now easily replace existing functionality without there being any chance to break anything. Even though reset/re-init handling may still need some work/tweaking, because I haven't reviewed tanker.nas for any hard-coded namespace references yet.--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 18:14, 2 November 2014 (even though it might make sense to UTC) | ||
I've looked at the Tanker class in tanker.nas and it would seem pretty straightforward to use your ai.Obj class there, so depending on you getting git/gitorious access shortly, I can also prototype the whole thing in the meantime. It would definitely be a good thing to grow a library of tests, including not just scripts for testing the missile functionality, but also ai.Obj itself - and under the hood, aircraft functionality is going to be crucial either way. Once tanker.nas is ported, we could also adapt the code to add an f14 aircraft that can actually fire the new missiles to exercise the code without relying on a particular aircraft/location setup. Thus, I'd suggest the following priorities: | |||
* review tanker.nas and port the Tanker class | |||
* review bombable.nas and other use-cases to help generalize the new ai/missile.nas modules | |||
* look at the guidance/autopilot logic and come up with corresponding base classes | |||
--[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 19:36, 2 November 2014 (UTC) | |||