-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple targets #28
Comments
Agreed on health point tracking. We could also easily move towards using the target to control its own motion. Multiple target spawning has a bit more complex dynamics to think through, but certainly an interesting option. We should discuss this a bit more in the development plan |
I now consider this issue to be largely addressed (though some small issues remain). I'll answer the questions from the original issue in order below:
The affiliated configuration changes (mostly moving from target parameters to arrays of target parameters) has been completed. Open items include:
|
Since we've implemented arbitrary target models I've added support for logging target model names as of a recent commit. This is part of the changes affiliated with logging outlined above. |
A recent commit moves towards using trial indexes together with session ids, and with target ids/indexes to make each target's name fully unique. I will consider this part done for now. Similarly Once we complete testing on the impacts of removing at hit and large target counts we can probably close this issue unless additional info needs to be added to the logs. |
Tested system performance using our latency tool the impact of target clear and multiple targets.
|
Thanks to @joohwankimNV for confirming performance. I believe all the core issues here are now addressed. Let's close this issue here and open new issues for any specific additional items we might need. |
It seemed easy at first, but soon I realized it requires changes across many parts. We should the decisions on them based on a high level philosophy, and then implement it. As a starting point of discussion here are the local changes needed.
The text was updated successfully, but these errors were encountered: