Defect Tracking

Defect Name: CTD from multiple splits Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: Fortress Keflavik [GIUK] Long Description: CTD from group after trying multiple splits Sequence to reproduce: 1. Select group ABu 2. F8 and move both submarines into a new group 3. Order new group to divide, again, by moving both subs into new group 4. Order new group to divide, again, by moving both subs into new group Expected behaviour: Group should split into new group Observed behaviour: Attempt to split group results in CTD CTD_from_multiple_splits.zip

Defect Name: Lost contact Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-070524 Scenario used: Lost contact.hpq Long Description: Aircraft approaching a sub group turn back to land even when asked if the want to continue the search. Sequence to reproduce: 1. Allow torpedo attack to be resolved against ZXu. You may have to run this a few times. In most cases, the torpedoes should sink the SSGN. 2. Once Oscar is sunk, image "Lost contact 1" is shown requesting if search should continue 3. Then image "Lost contact 2" appears 4. Air group then returns to base even if there are still other subs in group ZXu Expected be…

in GE vers 2025.025 scenario 2 there are a significant number of aground ships. When looking in the Scenario Editor and comparing with 2022.027 the BS map appears to have been distorted. Screen shots below

Air groups HaA and FvA were landing on the same time on carrier group AAC. When the last plane in group HaA landed group FvA did not land. Group FvA was split off of HaA. Created a test scenario with 1 base and 1 CV and the same splitting of the air group and both groups landed correctly. Created a smaller version of the game using DonT's AI tool Box and both air groups landed. The saved game has not been edited. If more saved game files are needed please let me know. AC Not Landing.zip

I know these weapons were corrected as four years ago in the game engine because excessive accuracy (don't remember it well now). With many years of delay at last Longshot HAAWC (weapon entry #22580) reached IOC in November 2022, and my idea was to introduce it in the new scenarios after 11/2022. Previously Stand Off ASW are little employed (mostly for old Soviet/Russian SSNs) and I didn't repair on this bug. When a Stand Off ASW weapon is now employed, the torpedo (I didn't tested nuke depth bombs) drops in water TEN NM from the target, and the torpedo never can reach the submarine target. If the launching ship is less than 10 NM from the target, the torp…

I have a a re occurring crash with GE20019.001. I have narrowed it down to the second. Saved game GE 2019.001 SVG 115 crashes when opened. Saved game GE 2019.001 SVG 113 and 114 open correctly. They are 1 second apart. As long as I keep playing the scenario it keeps running. If you need me to go back several more game seconds please let me know. I have included a copy of my fictional db and saved games files 113,114, and 115 in the zip file. If you need any additional info pleas let me know. Have a great day, Eric GE20019.001 GE Crash.zip

Defect Name: Convoy will not slow down [2006] Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-070524 Scenario used: United We Sail Long Description: Convoy is ordered to stop but ignores order and returns to cruise speed Sequence to reproduce: 1. Order convoy to full stop. 2. Run at 1 min compression 3. Convoy re-starts movement at cruise speed Expected behaviour: Convoy should stop and remained motionless. Observed behaviour: Convoy re-starts on its own accord. Convoy_will_not_slow_down__2006_.zip

Defect Name: SE Count bug [2005] Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-070524 Scenario used: SE_Count [EC2003 MEDC] test scenario Long Description: Test scenario has ViCond set at the destruction of two bases. Victory is granted after just one base is destroyed. Sequence to reproduce: 1. Play as Blue. 2. Launch bombers and kill one enemy base. 3. Victory awarded. 4. Test scen attached. Expected behaviour: Victory after destroying two bases. Observed behaviour: Victory awarded after destroying just one base. SE_Counting_bug__2005_.zip

GE 2021.010, Test save game zip attached, using westpac battleset and hcdb 150929 database At point of start 3 fa 18 detect two helo and a ship. Total victory is to destroy a ship, min victory is to destroy a helo. If you first sink the ship then down the helo you only get min victory, I would expect you'd get both min and total victory as both conditions are met. If you down the helo then sink the ship you get your minimum vic (when helo is downed) and total when ship is sunk, as I'd expect. PS in the same scenario but with no minimum victory set you get total victory when you sink the ship so that is good. victest.zip

as game goes past midnight the date remains the same, I'd expect it to go to the next date as midnight passes. atttached scenario for westpac battleset, hddb database. testdate.zip

Defect Name: Specific Class not possible in ViConds Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: Specific Class not possible in ViConds.scm Long Description: Unable to select the Class category for any type of Victory Condition. Consequently, scenario designers are no longer able to specify individual bases for ViConds. Sequence to reproduce: 1. Attempt to modify/add ViCond to scenario 2. No combination of selections will allow the user to specify destruction of Keflavik [only] as a ViCond Expected behaviour: ViConds should allow for more specific conditions Observed behaviour: Individual bases can no l…

Hey Tony While helping Eric on a issue I became aware of an issue. We find out that a 0kts problem Eric was having occur in version 2021.014 but was not occurring with his test scenario with my computer which was only at 2021.012. He down his version and it fixed the problem for him. I decided to update to 2021.014 but got the attach popups. I tried to do this with the latest 2022 version with same effect. I then tried to go back to 2018 version to start reloading up to the latest version but the same popups occurred. It seems to indicate my winharp.exe is now out dated. I changed nothing an use the process of updates to the latest version of 2021.…

Defect Name: Aircraft Grouping Not Logical Build: 2007.000 (Aug 12 2007 Release) Repeatable: Y Operating System: XP Database: I have no idea - the standard thing that goes with HDSC 10.0 Scenario: grouping_problem.zip Long Description: I'm used (HC 2002) to the fact that aircraft flying in one group are in a tight formation that causes them to appear as one icon both on Group Map and Unit Map. In HCE it seems to be different. In the attached scenario, I have launched an attack group comprised of two SEAD A-6s, one SEAD F-18 and two F-14s for AA cover. Unforutnately, HCE for some reason decided that the SEAD aircraft should fly some considerable distance in front …

With 2 ship task group I launched 6 AC in a group. After Splitting AC only the first plane lands from Air Group ABA after game is saved and then restarted. I launched 3 plane from each ship in 1 group. Split Plane group so that planes would land on the correct ship. Landing Test 5-Landing plane 1 is where I saved the game. After that group ABA wouldn't land anymore planes. Included in my file is the test scenario, several saved games and a copy of my db. This issue appears to be similar to the issue we had with base patrols becoming corrupt after saving a game. Thanks to DonT's tool box you are able to save the planes in the group that haven't la…

Greetings All, Have two questions about software performance. Not sure if problems, or not. First, when I export the database (build 2024.001) I get the following screen. My scenario(s) seem to work okay, but not sure if "the system cannot find the file specified" is an issue. Second, in the scenario editor, my unit screen is tiny even though I have clicked the 1x setting. I ran the window resize tool available here and reset the windows in the game engine but the scenario editor unit window remains super small. The unit window shows up in the upper left of the group window. Any ideas? Geo

Text in the Message Log and the Unit banner very light text are hard to read. The text is very light.

Carribean Basin BS, HCDA database, 2023.007 GE Assertion error popup, game proceeded normally after ignore button. Zipped: game save about 1 sec before occurrence, but not duplicated on replay. and GE.log enemy ship ZYS is detected and cobra helo of base AAB is selected to intercept aa-typebad.zip

Defect Name: SAMs not firing Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-070524 Scenario used: User Test: SAMs not firing.SCe Long Description: Able to fly Backfire strike right into a CVBG with no SAM fire encountered. Vikings with Sidewinders do fire along with AAA from ships, but SAMs will not fire until the Backfire launch first. ECM is not present and is thus not a factor. Sequence to reproduce: 1. Start SAMs not firing.hpe 2. Notice that Backfires are well within the SAM range ring and inside the formation without being engaged. 3. Formation air patrols and AAA will fire if the Backfire get close enough. Therefore, the AI kn…

Defect Name: Crash in Select Battleset/main menu. Build: Aug 12 2007 (Release) Repeatable: Y Operating System: XP DB used: N/A Scenario used: NA Long Description: I somewhat stupidly and accidentally (yes, everyone belive that ) changed the size of the "Region" menu button thing. It crashed the program. I did it again and it crashed a 2nd time. A weird, possibly not fixable defect, but a defect none-the-less. Sequence to reproduce: Open game. Move the size of "Region" so it no longer shows. Game might freeze. Expected behaviour: No crash? Observed behaviour: Crashes http://img.photobucket.com/albums/v369/dav...ieWAU/crash.jpg

The FireGuns function can result in units being freed from memory. In 2025.016, StoreConsumed is called after FireGuns so in situations where FireGuns shoots down all planes in a unit, StoreConsumed cannot report what unit the guns were being fired at. A fix would be to move the StoreConsumed calls into FireGuns instead of right after FireGuns. This is a different pattern than for other weapon types but would give a more useful result.