virtualbow
virtualbow copied to clipboard
nock offset
I would like to see a way to specify the nock offset, rather than reducing the length of the bow and estimating the weight of the part that is left behind the nocks and the end of the bow.
which is widthheightnock-offset*rho, but specifying "2cm" is easier :-)
I'm not sure about this feature. It would be very handy, but It also seems like too much "magic" to me, for the following reasons:
- The current parameter for the tip mass is still needed, for overlays or other additions. It would then have to be explained to users that the total tip mass is the one computed from the offset + this value. But that is just a minor issue.
- It neglects the grooves for the string or any other shaping/rounding of the nock that might have been done. I just think that most nocks have so little in common with the rest of the bow limb that we shouldn't attempt to model them in a geometric way and instead let it be the user's responsibility to figure out the right mass.
- The output results would look slightly different than the bow that the user modeled, because the tip would be missing (because it doesn't have to be simulated like the rest of the limb, only its mass has to be considered. Artificially adding the limb tip to the results would be possible, but that would produce more output data just for "cosmetic" reasons.)
It's a nice idea, but in my opinion the benefit just doesn't justify the complications.