donaldseadog

View File Indonesia-Malayasia Conflict 1 Requires Harpoon Classic version 2022.027 (matrix patch) or later, Westpac BattleSet and HCCW 140314 database. (Photo circa 1965 HMAS Melbourne, Vendetta and Voyager) The Indonesia - Malaysia confrontation was an armed conflict from 1963 to 1966 that stemmed from Indonesia's opposition to the creation of the state of Malaysia from the Federation of Malaya. After Indonesian president Sukarno was deposed in 1966, the dispute ended peacefully. The creation of Malaysia was a merger of the Federation of Malaya (now Peninsular Malaysia), Singapore and the British Crown colonies of North Borneo and Sarawak (collectively known as British Borneo, now East Malaysia) in September 1963. Vital precursors to the conflict included Indonesia's policy of confrontation against Dutch New Guinea from March to August 1962 and the Indonesia-backed Brunei revolt in December 1962. Malaysia had direct military support from the United Kingdom, Australia, and New Zealand. Indonesia had indirect support from the USSR and China, thus making it an episode of the Cold War in Asia. The conflict was an undeclared war with most of the action occurring in the border area between Indonesia and East Malaysia on the island of Borneo (known as Kalimantan in Indonesia). However Indonesia also conducted lower intensity covert actions on the Malay Peninsula and in Singapore. The conflict was characterised by restrained and isolated ground combat, set within tactics of low-level brinkmanship. Combat was usually conducted by company- or platoon-sized operations on either side of the border. It has been claimed that a Central Intelligence Agency memorandum of 1962 indicated that UK Prime Minister Macmillan and US President Kennedy were increasingly alarmed by the possibility of the confrontation with Malaysia spreading, and agreed to "liquidate President Sukarno, depending on the situation and available opportunities". [extract from Wikipedia] In this alternative to history situation Sukarno has been removed by external efforts but rather than calm the situation it has inflamed it and resulted in more direct involvement of China and the USSR. Submitter donaldseadog Submitted 09/24/2025 Category WestPac  

There's quite a bit of interesting reading here especially if you follow the various links. I'm wondering if things had gone bad and the conflict escalated to include significant naval and combat air action what would it have been like? https://en.wikipedia.org/wiki/Indonesia–Malaysia_confrontation?wprov=sfla1

Good to know, it is likely something to do with my 2025.025 install which went straight over 2025.023 beta. I'll look at my BS files.

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

I've uploaded a new version for running in the last few betas (2025.015+) and the release 2025.025. This fixes a (rare) crash when playing legacy scenario and fighter type aircraft engage aircraft with their in built A2A cannon. I took the opportunity to tidy up some code relating to saving console position between sessions and increased the max number of lines in the message window to 999. Also added if you don't want the game message window but want to see messages regarding iterative game saves then there is a check box too get this. I am also wondering if it is time to do a run down of what toolbox does, my actual assumption is that mostly I'm the only person that uses it so maybe that's not needed, let me know if I'm wrong. There is a fair rundown in the settings window of operations...

From Australian ABC news service https://www.abc.net.au/news/2025-09-10/ghost-shark-underwater-drone-fleet-plan/105758720?utm_source=abc_news_web&utm_medium=content_shared&utm_campaign=abc_news_web&utm_content=link

Try the test toolbox.dll in the attached zip. Don not run an AIWindow.dll while testing. Let me know if the problem is fixed and I'll do a update version for both toolbox and AIWindow in the downloads. ToolBoxFixLegacyCannon Crsh.zip

I'm away from home (going back tomorrow) and forgot my powerpack for the computer. I just got enough done in a resaved version of erics saved game to be fairly sure it's the problem but didn't have enough battery to try some code upgrade. I suspect I foolishly assumed any storeconsumed passed info would relate to an item in the database and included no checks. The fix should be easy if thats the case. The slow bit will be remembering what I did as it shares the info with AARData for game analysis over multiple sessions of game play. I don't think the problem is in the StoreConsumed code although I didn't get time to test it in LAZGui. I suspect that the pointer passed (i think its either the consuming unit or the mount or both) is going to be nil in this case but I didn't check for that possibility.

Then I'm positive its the code in toolbox and AIWindow that collects StoreConsumed info and its not upto speed with this type of cannon. PS It's a pretty neat idea I think, what fighter pilot wants to wait for orders to save his skin 😄

I've given eric some homework on this but I'm not home and forgot my power pack and now have no operational computer. What really strikes me as strange is that the blue air group seems to attack with cannon with no orders to do so. It's current course (which I checked and is an attack course) seems to me to indicate it is intercepting one of the ac groups to the NE. You can even cancel its course and give it an out and return to the vacinity of the red group and it will open fire with cannon with no instructions. Its a bit like a vessel with aa engaging automatically.

I think this relates to the use of either toolbox or Lazgui-extn which both collect information on stores used and the seemingly automatic use of cannon by air group FuA attacking air group YdA. It's not a problem that has occurred before but then I've never seen the apparent automatic engage A2A with cannon. In the saved game YdA Attack etc this occurs at time 40:12. If before that you change the course of FuA to avaoid coming within 3 nm of YdA all is good, if you then steer FuA back on a collision course you get the crash. If you have neither toolbox nor Lazgui-extn operating there is no problem either.

From Australian ABC news service https://www.abc.net.au/news/2025-09-04/military-gift-warship-artifical-reef-illegal-dumping/105728244?utm_source=abc_news_app&utm_medium=content_shared&utm_campaign=abc_news_app&utm_content=otherp

The yanks left taking theirs and we've (Aus) never had any. It sure is a leveler if only one side has them and they get the chance to let loose. I had wondered if to be fair Taipei should have better SAM, I think there was a more advanced NIKE available then. It's to my mind a very fascinating bit of military/political history, Bay of Pigs stuff. It probably deserves a better scenario writer

Second Taiwan Strait Crisis (versionB) View File This scenario has been written to be playable in Harpoon Classic version 2022.027 (last available Matrix Patch) and is a variation of my previous version A 2nd Taiwan Strait Crisis Escalation. Play in Westpac BS using HCCW-140314 DB. On 24 and 25 August 1958 Chinese Communist (PRC) forces and Taiwanese (ROC) forces clashed in the vicinity of Dongding Island, which the Nationalist (ROC) troops controlled. The action was seen as an attempt by the communists to land on the island. This was the only naval and amphibious landing action during the crisis. ROC had begun to build military installations on the island of Kinmen (Quemoy) and the Matsu archipelago, very close to the Chinese mainland. The PRC shelled the islands of Kinmen (Quemoy) and the Matsu Islands in an attempt to take them from Taiwan, governed by the Kuomintang (KMT), and to probe the extent of American commitment to defend the Republic of China. The conflict also involved air, naval, and amphibious operations. Then U.S. secretary of state Christian Herter reportedly described it as the "first serious nuclear crisis". The USA provided military assistance in both material, especially aircraft and artillery, and a strong naval presence including naval escorts for island replenishments. The Communist Chinese government announced a unilateral ceasefire on 6 October 1958. However, on 20 October the PLA resumed artillery fire on Kinmen because a U.S. Navy warship had breached the PRC-declared 3 nautical miles exclusive zone from the coast of China that they claimed was a stipulation for their unilateral ceasefire agreement. In this scenario we play with the idea of the situation escalating, rather than subsiding. The powerful US carrier group has left and a major portion of the Taiwanese air force is in maintenance and repair. Word has it that USSR and China are getting restless SPOILER ensure you play with nuclear release enabled Submitter donaldseadog Submitted 09/02/2025 Category WestPac  

Has anyone played or written a scenario where nuke release should occur but sometimes doesn't even though it's in the scenario when viewed in the se and the game has been started with nuke release enabled. It seems random, sometimes it's triggered sometimes it seems not. It's just a feeling I have at the moment, ive been intrigued by a comment in Wikipedia re the second taiwan crisis stating that if it had escalated the usa was prepared to use nukes, so of course ive written them into some scenarios but they don't always seem to trigger. I'm currently using the last matrix patch game and scen edit 2022.027 for this scenario for widest distribution.

Taiwan Straight 2nd Crisis Escalated View File Scenario Background: On 24 and 25 August 1958 Chinese Communist (PRC) forces and Taiwanese (ROC) forces clashed in the vicinity of Dongding Island, which the Nationalist (ROC) troops controlled. The action was seen as an attempt by the communists to land on the island. This was the only naval and amphibious landing action during the crisis. ROC had begun to build military installations on the island of Kinmen (Quemoy) and the Matsu archipelago, very close to the Chinese mainland. The PRC shelled the islands of Kinmen (Quemoy) and the Matsu Islands in an attempt to take them from Taiwan, governed by the Kuomintang (KMT), and to probe the extent of American commitment to defend the Republic of China. The conflict also involved air, naval, and amphibious operations. Then U.S. secretary of state Christian Herter reportedly described it as the "first serious nuclear crisis". The USA provided military assistance in both material, especially aircraft and artillery, and a strong naval presence including naval escorts for island repleshments. The Communist Chinese government announced a unilateral ceasefire on 6 October 1958. However, on 20 October the PLA resumed artillery fire on Kinmen because a U.S. Navy warship had breached the PRC-declared 3 nautical miles exclusive zone from the coast of China that they claimed was a stipulation for their unilateral ceasefire agreement. In this scenario we play with the idea of the situation escalating, rather than subsiding. Use Database HCCW 140314 and for best play Game version 2025.023 or newer and ErrataGE.dll (download from harpgamer.com forum). Submitter donaldseadog Submitted 08/25/2025 Category WestPac  

https://www.abc.net.au/news/2025-04-08/why-new-zealand-plans-to-nearly-double-its-defence-spending/105151326?utm_source=abc_news_app&utm_medium=content_shared&utm_campaign=abc_news_app&utm_content=other

this is the final offering but while it seems OK it's definitely a use at own risk job. It's OK to leave in place if playing from the original battleset series and probably any battleset, but maybe not. Anyway it was a good exercise and brought up a bit of a behind curtains issue to be looked at so thanks. ErrataBS2.zip

From the australian ABC news service. https://www.abc.net.au/news/2025-08-05/australia-japan-navy-frigates/105613688?utm_source=abc_news_app&utm_medium=content_shared&utm_campaign=abc_news_app&utm_content=other

Good that BAKU is fine. The fix for NACV needs more fiddling and testing to provide a test so that it will only be applied to appropriate battlesets and the best idea I have isn't very rigorous and could fail (although it's not likely). Anyway I might fiddle more with it in case it is needed in the future but for the moment you need to remember to disable that DLL (move it or rename the file type) when playing other Battlesets.

That looks like the optimal fix to me Does it launch SA-N9s from SA-N9 launchers ? Well not the Badger but Baku

Oh BOy, this is a learning curve for me The attached seems to work in BS2 for the BadgerJ jammer, I kind of know why my previous didn't. The only issue at the moment until I learn a new way of determining the battleset that is loaded is that if you use it for any other battleset but NACV original it will screw up something (depending on the DB) and maybe crash the game - a minor issue NOTE: It will only work in late beta versions of the game engine including the 2025 comprehensive update. These allow use of a feature that loads the DB changes before the scenario is loaded and allows the new radar/ECM gear to operate - at least that is my theory seemingly proven here. But I've nothing better to do and have a lead so who knows, we might catch a fish yet. PS although I haven't tested it if you run this in the folder ExportDLL it should also make the changes in the SE as well as the GE, but there's not much point so run it in the ExportDLL\GE folder (you might have to create it if you haven't already. ErrataBS2.zip

I don't know why there might be some problem with red jammers, the modified BadgerJ have the same jammer as the blue, i even tried a version with 3 jammers per aircraft. It's not as easy a problem as it first appeared. I'll shift to a later export.dll version that will let us have operable radar for the IOPG badgerJ. This will mean needing to play with ideally the 2025 comprehensive update game. Then we can see if it's jammer works. It might be easier to rewrite the scenario in a 'modern' battleset with hcdb DB 😄🥴