Prev: [GZG] PD systems, was Re: Monster ships Next: Re: [GZG] FT Vector: Alternative Fire Resolution Distance (Tom B)

Re: [GZG] FT Vector: Alternative Fire Resolution Distance (Tom B)

From: Tom B <kaladorn@g...>
Date: Fri, 15 Jan 2010 16:27:24 -0500
Subject: Re: [GZG] FT Vector: Alternative Fire Resolution Distance (Tom B)

For Hugh and Martin:

The rationalization as the endpoint of the turn as a resolution point
for fire with the claim it represents the longer continous process of
fire is interesting. It has problems. In Martin's model, it's just
'where you happen to choose to resolve discretely the continous fire
actually occuring. In Hugh's, similarly, but with the assumption you
are firing into the next turn (effectively).

This breaks down when:

1) At one point of this or the next turn (depending on your
assumptions) you were out of range or arc. In this sort of situation,
your fire should be less effective for a round if it really is
continous fire.

2) You die. That particularly affects Hugh's assumption because if you
blow up during a fire resolution after firing, and the assumption is
you were firing half way into next turn, some of your damage output
for the round was too great because you are no longer there to
complete the firing!

I have worked myself around to seeing that having multiple
contributing points during the term whose aggregate determines your
fire for that turn would be better. However, Details, meet Mr. Devil.
Mr. Devil, meet Details.

John T:

The problem won't be figuring out where you are at the midpoint, but
where you are pointed. As you say, FT makes instantaneous rotations.
One could get around this by assuming thrust is not turn long, but if
you're going to assume turn long fire, assuming short thrust bursts
seems somehow unbalanced. So yes, mid-turn bearing is a bit of a bear.
And realistically, rotation probably should be very much faster than
turn length, and that includes corkscrewing or rolling as well.

--------

Maybe the only real solution to this problem overall is going with
small time/distance assumptions that allow thrust and fire to be
discrete items (thrust and rotation still should not be, but with
small enough chunks of time, there's a sense that this issue isn't
large).

Or go buy Attack Vector, as Bob says.

Tom B
_______________________________________________
Gzg-l mailing list
Gzg-l@mail.csua.berkeley.edu
http://mail.csua.berkeley.edu:8080/mailman/listinfo/gzg-l


Prev: [GZG] PD systems, was Re: Monster ships Next: Re: [GZG] FT Vector: Alternative Fire Resolution Distance (Tom B)