Skip to content
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

[Feature Request] Sortie time statistics #81

Open
ha15224 opened this issue Jul 11, 2024 · 7 comments
Open

[Feature Request] Sortie time statistics #81

ha15224 opened this issue Jul 11, 2024 · 7 comments

Comments

@ha15224
Copy link

ha15224 commented Jul 11, 2024

Adding sortie time statistics such as average sortie time, battle duration for each node, and etc would be helpful in optimizing compositions that would benefit from faster runs, such as leveling or ranking.

Gathering the time data for each animation (shelling, aaci, carrier attacks, ....) would be a painstaking job, but I am willing to cooperate if necessary.

@X-20A
Copy link

X-20A commented Jul 11, 2024

Besides the sheer volume of work, other concerns would include.

  • Will the addition of this functionality delay the original simulation process?
  • Won't that clutter up the code writing?

Honestly, I can't think of a concrete solution for this.

@ha15224
Copy link
Author

ha15224 commented Jul 11, 2024

Frankly I have no knowledge of how the internal computation/ source code works within the simulator, but wouldn't an option a user can tick to include the time measurements within the simulator settings be an easy fix?

@X-20A
Copy link

X-20A commented Jul 11, 2024

It would be easy to prepare a flag and switch.
However, a description of the time measurement is required for every operation (either to be added sequentially or to be logged and calculated together).

@ha15224
Copy link
Author

ha15224 commented Jul 11, 2024

That would be necessary as I can imagine. That being said, I do think the order of computational complexity shouldn't change (e.g. less than double the current speed as it is only doing an additional sum for every existing operation) with this feature. Of course, only users who wish to obtain these statistics would have reason to wait the extra dozen seconds.

@X-20A
Copy link

X-20A commented Jul 11, 2024

As for latency, there is no other way but to measure it in the end. In fact, it could be that it is hardly a problem.
However, it is inevitable that the code will become more complex

@fourinone41
Copy link
Contributor

It's an interesting idea, but yeah my main concern is the amount of work, not just to start but to maintain (e.g. still need update if devs add something niche like atoll node attacks, Momochi anti-install animation), not sure if that's something I'm willing to maintain for now.

Won't that clutter up the code writing?

My idea is to turn on API generation which is used for Watch a Replay, use that to calculate time (as animations are directly tied to API), all separate from sim code. But yes that would increase sim time and would need a flag.

Of course also can't handle variables such as network latency, asset loading/caching, player's speed clicking yasen button, etc.

@ha15224
Copy link
Author

ha15224 commented Jul 11, 2024

I would greatly appreciate it if you were to entertain the possibility. Thank you for your attention and feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants