eeustice

R-360 Neptune Ukrainian SSM that sank the flag ship of the Russian Black Sea Fleet. Based on the Russian KH-35 SSM. http://www.military-today.com/missiles/neptun.htm View full record

Welcome back! Happy Harpooning!

It's awesome that a game that has been around for over 30 years can still compete with much newer games. Thanks to everyone who supports the Harpoon community!

Looks like my list is getting shorter! Thanks Tony for all of your time and effort!

Running the first version of of the GroupidManager I found when starting a new game the GE crashes. If you play a saved game the GroupidManagerworks great. I have had it up to 715 groups. 196 Blue and 519 Red in my test scenario. It looks like Tony finally broke the 676 group ID limit!

Welcome to the HARPGAMER forum. Harpoon has been around since the early 90's. I purchased my first copy on 5 1/4 inch floppy disks. It existed as a board game before that. If you have any questions please do not hesitate to ask. Over the years there have been many upgrades and enhancements to the game. There are still bug fixes and enhancements continuing to this day. The latest updates are this forum.! Enjoy and Happy Harpooning!

Test of new HC build and updated Turncoat worked! Thanks Tony!

Looking at the Group ID Export dll there are only 152 groups at this point in the game. I am unable to turn over any of the red bases. I have included the latest edition of my db Turncoat 152 Groups.zip

Looking at my current game the Blue side goes from groups AAb to HEA with several gaps. The Red side goes from ZZb to YJs with several gaps in it. I can not convert a base at this time. What is the limit of group ID's available for Turncoat to use? I would expect that any available non used group ID would be available to be used. In some of my games I have seen Red group ID's mixed in with the Blue group ID's.The GE grabs any available group ID no matter what it is. In this case I destroyed base ZVa. In the units window of Turncoat the group ID is ZV000 Jianqiao. Could that be an invalid group ID? I used the last version of Turncoat to capture a base and it assigned group ID (Aa. Is it possible that Turncoat is trying to use a group ID that is being used for an existing air group or task group?

(ZUa)When attempting to change destroyed air base (ZUa) to blue using Turncoat, receive "Side change failed, no group id available" message. Created a test scenario and was unable to duplicate the issue. Earlier in the game I converted a red base to blue base (DSa) using Turncoat. There was an update to Turncoat after base was converted to DSa due to a previous GE crash caused by Turncoat. It appears that the side in the Turncoat base resets it self back to the Red instead of the Blue side. I have restarted the GE several times and the issue persists. In my test scenario I was able to change the sides of a base to any option available with out a problem. Attached is my saved game. Update Test 1-25.zip

Verified fix. My AC no longer loiter at 0kts.

Further testing reveals that in 2021.012 the issue does not occur.

Ran test scenario and there was no crash. Issue resolved!

After launching and setting AC to patrol at high altitude, when aircraft reaches patrol location speed goes to 0kts. Attached is a saved game just before the AC reaches it patrol location as well as the scenario created for the test. GE log has been included. If you need any additional info, please let me know. 0kts Loitering.zip

In my db it is the air launched version of my Ballistic Missile killer. Max altitude is Too High (suborbital)

I ran the scenario again this evening and it appears that the crash is being caused by the lazTurncoat.dll. I can kind of understand why it happened in this scenario. The destroyed AD units were part of the original base that was destroyed and then changed sides.

Tony, looking at the whole path where I had the scenario saved the length probably is longer than 150 characters. My file path was: E:\HC Scenairos\Spratly Islands\Spratly Island #4 Files\Spartly Island 4 Part 1\Spartly Island 4 Part 1 Final Files Thanks,

Interesting! I ran the scenario yesterday from before I launched the missiles that destroyed the base and turned it to blue using Turncoat and the crash occurred just after I destroyed one of the AD units. I am wondering if you need the saved game file just before the AD unit was destroyed. All crashes occurred after the AD unit was destroyed. I just ran the scenario again. The GE crashed just after the saved game started. If the GE doesn't crash the next game second then I don't know where to go from there. Update Test 1-9.hpq

During game play shortly after missiles hitting AD units close to blue base Yelizovo, Russia GE crashed. Blue side destroyed Red base Yelizovo, Russia. Used Turncoat dll to turn base blue. Just after 25 seconds of play the GE crashed. This crash has occurred multiple times at the same time. I have included the last 3 seconds of play game time, GE Log and the latest edition of my db. Please let me know if any additional info is needed. GE2021.012 Crash.zip

Correct File has been uploaded!

When Saving a Scenario that I was editing, the message below came up several times. Scenario seems to save Ok. When reopening it appears that all changes were saved. Selecting Retry seems to save the Scenario. The zip file consists of the latest edition of my db, the SE Log file and a copy of the scenario. If you need any additional info please let me know. Saved scenario with 2021.006 and save did not produce any messages and SE did not crash. Spartly Island 4 Part 1 Update 12.zip

Fix Verified! Thanks Tony!

In 2021.006 with exactly the same DB as I used in 2021.009, there is no issue. The issue occurs even in a brand new blank scenario when I look at the platform display in the SE

I tried to load my latest version of my scenario in 2021.006 and it wouldn't load. Due to the message I received, I'm guessing that it was due to the 2021.009 update. I went back and found a recently updated scenario and China did not come up as Side. I checked multiple versions of my db and don't think that my db was causing the issue.