I finally got one base in Pensacola to work, but that puts me right at the apparent limit of 2048.

 

The scenario still doesn't appear in the BS window (it's empty) and has to be loaded as a user scenario,

 

Cool that at least one Problem got fixed.

 

For your Scen. You need to build the BS first to get the map (it is usefull to note the used coordinates on a sheet of dead wood aka paper). Add 1 old scen to the BS, it doesn´t mater where it is located!

 

then you can build your desired Scen. Build a new BS 8with the old/same coordinates) but you now can replace the placeholder scen by your new build scen

 

Edit: I can open the BS File here without any Problems, no crashes but i´m using the Euro DB at the moment!

 

Next try is with Buddhas DB file

 

Edit II: Works fine with Buddhas commondb file except of the missing Base.....

 

Regards René

 

Rene:

 

I managed a similar workaround, although mine involved uninsatalling and reinstalling the builder. I like your way much better. As to Editting, what I would like to see is a way to open the BS in the builder and edit it there. I haven't been able to figure out a way to do that yet.

 

Also, while I did get Pensacola to work as a base, it puts me at the 2048 limit so I can only have one installation in one BS, no more. If I create any more installations in the PE and export, they do not appear as available anywhere. I'd like to delete some of the installations I never use to make room, but I'm afraid if I do, I'll crash the whole thing.

 

I sent most of this to Tony in a PM last night since I seem to be the only one having these problems, but sharing them here is probably a good idea, too.

 

Buddha

[As to Editting, what I would like to see is a way to open the BS in the builder and edit it there. I haven't been able to figure out a way to do that yet.

 

 

As far as i know the Edit fuction is missing => something Tony is working on for the future and as long as we haven´t got an edit function for the BS-Creator you can use my workaround.

 

Regards René

[As to Editting, what I would like to see is a way to open the BS in the builder and edit it there. I haven't been able to figure out a way to do that yet.

 

 

As far as i know the Edit fuction is missing => something Tony is working on for the future and as long as we haven´t got an edit function for the BS-Creator you can use my workaround.

 

Regards René

 

What I'm working on isn't an editing of a battleset but rather saving of the settings used to create a battleset. So a file will be created that has the coordinates of the battleset, text of the battleset, filenames of the scenarios. As to how much farther the capability will go, I'm not sure. I'm tempted to save also in that configuration file of sorts a copy of the scenarios and such but I'm not sure. The other approach is as you both suggest, allow editing of a battleset (which already holds all of the information of interest).

[As to Editting, what I would like to see is a way to open the BS in the builder and edit it there. I haven't been able to figure out a way to do that yet.

 

 

As far as i know the Edit fuction is missing => something Tony is working on for the future and as long as we haven´t got an edit function for the BS-Creator you can use my workaround.

 

Regards René

 

What I'm working on isn't an editing of a battleset but rather saving of the settings used to create a battleset. So a file will be created that has the coordinates of the battleset, text of the battleset, filenames of the scenarios. As to how much farther the capability will go, I'm not sure. I'm tempted to save also in that configuration file of sorts a copy of the scenarios and such but I'm not sure. The other approach is as you both suggest, allow editing of a battleset (which already holds all of the information of interest).

 

Tony:

 

Now that I seem to have everything up and running normally, I have another question or two. If I create more than one battleset (South Pacific in addition to my Caribbean for example), are they designated sequentially as in HDSM.RES, HDSN.RES, HDSO.RES, etc. or will they all need to be saved in separate folders as HDSM and swapped in and out of the Harpoon folder? Also, I recall a blank DB file available for download someplace that you could import data into, such as the data in Rene's Baltic DB, but I've lost the URL for it somehow. Anyone remember where that's located?

 

Thanx:

 

Buddha

Now that I seem to have everything up and running normally, I have another question or two. If I create more than one battleset (South Pacific in addition to my Caribbean for example), are they designated sequentially as in HDSM.RES, HDSN.RES, HDSO.RES, etc. or will they all need to be saved in separate folders as HDSM and swapped in and out of the Harpoon folder? Also, I recall a blank DB file available for download someplace that you could import data into, such as the data in Rene's Baltic DB, but I've lost the URL for it somehow. Anyone remember where that's located?

 

Thanx:

 

Buddha

 

At this time there is only hdsm.res and so must be swapped. This will change but we don't have it planned out yet.

 

Any time you import a DB into the editor, it overwrites any data already in the pfData file, so just make a copy of pfData for each DB you use, no need for the blank DB (which is in the downloads section at HarpGamer here) unless you are starting a DB from scratch.

Now that I seem to have everything up and running normally, I have another question or two. If I create more than one battleset (South Pacific in addition to my Caribbean for example), are they designated sequentially as in HDSM.RES, HDSN.RES, HDSO.RES, etc. or will they all need to be saved in separate folders as HDSM and swapped in and out of the Harpoon folder? Also, I recall a blank DB file available for download someplace that you could import data into, such as the data in Rene's Baltic DB, but I've lost the URL for it somehow. Anyone remember where that's located?

 

Thanx:

 

Buddha

 

At this time there is only hdsm.res and so must be swapped. This will change but we don't have it planned out yet.

 

Any time you import a DB into the editor, it overwrites any data already in the pfData file, so just make a copy of pfData for each DB you use, no need for the blank DB (which is in the downloads section at HarpGamer here) unless you are starting a DB from scratch.

 

How does this affect the pfBuild file. Does that need to be duplicated as well?

How does this affect the pfBuild file. Does that need to be duplicated as well?

 

Nope, you only need the one pfBuild file.

Any time you import a DB into the editor, it overwrites any data already in the pfData file, so just make a copy of pfData for each DB you use,

 

A little suggestion.

 

I´ve renamed those files to pfdatahceurope.mdb, pfdatahcatlantic, pfdatahcdb

 

so you can keep all those fles in 1 folder without messing them up.

 

All you need is to browse to the right file.

Befor I write up the following procedures and post them to the WIKI, I wanted to run them past you guys and make sure I'm correct.

 

To play another member's BS and associated scenarios, do the following:

 

Rename your HDSM.RES and HDSM.RSR files, if they exist, to preserve them.

 

Copy the member's HDSM.RES and HDSM.rsr files to your Harpoon directory.

 

In the PE, link to the PFData file containing the member's platforms and export.

 

To reverse the above and return to your own BS, if you have created one:

 

Delete or rename the member's HDSM.RES and HDSM.RSR and rename your old ones appropriately.

 

Link to your old PFData file and export.

 

Is this Correct?

 

Buddha

Befor I write up the following procedures and post them to the WIKI, I wanted to run them past you guys and make sure I'm correct.

 

To play another member's BS and associated scenarios, do the following:

 

Rename your HDSM.RES and HDSM.RSR files, if they exist, to preserve them.

 

Copy the member's HDSM.RES and HDSM.rsr files to your Harpoon directory.

 

In the PE, link to the PFData file containing the member's platforms and export.

 

To reverse the above and return to your own BS, if you have created one:

 

Delete or rename the member's HDSM.RES and HDSM.RSR and rename your old ones appropriately.

 

Link to your old PFData file and export.

 

Is this Correct?

 

Buddha

 

You don't need to use the PE at all in most cases, just make sure you have the appropriate commondb.res and commmondb.rsr files in place. For most people the PE just means more things to go wrong. Feel free to put it in the wiki but it isn't the final form so you'll be doing a lot of changing if you start now (in other words I'd say a lot of things are more deserving of wiki entries than an early beta battleset creator that will not work this way upon release).

 

Otherwise it appears you have the procedure correct.

Befor I write up the following procedures and post them to the WIKI, I wanted to run them past you guys and make sure I'm correct.

 

To play another member's BS and associated scenarios, do the following:

 

Rename your HDSM.RES and HDSM.RSR files, if they exist, to preserve them.

 

Copy the member's HDSM.RES and HDSM.rsr files to your Harpoon directory.

 

In the PE, link to the PFData file containing the member's platforms and export.

 

To reverse the above and return to your own BS, if you have created one:

 

Delete or rename the member's HDSM.RES and HDSM.RSR and rename your old ones appropriately.

 

Link to your old PFData file and export.

 

Is this Correct?

 

Buddha

 

You don't need to use the PE at all in most cases, just make sure you have the appropriate commondb.res and commmondb.rsr files in place. For most people the PE just means more things to go wrong. Feel free to put it in the wiki but it isn't the final form so you'll be doing a lot of changing if you start now (in other words I'd say a lot of things are more deserving of wiki entries than an early beta battleset creator that will not work this way upon release).

 

Otherwise it appears you have the procedure correct.

 

Point taken. It appears posting something now might cause more confusion than it solves. The reason I mention the PE is that in my own case some of my scenarios contain platforms I've created, and if others have the same, the platforms won't be available without the export. Of course if no homemade platforms are involved, this step isn't necessary.

 

Buddha

Also, while I did get Pensacola to work as a base, it puts me at the 2048 limit so I can only have one installation in one BS, no more. If I create any more installations in the PE and export, they do not appear as available anywhere. I'd like to delete some of the installations I never use to make room, but I'm afraid if I do, I'll crash the whole thing.

 

Buddha, I think everyone forgot to elaborate on what to do for now about the 2048 limit, sorry about that. The mantra "always add, never delete" has the important connotation that you can modify existing entries. In making your own database if you don't need to guarantee compatibility with existing scenarios, you can modify installations you don't ever plan to use into ones you do plan to use. A Bejing airfield for instance may have no use in a Caribbean battleset so you could rename your Bejing installation and change any characteristics about it for use as say, Hugo Chavez Military Field #1.

 

Does that help explain?

Also, while I did get Pensacola to work as a base, it puts me at the 2048 limit so I can only have one installation in one BS, no more. If I create any more installations in the PE and export, they do not appear as available anywhere. I'd like to delete some of the installations I never use to make room, but I'm afraid if I do, I'll crash the whole thing.

 

Buddha, I think everyone forgot to elaborate on what to do for now about the 2048 limit, sorry about that. The mantra "always add, never delete" has the important connotation that you can modify existing entries. In making your own database if you don't need to guarantee compatibility with existing scenarios, you can modify installations you don't ever plan to use into ones you do plan to use. A Bejing airfield for instance may have no use in a Caribbean battleset so you could rename your Bejing installation and change any characteristics about it for use as say, Hugo Chavez Military Field #1.

 

Does that help explain?

 

That's basically what I wound up doing, although in my case it was an antenna site in Iceland. I figured since the ID#'s weren't messed with, I could edit description, side, location, etc. without hosing things up. So far everything seems OK.

 

Buddha

Since my system upgrade and reinstallation of all things Harpoon, I've noticed a minor problem. I recreated the Caribbean BS and saved it without any difficulty. I then used the SE to create a small Caribbean ASUW scenario, opened the BS in the BS Creator, and added it as a BS scenario. Then I ran the end edit routine. When I load Harpoon, the Caribbean BS loads OK, but the scenario doesn't appear in the window as available. It does load and play just fine as a user scenario, so playability is not diminished. I just can't figure out why it's not showing up in the BS window as a BS scenario.

 

What did I miss here?

 

BTW, thanx to Tony for his help in getting everything up and running again, especially the PE.

 

Buddha

Since my system upgrade and reinstallation of all things Harpoon, I've noticed a minor problem. I recreated the Caribbean BS and saved it without any difficulty. I then used the SE to create a small Caribbean ASUW scenario, opened the BS in the BS Creator, and added it as a BS scenario. Then I ran the end edit routine. When I load Harpoon, the Caribbean BS loads OK, but the scenario doesn't appear in the window as available. It does load and play just fine as a user scenario, so playability is not diminished. I just can't figure out why it's not showing up in the BS window as a BS scenario.

 

What did I miss here?

 

BTW, thanx to Tony for his help in getting everything up and running again, especially the PE.

 

Buddha

 

The most recent version of the BS Creator does decent logging about adding scenarios, please post up your log. It should be in he same directory as the BSBuilder.exe and is called BSBuilder.log. Current version of the BSBuilder is 2007.024. As an unrelated request, do you get any error messages when loading saved settings in the BS Builder? Not getting it here, but Rene is and would like more detail on recreating the problem.