R3
R3 copied to clipboard
alexcroox
Add tracking of mortar/artillery fire?
Our operations often include some form of enemy mortar fire, so it'd be really useful if we could track the mortar fire that was taken akin to how the RPG launches are currently tracked. (with a toggle for instances where the fire is too heavy to track unit movements, like the map waypoints system currently)
The RPGs are easy as there is an EH dedicated for it, there isn't for mortars. However I have done some early work in the refactor branch for tracking grenade and smoke throws, and I'll be sure experiment with tracking artillery. Again slightly more complex since we need to track their movement over time unlike thrown items where we only care about the explosion.
Realistically, we would love to be able to track every round/shell/grenade/etc that's fired/thrown from start to end, so that we can track how effective fire was and if there were issues with contact reaction which is why we put in this ticket. However I'm guessing that is too intensive
On Sun, 26 Mar 2017, 23:00 Alex Crooks, [email protected] wrote:
The RPGs are easy as there is an EH dedicated for it, there isn't for mortars. However I have done some early work in the refactor branch for tracking grenade and smoke throws, and I'll be sure experiment with tracking artillery. Again slightly more complex since we need to track their movement over time unlike thrown items which we only care about the explosion.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/alexcroox/R3/issues/20#issuecomment-289314490, or mute the thread https://github.com/notifications/unsubscribe-auth/AARy8k8YfXV7GvtMIyd1rexB2YXbJtXtks5rptCagaJpZM4MpSb3 .
It's been discussed in the past and while it's too intensive in its current format, when I'm finished with this big rewrite I do want to revisit it. Ive got a few ideas for better ways to group up the fired data to send, finding a balance between server performance and playback size.
What about using a module to configure the addon? Have defaults that work for most cases and allow enabling of more intensive options.
