Sonar will never turn on because Intermittent defaults will show 0 mins Active for 0% variance and then 5 min Passive for 50% variance

1. [PDb] Intermittent sensor defaults to zero (3.10).scn in GE2. Run from Side One3. Create Support mission and have all sensor settings for Int4. Assign DD Spruance to mission5. Sonar will never turn on because Intermittent defaults will show 0 mins Active for 0% variance and then 5 min Passive for 50% variance

When the command is given, it calculates the maximum possible number of weapons for a magazine and assumes that this should be the capacity of the magazine. Therefore, if a magazine consisted of two weapons record entries such as:

Torpedo1 6/12Torpedo2 6/12

the H3RE estimates that the maximum capacity of the magazine should be 24. This is wrong since the total magazine capacity of this submarine example should only be 12. A scenario designer could switch weapons around and load a combined maximum of 12 weapons into the magazine.

As well, the Magazine Weapons Records must have some empty 'space' so that a player can unload weapons that may already be loaded into the tubes.

If the weapons records were changed to:

Torpedo1 6/6Torpedo2 6/6

the current loads in the tubes would have no place to unload in order to switch to a different weapon.

The H3RE validation check is also inconsistent with the H3Editor. A Sanity Check using the H3Editor evaluates using the largest potential record in the magazine. For example, if a magazine had the following two Weapons Records:

Torpedo1 6/6Torpedo2 6/12

the H3Editor would check to see if the magazine capacity was at least 12 (and not 18).

AI will automatically calculate magazine loadout and discard weapons it considers in excess of capacity leaving a user no opportunity to either stop this process or correct his error before records are wiped

1. Load [PDb] Magazines forcibly re-set (3.10).scn in SE2. AI will automatically calculate magazine loadout and discard weapons it considers in excess of capacity3. User has no opportunity to either stop this process or correct his error before records are wiped

Missile will instantaneously dive from 60,000m to 132m for the terminal attack profile

1. Change DF-21 ASBM Weapon characteristics so that Cruise altitude is 60000m and dive rate is 6000m/s2. Load [PDb] Missile dives 60km instantaneously (3.10).scn in GameEditor3. Fire DF-21 at ship4. Track missile5. At a distance of 20nm from the ship, the missile will instantaneously dive from 60,000m to 132m for the terminal attack profile

Mission Editor not fully accessible in window mode. Even though size of Editor window can be changed, it is impossible to reach/see the bottom controls of the ME without the addition of a scroll bar (Originally reported by Josh Loughlin [a.k.a. Fulton])

Multiple use of "Re-build by Battleset" command causes scenario to balloon in size and freeze during load

1. Load NWCM1.scn into SE from PlayersDB Library collection2. Order Export of All Weapons Edits3. Order Re-build by Battleset4. Repeat Step 3 twenty times in a row5. NWCM1.scn size was .99mB will balloon to 1.83mB6. Attempt to Open re-built file (1.83mB size)7. SE will freeze

Path editor only appends in MP when it should be adding plotted path at whatever waypoint is selected

1. Plot path with 2 waypoints for unit in MP2. Select first waypoint and attempt to plot path from that point onwards by hitting F3 button3. Game adds waypoint to the end of Waypoint 2 instead of deleting Waypoint 2 and continuing plotting from Waypoint 1