1. The rulebook only mentioned the evaporative duct as being usable by ships, and yet the scenario has a helicopter using the duct to extend its radar horizon. Can aircraft use the duct? If so, where is that rule located?
2. I think I figured this out by going through errata documents, but can someone confirm that the sensor type modifier for RF FC solutions no longer exists? As I understand it, instead of a modifier, now non data-link sharing from the helicopter should only provide a "poor" solution if it is feeding data to the frigate from an active sensor, and should have no effect whatsoever on the FC solution if the frigate decides to make its own, independent, solution using passive bearing (since the sensor type modifier no longer exists)
3. Not related to the scenario, but still confusing to me. When the rules state that a helicopter launch leads to the helicopter, at the end of the movement phase, moving into the wind at 25% of its full power at low altitude, what does that mean exactly? If the helicopter needs 5 minutes to launch, was launched in the previous tac turn, and is now launched 2 minutes into the current tac turn (for a total of 5 min) does that mean the helicopter is forced to move into the wind at 25% of its full power speed until the end of the movement phase (the remaining 3 min of the phase)? Or rather, does it mean that a helicopter launch is not finished until the end of the movement phase, even if time-wise it would finish half way through it?

I hope this is the appropriate place to be asking these questions. If not, I'd appreciate being pointed in the right direction, as opposed to simply telling me I was wrong to post this here. 
Regardless, I'll appreciate any help anyone can provide.

However, the "Tattletail" scenario has an O.H. Perry with an F arc for the CAS and a P&S arc for the STIR, the complete opposite of the fleet book, not to mention a PW/SW arc for the backup OP gunfire director, whereas the fleet book lists no such arcs and assumes the director will have the same arc as the mount. 

What gives? Both of these documents are supposedly updated to August 2024

The upcoming issue is the complexity of not only the code to execute turn replay, but also the amount of data that must be stored in the way of historic movement tracks to support turn replay. The more features I add to SimPlot, the more coding that must be done and the more data that must be collected to support turn replay.

Already I have eliminated range arcs/circles from historic consideration. That means the arcs/circles will not appear and disappear during the course of replay, but rather they will stay on/off based on their last status.

I am in the process of expanding the formation editor features, but it occurs to me a formation will change its composition (units and their locations within the formation) over time. Even a change to the formation leader will cause the turn replay to not function right unless the changes are tracked by time. (Especially because all the formation bearings and distance are based on the leader.) This requires additional code and data storage (larger file sizes) to implement correctly.

I have to admit I really like the concept of a live turn replay. It was originally a response to players of multi-player games that felt disconnected by the multi-player experience (processing multiple turns between player interactions). The replay would give a player an opportunity to "catch up" with the action since the last turn. Perhaps an alternative could be offered in the way of screenshots saved into Red, Blue, and All folders based on the referee "Show Side" setting.

Movement tracks are s lightly lesser issue for coding, but they are a huge issue for file sizes. Already I have begun offering players the option to not save movement tracks in their turn files. The movement tracks do at least allow players to "turn back the clock" in case of an error during movement. That means tracking movement for at least one turn. But, I would like to know if displaying the total historic tracks during a scenario is useful to you.

Kevin

Specifically, 

A way to put an aircraft into a loitering state without waypointing the same circle 20 times as well as a way to give orders to a bunch of selected units instead of one unit at a time.

SimPlot 2.3 Beta for MacOS

• Submitter
  kmart494
• Submitted
  11/12/2021
• Category
  Application/Tools/Mods/Docs

SimPlot MapMaker for Win10

• Submitter
  kmart494
• Submitted
  10/30/2021
• Category
  Application/Tools/Mods/Docs

SimPlot MapMaker for MacOS

• Submitter
  kmart494
• Submitted
  12/11/2021
• Category
  Application/Tools/Mods/Docs

For your behind-the-scenes information, the Jumpstart scenario was run by me using SimPlot.  There were actually three scenarios executed, with each one resulting in tweaks to the rules, data annexes, or the scenario graphics.  The Guardian scenario contained therein is the third and final version.  Some changes to SimPlot were also implemented to facilitate making data changes to the scenario.  Some of these changes will find there way into the next SP update.

Larry Bond has given permission to freely copy and distribute the Jumpstart.

The H5 rules, data annexes, and Player's Handbook are awaiting final print proofing.  We are almost there!

HpnV Jumpstart 10 Jul 20.pdf

So I am reading through the rules for the first edition.  The example of play that is described is confusing me.  Maybe I'm just not getting it, or maybe there is a typo.

Is there errata anywhere for this edition?

My problem is:

9-6 is 1-1

6-9 is 1-2

It says to always round down.  Can someone explain the 6-9 becoming 1 to 2, I'm just not getting it.

I'm stuck, and this is going to bother me until I figure it out.

Thank you in advance.

-Byron

https://vassalengine.org/wiki/Module:Harpoon:_Captain's_Edition

https://rockymountainnavy.com/2022/04/14/moskva-burning-using-the-wargame-harpoon-v-from-admiraltytrilogy-com-to-assess-the-story/