Map depths in 3.9.4 are different from depths in previous versions (Originally reported by Freek Schepers)
1. Load [PDb] Map depths arbitrarily changed (3.9.4).scn in GE or SE 3.9.3 2. Depth at the marked refpoint2 is in excess of -100m 3. Load [PDb] Map depths arbitrarily changed (3.9.4).scn in GE or SE 3.9.4 4. Depth at the marked refpoint2 is only -10m
Ship will attempt to re-load each of its torpedo mounts. Re-load operation will never finish. Mount never becomes ready to fire
1. Load [PDb] Mount re-load never finishes (3.9.4).scn in GE 2. Order AOE to sail at cruise (15kts) speed to RefPt AOE 3. Select DD Deyo and order it to intercept and conduct UnRep from AOE 4. When UnRep begins, order 18 Mk46 Neartip and 12 Mk50 Barracuda to transfer to DD 5. After UnRep ends, DD will attempt to load 1 Mk50 Barracuda into each of its torpedo mounts 6. Re-load operation will never finish. Mount never becomes ready to fire.
On Station ViCond fails to trigger when ships arrive within designated polygon
1. Run [PDb] On Station ViCond fails (3.9.4).scn in GE 2. Arrival of UK TF in polygon fails to trigger ViCond 3. If TF starts within polygon, ViCond triggers successfully
B014 will launch ALCM and then circle until running low on fuel before RTB
1. Run [PDb] Plane does not immediately RTB (3.9.3).scn in SE 2. B014 will launch ALCM and then circle until running low on fuel before RTB. B015 launches and correctly returns to base immediately.
Plane will launch on patrol and return to base but never become ready, again
1. Run [PDb] Plane never becomes ready (3.9.4).scn in SE from Neutral side with show all ON at 1:30 min compression 2. Run test file for full duration of scenario then use Edit Aircraft function to examine UK base 3. UK Canberra will launch on patrol and return to base but never become ready, again.
Plane will launch on Recon mission, be unable to plot a path to RefPts, circle for awhile, and then RTB with 9hrs endurance remaining (Originally reported by Freek Schepers)
1. Run [PDb] Plane RTB with plenty of fuel (3.9.4).scn in SE with Show All ON from Argentine side at 1:30 min compression 2. After 90 mins, Chilean PR. 9 Canberra will launch on Recon mission, be unable to plot a path to RefPts, circle for awhile, and then RTB with 9hrs endurance remaining
Planes cannot accept mission even though they are not intended for immediate launch
1. Run [PDb] Planes cannot accept mission (3.9.4).scn in GE 2. When runway status is reduced to Medium, create a support mission with 2 day delay and attempt to assign aircraft to it 3. "Cannot launch from Available Runways" error message is received.
Two CAP fighters concentrate fire on a single target when there are two eligible targets. Each fighter should be engaging a separate target.
1. Run [PDb] Poor AAW missile allocation (3.9.3).scn in GE 2. Watch as the CAP fires on the incoming bombers 3. After initial missiles are launched, pause the game and see that one of the Ching-Kuo has been engaged by a single missile from each of the two fighters. 4. This is bad behaviour. With two bombers and two fighters, each fighter should only be engaging one enemy unit instead of both fighters engaging the same unit especially since the Phantom radar is only capable of engaging a single target at a time.
Ready time changed when aircraft are assigned to a mission
1. Run [PDb] Ready time cancelled by mission (3.9.4).scn in GE 2. Create area AAW Patrol mission 3. Assign 2 aircraft of the six present that are currently on 15 min ready time 4. Assigned aircraft will now show 30 min ready time and not 15 min
Violation of RoE yields message saying that it was a Good Guess instead of a message saying that the player will come before a Board of Inquiry
1. Run [PDb] RoE error yields wrong message (3.9.4).scn 2. Open fire on nearest unit 3. Resign game 4. Evaluation gives [PDb] RoE error yields wrong message 1 (3.9.4).gif 5. Side that was attacked was Neutral to player side an player side was Neutral towards it 6. Evaluation should display [PDb] RoE error yields wrong message 2 (3.9.4).gif informing player that a Board of Inquiry will be held
SARH/Semi-active sensor detects invisible aircraft that is undetectable under all other instances
1. Run [PDb] SARH detects invisible aircraft (3.9.4) in GE from NATO side at 1:1 2. An aircraft specifically designed to be invisible is detected after awhile. The message says it is due to Radar, Semi-Active, or SARH. This aircraft is invisible to radar in all other instances.
Sonar range circle appears for group where none should be seen
1. Load [PDb] Sonar range circle appears for group (3.9.4).scn in GE 2. Select group and plot path anywhere 3. Group displays sonar circle [PDb] Sonar range circle appears for group 1 (3.9.4).gif 4. Actual sonar coverage is [PDb] Sonar range circle appears for group 2 (3.9.4).gif 5. No sonar range circle should appear for the group, at all
Helos will launch, lay sonobuoys and then hover when out of buoys instead of RTB for more buoys
1. Run [PDb] Sonobuoy helos fail to RTB (3.9.4).scn in GE with Auto-formation patrol enabled 2. Plot long path for convoy north 3. Helos will launch, lay sonobuoys and then hover when out of buoys instead of RTB for more buoys 4. Convoy sails over buoys 5. In H3, helos would launch, lay buoys, exhaust them, and return for reload right away after displaying a "Out of relevant ammo; returning to base" message; thus buoys always appeared in front of the convoy to screen them
Sub is ordered to rise to the surface and run at 10kts, but only makes 5kts when it reaches the surface
1. Run [PDB] Sub ignores speed order (3.9.4).scn in GE 2. Sub is ordered to rise to the surface and run at 10kts 3. Sub comes to the surface, but only runs at 5kts