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.

Herman

Banned
  • Joined

  • Last visited

Everything posted by Herman

  1. No, I am running the "Mark II" version of the scenario. The first one was judged by everyone to be faulty from conception. I am testing with the 'hand-crafted' second version built from scratch. That's why I now believe that it is a legitimate problem.
  2. Read the description for the unit/carrier Mitchel where you find those planes: It's a hypothetical platform. I don't believe that it is either a bug or an accident.
  3. I've run through this, again. I note that there seem to have been a number of changes. It's still a fun and challenging scenario. Your removal of the ECM support for NATO is significant. It really changes the 'flavour' of the scenario. I'm not saying that it is bad, but it certainly has serious impact on how the game plays. Also, unless I am mistaken, the F-16s that you have added now can carry the AMRAAM with 60nm range (I don't remember seeing that capability in the earlier version.) This makes the scen quite a bit easier for the player. When I only had 40nm AMRAAM, dueling with Flankers who had longer-ranged missiles was much riskier. I don't know if the Bear AGM strike was present in the earlier version, but it darn near caught me off guard to wipe out Jan Mayen. Too bad about the current behaviour wherby the Bears follow their missiles in and get slaughtered, though. Overall, it's still fun, but I think it might be a bit easier than it was before. I have one suggestion. The PhibRon might be a bit too far from the Striking group to be covered by them. Not a big problem, but it was quite daunting to see both groups bearing down on Iceland. I think that the strike group may have outrun the Amphibs. Thanks for making it and sharing it. Sorry that I cannot add much on how the AI makes/controls attacks.
  4. Defect Name: Ineligible target type Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: Ineligible target type.hph Long Description: When ordered to attack a surface group known to contain ships, subs, and aircraft, only subs and aircraft are offered as target types. Sequence to reproduce: 1. Order DOa to attack ZRc. 2. Only Submarine and Aircraft show up as eligible targets Expected behaviour: All three platform types should show up on selection menu Observed behaviour: Only two platform types show up on selection menu Ineligible_target_type.zip
  5. I think that I have to resurrect this report. Larry insists that he didn't use improper technique in creating this [second version of the] scenario. He says that he built it from scratch, so there should not be any hidden problems with file formats. Subs are now being detected right through an island and at extreme range. These aren't noisy subs, either. Once contact is with an Akula. Defect Name: LR sub contact Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: LR sub contact.hph Long Description: Sonar contact from Burke is at ultra-extreme range. It should also be blocked by the island of Iceland. Sequence to reproduce: 1. Burke shows sonar contact on the other side of the island Expected behaviour: Sub contacts should not be behind an island and at extreme range Observed behaviour: Sub contacts are behind an island and at extreme range Extraordinary_sonar_range.zip
  6. Defect Name: Runway too short for Harrier Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: Runway too short for Harrier.hph Long Description: Beachhead Charlie, AAp, allows some versions of the AV-8 Harrier to land on it yet prevents other Harriers. I think that all Harriers should be the same type of aircraft utilizting the same landing restrictions/requirements. Sequence to reproduce: 1. Attempt to ferry Harriers from ship group AIs to AAp Expected behaviour: All Harriers should have the same landing requirements. Observed behaviour: Harriers have different landing requirements. Runway_too_short_for_Harrier.zip
  7. As in the other thread, why should this be considered moot? Those Harpoons are not rated "land-capable" when you try to attack the base. They can only fire at the barges, not the base.
  8. Why should it be considered moot? It still uses the same game engine.
  9. Just to be clear, the player is able to fire sub-launched Harpoon missiles at the barges docked in the harbour; but not torpedoes.
  10. I saved that scenario a bit 'close to the quick'. You have to be very fast to try and launch that sub attack because the target sub disappears within 1-2 seconds of the test scen being run. Sorry. I would have given a bit more leeway had I known it might be a problem.
  11. The hotkey is 'b'. Hit 'b' and then the point where you what your missile to go active. It is similar to assigning a patrol mission.
  12. Defect Name: Phantom air group attempts landing Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: Phantom air group attempts landing.hpe Long Description: "Select Group for landing" window appears for unspecified air group. Only two air groups are airborne. Nothing happens regardless of the landing field selected. Sequence to reproduce: 1. Run until window for selecting landing field appears Expected behaviour: "Select Group for landing" window should not appear Observed behaviour: "Select Group for landing" window appears Phantom_air_group_attempts_landing.zip
  13. Defect Name: Barges in harbour cannot be torpedoed Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: Barges in harbour cannot be torpedoed.hpe Long Description: Barges grouped with land facilities cannot be attacked by torpedo even though the vessels are clearly in open water. Attack is possible by SLCM. Sequence to reproduce: 1. ADu cannot attack ZIp with torpedoes Expected behaviour: Ships in port should be open to attack from torpedoes Observed behaviour: Ships in port cannot be attacked with torpedoes Barges_in_harbour_cannot_be_torpedoed.zip
  14. The 289th NEW Harpoon scenario in the last 12 months! 4.0 San Carlos By the 20th of May, there were strong indications that invasion was imminent. Destroyers had shelled Argentine coastal garrisons and rumours were rampant that SAS troops were on the ground. During the night, an Argentine freighter was shelled by an unknown British warship in Falkland Sound. By daybreak, Argentinean observation posts saw the amphibious force steam into San Carlos waters. Author: Freek Schepers With over 142,000 PlayersDB scenarios downloaded in the last 12 months alone, the PlayersDB has proven itself the unequivocal players' favourite. Harpoon ANW users can get the Complete Harpoon ANW Library This scenario requires the latest release of the PlayersDB-ANW Get it via: ughHQ, GameSquad, HarpGamer, SimHQ, Matrix, SubSim, or Frugal's World of Simulation. Harpoon3.6.3 users can get the Complete Harpoon 3.6.3 Library Home of the Harpoon3 PlayersDB FilesOfScenShare
  15. The game is operating as it has always done. Check the spacing between your F-14 and your Hornet. It is 41nm. If you check the spacing between your two carriers, they are 40nm apart. You have inadvertently launched planes from both carriers into the same group. The group behaviour is working as it always did. I think that the oversight is on your part. I don't disagree that it would be a nice option for all elements within a group to move together once they launch, but I would truly hate to see this as a mandatory behaviour because there are some missions like ASW whereby you want your MPA/helos to be spread out so that they can drop a wall or line of overlapping sonobuoys.
  16. Defect Name: Damage display corrupted [2006] Build: Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: Damage display corrupted [2006].hpi Long Description: After base is damaged by missiles, the Unit display is corrupted. Sequence to reproduce: 1. Run saved game Expected behaviour: Display should not be corrupted. Observed behaviour: Display is corrupted. Damage_display_corrupted__2006_.zip
  17. 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 longer be selected for ViConds Specific_Class_not_possible_in_ViConds.zip
  18. Perhaps there should be a new category of surface combatant? The "UnDead" class? They could communicate through Jennifer Love Hewitt of the Ghost Whisperer.
  19. What am I? Chopped liver?
  20. Interesting hypothesis. Unfortunately, this ship reports 0% damage.
  21. Thanks for the suggestion, but I never do that anymore. I have done it in the past and also found them to run out of gas so I stopped doing it.
  22. Close Air Support - often rockets, napalm Battlefield Interdiction - often CBUs Single Integrated Operational Plan - Nukes
  23. Defect Name: Ghost of Scorpio Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: Saved game - Ghost of Scorpio.hpi Long Description: Scorpio ship unit ZC04 does not appear to be susceptible to attack. Two attacks were made against group ZCs with 15+ Harpoon allocated to Scorpio on both occasions. No hits and now the player is unable to select the ship group for attack. This scenario was played before and I *think* that I was able to kill the ship, but I cannot be certain. Sequence to reproduce: 1. ZC04 cannot be attack. Player cannot even launch group against ZCs. 2. Note that the oddly discoloured icon for Scorpio was present before any attacks occurred. Expected behaviour: Player should be able to attack Scorpio Observed behaviour: Player cannot attack Scorpio Ghost_of_Scorpio.zip
  24. Defect Name: Text wrapped around Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: Text wrapped around.SCn Long Description: Text name for ships in formation editor wraps around onto next line. Sequence to reproduce: 1. Select formation ZDS and hit Formation Editor 2. Name of Tarantul wraps onto next line Expected behaviour: Names should be only on one line Observed behaviour: Names wrap around onto following lines Text_wrapped_around.zip
  25. Defect Name: Air patrol runs out of gas Build: HCE 2007.000 Repeatable: Y Operating System: XP DB used: HCDB-071223 Scenario used: Saved game - Air patrol runs out of gas.hpi Long Description: Formation air patrol AA29 runs out of gas on its own. Sequence to reproduce: 1. Run saved game for about 10min. High compression is okay. Expected behaviour: Formation air patrols should never run out of gas Observed behaviour: Formation air patrol runs out of gas. Air_patrol_runs_out_of_gas.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.