Tony or Brad:

 

Are there specific instructions on how to utilize the battleset builder program. Via trial and error I've figured out part of it but I can't get my test battleset to be read by the scenario editor. It created a HCBS file but that appears to be incorrect. I'm trying to create a Hawaii battleset with an embedded database as a test. I got the map to work under the "my battleset" and the scenario editor sees that battleset. However, the battleset I'm trying to create, "test 1" with a Hawaii map (rsr file ?) and with an embedded database. Something was saved as a HCBS file, but it is not read or accessed by the scenario editor.

 

1. When embedding data bases will any data base (res) work in a battleset?

 

2. When it asks for an rsr file does that refer to the map file you want to use?

 

3. Is the battleset program backwards compatable: ie once a battleset is created is it permanent and non-editable in the program?

 

4. I have yet to fully understand the nature of the res and rsr files. I assume the rsr is the map and graphics and the res is the database structure?

 

5. Has anyone else asked these questions?

 

Some clarification on how this is supposed to work would be helpful.

 

As always thank you,

 

Steve M

1. Only a commondb.res style database may be used. You cannot use the earlier battleset .res files (such as HDS1.RES). But yes, you can embed HCDB, or HCDA, or EuroDB, some custom DB, etc.

 

2. The rsr file is mostly used for platform photos in the current version of the BS Builder. At some future time other game graphics may be pulled from the .rsr file (victory images, staff assistant images, and such).

 

3. Once you create the hdsu.res and hdsu.rsr they are no longer editable, correct. That is where the .hcbs files come in, they store your settings in case you want to 'update' the created hdsu.res and hdsu.rsr.

 

4. Quite correct! The .res file also holds the map information and map texture graphics in addition to the platform database.

 

5. Not really, some of the testers have asked, not too much questioning past that. So thanks for asking for all of those who haven't asked but want to know.

 

BS Builder explained...

Default screen - "Battleset Map"

• Here is where the user chooses the area the battleset should cover. Right-click the spot that equates to the upper-left corner of your battleset. Then hold Shift and right-click the lower-right corned of the area that encompasses your battleset.
  
• Caveat, as of 2008.044 the output map is made as a square image, 1024 x 1024 pixels (and 2048 x 2048 for the textured map). That means your map will look scrunched if you choose a non-squarish area. Trial and error is how to find something you like. Notice that the GIUK battleset is quite square (range rings are circular) while WestPac is scrunched (range rings are more elliptical).
  
• You may also type in bounding lat/lon if you so desire. The program will yell at you on occasion when using this method but no fatal crashes will occur, it is just upset when there is an invalid number in the box.
  
• Make Battleset button - click this one when you have entered your desired settings on all of the tabs and a battleset will pop-out, consisting of two files, hdsu.res and hdsu.rsr in your HCE directory. It general takes multiple minutes to run and the program is unresponsive during this time since it isn't nicely multithreaded. There will be a pop-up message when the process is complete (and if there is an error). If there is an error you might not be able to click the X to close the program, right-click it on the task bar to close the program.
  
• Help button - gives extremely simplistic instruction on using the BS Builder.
  
• Save Settings button - When you've defined all of your settings for the battleset use this button to save those settings for later use. This is handy while constructing a multi-scenario battleset. You might have a single scenario and embedded database to distribute at first. So you save the settings. Then you make a database update and write another scenario. By opening the BS Builder and using "Load Settings" you will already have the first scenario defined, battleset information defined, etc. So you'll just add the new scenario on the "Battleset Scenarios" tab and make sure you are pointing to the updated database on the "Battleset Database" tab. Then save your new settings and hit the "Make Battleset" button to crank out your updated battleset.
  
• Load Settings button - See Save Settings button...
  

 

Battleset Text

• Battleset Name - The name as it is shown in the battleset listing (i.e. Indian Ocean exploratory battleset)
  
• Region - this short snippet shows as the right-hand column in the battleset listing (i.e. GIUK, MEDC, IOPG, etc.). This is purely for information display and doesn't have to be an existing value.
  
• Battleset Descriptive Text - Here is where you expound upon any over-arching story for the battleset. It is displayed in the battleset listing when this battleset is selected. It is not shown in the scenario selection area of the game.
  

 

Battleset Scenarios

• You may type in scenario long names towards the top of this tab for any scenarios you are distributing in the battleset (you don't need to include scenarios but it is commonplace to include some). Then of course point to the scenario file in the Filename entry.
  
• Caveat, the program stores the path to the file as well so if you change where the file is stored, the scenario will need to be re-added to the list.
  
• The triangular buttons are used to re-order the scenarios defined for inclusion in the battleset and the minus button is used to remove the selected scenario from the battleset definition.
  
• As the program indicates, each scenario must have Orders files. They can be created with the OrdWrite.exe program in your HCE directory.
  

 

Battleset Database

• You may include a database in your battleset but do not have to. Usually the .res file is a commondb.res file and the .rsr file is a commondb.rsr file. If you do not embed a database, the current commondb.res and commondb.rsr file active in the user's HCE directory will be used.
  
• Caveat, the program stores the path to the file as well as the file name, so if you move the commondb.res and .rsr files for your battleset, when you re-load the settings (battleset definition aka .hcbs file), you will have to re-visit this tab and check your settings.
  

 

So the quick recap is the BS Builder can do as little as create a new map for you to play with. Beyond that you can add a non-generic description, scenarios, and even a database. In that ultimate configuration you need only distribute the hdsu.res and hdsu.rsr files for someone to play your battleset. This removes the burden of matching map to scenarios to database from the player at the expense of distributing larger files than just a scenario file and orders.

One note on what Tony just said. For those of you unfortunate to have Windows Vista, as I do, while the BS Builder is actually building the Battleset, it will display the "Not Responding" alert we're all too familiar with. Unlike other programs where this Vista alert means the software has stopped working and died, in the case of the BS Builder it is normal and only needs to be waited out.

 

Buddha