donaldseadog

Days after the announcement, Japan loosened decades-old restrictions on defence exports, in a long-anticipated change that will allow it to further ramp up arms sales, with analysts predicting some US allies — including Australia — will increasingly turn to Tokyo for key defence equipment ... https://www.abc.net.au/news/2026-04-27/us-allies-turn-to-japan-defence-supplies-as-iran-war-drags-on/106607656?utm_source=abc_news_app&utm_medium=content_shared&utm_campaign=abc_news_app&utm_content=other

https://www.abc.net.au/news/2026-04-26/netherlands-buys-bushmaster-fleet-australia-commits-to-more/106608000?utm_source=abc_news_app&utm_medium=content_shared&utm_campaign=abc_news_app&utm_content=other

********** SPOILER ALERT ************ Well we basically just followed orders, and got lucky with the very early deluge of ballistic missiles. We used our choppers sparingly to seek out any surface combatants that could hinder our advance, and found them. The lower threats were advanced on until within in accurate gunnery range, then hammered. Regular and pesky air patrols from a mainland base took a couple of our choppers before they could dash back, skimming the wave tops wasn't good enough to evade detection and then the inevitable. TotalGameTimeDuration=11Hrs34Mins GameTimeToGO=12 Hrs: 25 Mins RealTimeDuration ThisSession=1:26:40 [StoresConsumed - Blue] Blue Weapon=Tally SM-2MR Block IIIB=38 AGM-114M Hellfire II=10 RGM-84D Harpoon=4 SSM-2 (Type 90/96)=8 SSM-1 (Type 88/90)=16 RIM-162A ESSM=40 127mm/62 Mk45 HE=218 127mm/54 Compact HE=104 Squad Rifle=2 12.7mm MG burst=16 Platoon Infantry=3 [StoresConsumed - Red] Red Weapon=Tally DF-21D ASBM=10 YJ-18=16 C-803 (YJ-83)=24 AA-12 Adder A (R-77)=5 AA-11 Archer (R-73)=8 HQ-9 (FD-2000)=4 SA-N-12 Grizzly (Shtil-1)=26 QW-4=10 AS-14 Kedge (Kh-29T)=4 130mm/54 AK-130 HE=11 Thanks for this one Enrique. I have a feeling the outcome could well be different every time it's played. Luck dodging, or not, those ballistic missiles is a big determining factor. I might give it a run as the Red side and see what happens.

If at first you don't succeed, ... (try again in case your luck has improved)

https://www.abc.net.au/news/2026-04-24/us-navy-awards-contract-for-aukus-submarine-deal/106601042?utm_source=abc_news_app&utm_medium=content_shared&utm_campaign=abc_news_app&utm_content=other

Australia enters homegrown missile race — but can it really stand alone? SBS NewsAustralia enters homegrown missile race — but can it real...As Australia ramps up missile production, experts say supply chain gaps and export challenges could limit its independence.

I'm sure I still have hair on my head (although it is white) because of Tony's launcher 😻 I'm glad you're back into it and all is going well.

From australian ABC news service https://www.abc.net.au/news/2026-04-10/uk-intercepts-russian-sub-threat/106548994?utm_source=abc_news_app&utm_medium=content_shared&utm_campaign=abc_news_app&utm_content=other

I'd suggest the best way is to prepare some folders named for each database you intend to use (I use subfolder 'HCDBs' with further subfolders for each database eg HCDB2, HCCW, HCWW) then just download the files fresh from the downloads section of harpgamer. The thing is that the database files will generally all be named commondb.rsr as they were intially intended to be swapped in and out of the root HC folder. By having the individual folders and by using the custom 'launcher' programs (also in the downloads section) the complexity is negated. You can even give the database files unique file names. Otherwise you are continually having to move or rename the commondb files and easily loose track of which is which.

I'm getting quite excited. I'll hopefully give this update a run tonight. I realised I can use Toolbox to set active group and unit in the game without needing the game's group window, so I can put this one over it (on my 14" laptop screen) and give it a good workout.

The aerial drones in particular, or more to the point their loadouts, would be a demand on our database if treated individually, so that was mostly where I was thinking, and some well thought out generic platforms would be beneficial. For the type treated as weapons I'm thinking there is much more space availability in our DB annexes, maybe a few new specialised platforms and mounts and modified existing platforms but for the most part it would just be additional weapons?

With a lot of new drone and autonomous weapons it seems to me (once we get back to modernising DBs in some way) that the line between platform and weapon is becoming difficult to decide. Also there is the decision on whether to create single generic items or create a pletherer of individual. Here's what hot my thinking about it (I know infact it's not a new delema) seen in current events https://defence-blog.com/xdown-develops-stud-drone-for-squad-level-strikes/

Some back ground: I guess its an historic thing, pre 2003 all battlesets had there own in built database so it was effectively selected from within the game when you selected which battleset you were going to play, and then from there you could select scenarios. Since 2003 the option (normal arrangement for 'new' battlesets) is that the database is external and as it can't be selected once the game starts you need to know before starting the GE which database you are going to want. The databases tend to relate to time periods so that's not so bad. So most of the xxx2003 battlesets and Westpac are like that, Malacca being an exception as it has the HCDB2 database embedded in it. A scenario's required database will be listed in it's HarpGamer download page plus if you open the scenario file with a text editor and look at the first few lines of gobblygook you'll see some plain text including the database name, eg HCDB170909, that will be the database the scenario needs. (You don't need to do that if the scenario is from one of the pre 2003 legacy battlesets) Loading a scenario that requires a different database to the one loaded into the GE gives an error message similar to your "GetMemAnnexA Error" but that doesn't mean for certain that's what's happened to you, but it's what brought this to my mind. By default the GE loads the database from the commondb.res file in the main hc folder but a different database can be loaded by using a modified command line (eg by using HClauncher or SELauncher respectively for GE and SE, but also by other means more fiddly). Before HCLauncher the two common methods were to rename the database file needed as commondb.res and to swap it for the one in the root folder or to execute the GE (or SE) via a shortcut and manually write into the execute line the flag <-d ?> followed by the full pathname to the database file, Tony's GELauncher was an obvious godsend. If all was working fine for you using the last beta and you were starting GE and SE straight from the respective executable in the hc folder (or from the default game menu) then I think you must have only been playing custom scenarios for the default (HCDB) database or legacy battlesets? Don

One thought, are you trying to open a scenario that uses other than the standard database, if so then the necessary database needs to either replace the commondb database in hc root folder or be linked in the command line executing the SE (and GE). For this reason it is good to start the GE with TonyEs game launcher or the SE with my SELauncher as they allow you to search and link the database (and battlesets\scenarios etc) at launch.