Since installing the latest Beta, I get the attached error message in the WestPac BS when loading scenarios 4.0 and above. Although the message states that the program will terminate, clearing the error repeatedly (anywhere between 3 and 9 times so far) will finally allow the scenario to be played normally.

 

Buddha

Since installing the latest Beta, I get the attached error message in the WestPac BS when loading scenarios 4.0 and above. Although the message states that the program will terminate, clearing the error repeatedly (anywhere between 3 and 9 times so far) will finally allow the scenario to be played normally.

 

Buddha

 

Seems to be an error loading the db...

 

The Installation 53048 looks ok...

Since installing the latest Beta, I get the attached error message in the WestPac BS when loading scenarios 4.0 and above. Although the message states that the program will terminate, clearing the error repeatedly (anywhere between 3 and 9 times so far) will finally allow the scenario to be played normally.

 

Buddha

 

In your screenshot you have the HCDA database loaded, not HCDB. I just checked the zip file and it had HCDB in it so you probably just need to swap in the right database, http://harpgamer.com/harpforum/index.php?a...mp;showfile=235

 

I did include the wrong MEDC 2003 Battleset and will remedy that in the next build.

Hmm, I think my source was misguided and the correct MEDC2003 is in the download.

Since installing the latest Beta, I get the attached error message in the WestPac BS when loading scenarios 4.0 and above. Although the message states that the program will terminate, clearing the error repeatedly (anywhere between 3 and 9 times so far) will finally allow the scenario to be played normally.

 

Buddha

 

In your screenshot you have the HCDA database loaded, not HCDB. I just checked the zip file and it had HCDB in it so you probably just need to swap in the right database, http://harpgamer.com/harpforum/index.php?a...mp;showfile=235

 

I did include the wrong MEDC 2003 Battleset and will remedy that in the next build.

 

Tony,

 

That seems to have solved that problem, thanx. I don't know how I got the wrong DB in there, but with all the switching I do sometimes, it's not a surprise.

 

One thing, though. I previously created a Caribbean Sea scenario using a BS I made with the BS Builder. When I load that scenario now, Elgin AFB lists itself as being in Baghdad instead of the Southern US. It's still in the same place, and the A/C are still the same, only the name has changed. Also, the HCDB seems to have no US Facilities in the Caribbean region. Is it safe to assume that maintainig separate commondb.res files in separate folders and swapping them as needed will be OK?

 

Buddha

Tony,

 

That seems to have solved that problem, thanx. I don't know how I got the wrong DB in there, but with all the switching I do sometimes, it's not a surprise.

 

One thing, though. I previously created a Caribbean Sea scenario using a BS I made with the BS Builder. When I load that scenario now, Elgin AFB lists itself as being in Baghdad instead of the Southern US. It's still in the same place, and the A/C are still the same, only the name has changed. Also, the HCDB seems to have no US Facilities in the Caribbean region. Is it safe to assume that maintainig separate commondb.res files in separate folders and swapping them as needed will be OK?

 

Buddha

 

Your method of swapping should be fine. You do have an alternative in recent builds, when you create that custom battleset you can now embed the database in the hdsu.res and hdsu.rsr files. In the BS Builder you'll see a new tab that mentions database (so there are map, BS description, scenario, and database tabs these days). Embedding the database simplifies things greatly, especially when releasing to the general public as they don't have to match scenarios to battlesets and databases to battlesets, everything is included in those two files, hdsu.res and .rsr.

 

I've found myself making a folder for each custom battleset I make. I store the .HCBS file, scenarios (including orders), and database files used in the folder so that I can quickly re-build the battleset if I want to update the embedded DB or scenarios.

Tony,

 

That seems to have solved that problem, thanx. I don't know how I got the wrong DB in there, but with all the switching I do sometimes, it's not a surprise.

 

One thing, though. I previously created a Caribbean Sea scenario using a BS I made with the BS Builder. When I load that scenario now, Elgin AFB lists itself as being in Baghdad instead of the Southern US. It's still in the same place, and the A/C are still the same, only the name has changed. Also, the HCDB seems to have no US Facilities in the Caribbean region. Is it safe to assume that maintainig separate commondb.res files in separate folders and swapping them as needed will be OK?

 

Buddha

 

Your method of swapping should be fine. You do have an alternative in recent builds, when you create that custom battleset you can now embed the database in the hdsu.res and hdsu.rsr files. In the BS Builder you'll see a new tab that mentions database (so there are map, BS description, scenario, and database tabs these days). Embedding the database simplifies things greatly, especially when releasing to the general public as they don't have to match scenarios to battlesets and databases to battlesets, everything is included in those two files, hdsu.res and .rsr.

 

I've found myself making a folder for each custom battleset I make. I store the .HCBS file, scenarios (including orders), and database files used in the folder so that I can quickly re-build the battleset if I want to update the embedded DB or scenarios.

 

I haven't really dug into the new BS Builder yet, so I hadn't noticed the tab you mention until I checked it out just now. I did DL the Falkland Islands series of scenarios, and I notice the method you mention of including all the relavent files in one folder was used there. The author obviously took your advice, as switching is about as easy as I could have hoped for. Given the ease of confusing the .res and .rsr files between BSs, I think I'll go with that approach as well. It'll also help on the off chance I ever design anything worth sharing. So far, I've confined my designs to simple scenarios I can use to test the Beta releases and report my findings without getting to big and complex in the process.

 

BTW, my hard copy of the game with Don's signature on the manual arrived the other day, in case anyone here is tracking such things. I already contacted Don to let him know I'd received it.

 

Buddha

BTW, my hard copy of the game with Don's signature on the manual arrived the other day, in case anyone here is tracking such things.

 

:( :(

 

looks like the mail turtle was sunk on the way over the Atlantic...