Skip to content
View in the app

A better way to browse. Learn more.

HarpGamer

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Defect Tracking

Repository of user created Defect, Bug, Issue, Feature reports for HC.

Background: This forum encapsulates perhaps the most thorough documentation of sub-optimal performance of HC. Most of the reports demonstrate excellent form and presentation to make addressing defects as easy as possible, use them as a template. The term Defect is used since not everything is a bug; some items are bugs, some are design limitations, some voice a dissenting viewpoint, defect is the term chosen to cover all of the ground.

 

Tags: Add the following tags to new issue reports,

OP: Username, UNFILED, VerRep: 2017.011

Replace "Username" with your forum username and 2017.011 with the version of the game in which you see the issue.

 

Hints: A test scenario is better than a saved game. A tiny test scenario targeted at the problem helps track down the issue. The fewer the units in the scenario, the easier to debug as well.

  1. After adjusting ASROC drop distances of torps to target we looked at the distance actually dropped and the torps position immediately after drop. We observed the torpedo was always dropped directly on the sub or 0nm away and also the torps were instantly at the depth of the sub. This was regardless of level of detection or lock on the sub. This gave the sub no warning of a drop on them by ASROC and no time to react or any sensor check might be too long for a detection. I was thinking perhaps a adjustment on flight time might increase the drop distance to the sub a bit and If needed adjustment to torpedoes acquiring depth instantly on drop. Helicopter …

  2. 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

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

  4. super slueth TonyD has found a number of older scenarios don't open in GE 2023.006, but can be opened in the current SE, saved with no changes, and they run. I've attached a zipped scenario that shows this defect. GE.log included, runs BS Medc2003, DB HCDB 150621. Don ge_OldScenWontOpen.zip

  5. GE crashes with out any warning. This has happened several time in about the same spot in the game. I have included the last 5 game saves 1 second apart. If more saved games are needed please let me know. The zip file includes GE log, db and saved games. let me know if you need any additional information. GE Crash 2023.006.zip

  6. After leaving TonyD and I alone for 15 minutes we found an issue with the 2023.003 version of the SE. When selection weapons on a plane at an air base the SE Crashes. When selecting Sensor on a ship or a sub the SE crashes. Crashes verified by TD and myself with various db's and scenarios. Included in the Zip file is a small scenario, latest db and the SE log file. 2023.003 SE Crash.zip

  7. This occurred in GE 2022.016 but repeated (different scenario) GE 2022.20 Error isn't reproduced in saved game from 1 and 4 seconds prior. GE.LOG file attached in zip, line 689,553 (game time 109392) shows: 109392 Combat5.c:1580 - G AMA:AirAttacker: ZZr.. AirTargetType = (a symbol not copied) 109392 Combat5.c:1602 - G ZZr:target_type = 1, range=4, bearing=88 109392 Combat5.c:1704 - after case, gflag=0, wrange=143, WR.weapon_range=143, attack type (type_aa)=0 Note the attacker is an F16 loaded with pavewave bomb 4 m range. (maybe a help, maybe a herring?) Scenario and two saved games from -1 and -4 seconds included. played in custom battle set …

  8. playing the Heart 3 scenario (2022 attack on Taiwan) at some 4 hours of gameplay this adjunted error (See files): taiwna 222222.hpq

  9. Upon loading a saved game using the 2023.001 GE scenario crashed. Starting a new game with scenario and db loaded fine. Opened scenario in the SE without any issues. Attached is a saved game, GE log file, latest db. If you need anything else please let me know! 2023.001 Update Saved Game Load Crash.zip

  10. 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…

  11. uses GE 2023.002, included in zip: custom battleset southPacificIslands, hccw140314 db, GE.log screen shot saved game 1 sec before popup. game played on after ignoring error type-aa-invalid-ge.zip

  12. When ever I use the F10 message (reminder) generator the game crashes.

  13. In seemingly any game after setting radar to intermittent using F9 button, at game save game crashes

  14. Hello Everytime I try to add an helo to a destroyer or a non-CV ship I get this message: 3 days ago everything worked fine but I had a corrupt file at some point when using the PE editor. So I've been uninstalling and reinstalling for 3 times now and since then I always get this message. Any help would be really appreciated.

  15. Since we can now capture bases, I changed the size of the runway on Sinuiju North Korea (ID 52621)from small to large. The base size in the SE and GE do not change size. In the PE the base size is Large. Attached is a scenario with the North Korean base, the latest copy of my db If you have any questions please let me know. Sinuiju North Korea.zip

  16. When using the autotest batch files against 2022.021 and 2022.022 Release builds, I'm getting assertions thrown in Stubs.c line 351, GetPtrSize. Even if I ignore the assertion, the GE exits soon afterward without warning. Instead of an exitcode of 0 (clean termination of the GE), I see an exitcode of -1073741819. I thought this might only be when using the AutoTest batch files where multiple copies of the GE are running simultaneously so I ran just EC2003 MEDC in single-file (one scenario at a time, one copy of GE running at a time) and still see the exitcode of -1073741819 for 50% of the scenarios (8 clean exits, 8 errors) so far. Error scenarios: EC…

  17. If you wish to start a new Battleset inbuilt scenario and go to the appropriate menu then the description of the scenario should include only the scenario background but it also includes the Blue Orders. The screen shots are from BS giuk 2003, but it seems other BS are the same. Not a critical error effecting play so low priority.

  18. When attacking a ship with guns the number of rounds the GE selects to destroy a target is much larger than what is really required to sink target. Attached is a test scenario based on my fictional db. Issue verified by TonyE TonyE Note: AttackDoctrineWithRisk uses the AllocateRounds logic which is meant for missiles (which can be shot down), not for guns. Guns Test.scq

  19. Attached is a simple scenario for westpac BS HCDB2 DB that was used to produce the screen shots, one from scenario editor, one from game. Looking at the weapon LS-6 in the appropriate loadouts for the JH-7B aircraft in Scenario editor it is listed as surf (attack) while in game it is listed as land (attack) and won't attack sea targets. This makes it possible for the scenario writer to send out patrols that are not appropriately loaded for the intended target. MSBS-Loadout.zip

  20. It appears that the air patrol crashing is back. I have had 2 ASW patrols crash, and I am unable to delete air patrols in my TG's Attached is a save game with the air patrols that were not able to be deleted in TG AEC Air Patrols Crashing.zip

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.