2. Battleset by filename isn't working (at least in the hdsu.res case though I wonder if that is the only case that doesn't work)

 

It was wrong of me to show a battleset by filename option in the launcher, I just re-read the release notes and they don't list a battleset by filename option. I had wanted to make it possible but it was requiring too many changes for too little gain. It is disabled in the next version of the launcher.

Get the updated launcher at http://harpgamer.com/harpforum/index.php?s...ost&p=15003

 

I tried older versions of the GE and couldn't find one that worked properly with a single -l followed by multiple arguments so I changed the launcher to use one -l per log argument and that seems to work just fine.

 

Oh, also note that you can copy the command lines shown by the launcher in this new version (and ostensibly paste them into your report)

Launcher does not work. When I hit launch GE, nothing happens.

 

Also, typing in the text it provides as the command line keeps giving me the error that 'winharp32.exe' is not a recognizable executable or batch command...etc.

 

In other words, I have yet to get the launcher or using command lines to work.

Is more workload in the databases, but very good the news about the air to air guns.

In other words, I have yet to get the launcher or using command lines to work.

 

Are you sure the launcher is in your HCE directory?

In other words, I have yet to get the launcher or using command lines to work.

 

Are you sure the launcher is in your HCE directory?

 

Yes, I unzipped it to my main HCE folder. When I hit the 'Launch GE' button on the launcher, absolutely nothing happens.

In other words, I have yet to get the launcher or using command lines to work.

 

Are you sure the launcher is in your HCE directory?

 

Yes, I unzipped it to my main HCE folder. When I hit the 'Launch GE' button on the launcher, absolutely nothing happens.

Well things happen here too fast for me, but I'll post up my fiiles from testing the older launcher, I had some issues with scenario by name (perhpas that option shouldn't be in?). I'll try the new launcher.

Ive attached some log file portions with my notes included within each file as a header.

generally:

IGNORE THIS NOW[battleset by name always gives original GUIK (batleset 1) although the log file has the correct file passed in.]

 

scenario by name caused view of orders file at startup and time rate was always '0' (paused).

any ofthe items that are selected from a drop down list must have the "box" ticked after selecting the variable or the selected variable box must be 'clicked' a second time. you see the progress (or lack therof) in the simple command line at the foot of the launcher window. This includes options within the 'game options'.

IGNORE THIS NOW [only one logging option may be run. You can select as many as you like but it will only log the first selected. You may select 'all' and this works ok.]

Hope this helps. seems to me a great way of starting non standard games especially from custom battlesets once it is running mickey mouse.

Don Thomas

fedbck.zip

In other words, I have yet to get the launcher or using command lines to work.

 

Are you sure the launcher is in your HCE directory?

 

Yes, I unzipped it to my main HCE folder. When I hit the 'Launch GE' button on the launcher, absolutely nothing happens.

Well things happen here too fast for me, but I'll post up my fiiles from testing the older launcher, I had some issues with scenario by name (perhpas that option shouldn't be in?). I'll try the new launcher.

Iv................elps. seems to me a great way of starting non standard games especially from custom battlesets once it is running mickey mouse.

Don Thomas

Ha, you must be all asleep at last.

I've attached some log files after testing the new launcher.

In summary some problems:

didn't have much luck trying to link to a commondatabase by name in another folder.

one logging option disregarded.

problems if the command line too long.

the details are at the start of each log file which are named to indicate the general content.

I just have to work out what all the logging report items mean?

Don.

launchfeedbck.zip

Ha, you must be all asleep at last.

I've attached some log files after testing the new launcher.

In summary some problems:

didn't have much luck trying to link to a commondatabase by name in another folder.

one logging option disregarded.

problems if the command line too long.

the details are at the start of each log file which are named to indicate the general content.

I just have to work out what all the logging report items mean?

Don.

 

Nice work again! Most of the log options are at least minimally explained at http://harpgamer.com/harpforum/index.php?showtopic=3574

 

Performance logging was properly ignored, in release builds it is ignored, when I put up the next beta build that one will work since it will be a debug build.

So if its working for him, I wonder what I've managed to do wrong. It's probably my own fault, as usual.

Ha, you must be all asleep at last.

I've attached some log files after testing the new launcher.

In summary some problems:

didn't have much luck trying to link to a commondatabase by name in another folder.

one logging option disregarded.

problems if the command line too long.

the details are at the start of each log file which are named to indicate the general content.

I just have to work out what all the logging report items mean?

Don.

 

Nice work again! Most of the log options are at least minimally explained at http://harpgamer.com/harpforum/index.php?showtopic=3574

 

Performance logging was properly ignored, in release builds it is ignored, when I put up the next beta build that one will work since it will be a debug build.

I followed the link and found what looked like what I would be after " HC_Beta_Tester_Manual.pdf " but that link seemed to go to a blank page, I think I've saved the URL: "http://harpgamer.com/harpforum/index.php?act=attach&type=post&id=718", is there a manual that will let me understand this better and should it be at this URL?

Don.

Ha, you must be all asleep at last.

I've attached some log files after testing the new launcher.

In summary some problems:

didn't have much luck trying to link to a commondatabase by name in another folder.

one logging option disregarded.

problems if the command line too long.

the details are at the start of each log file which are named to indicate the general content.

I just have to work out what all the logging report items mean?

Don.

 

At one time we never slept but you'll catch us napping now and again these days.

 

Re: cmndatab.txt my counter-test was:

"D:\Games\HCCE\Winharp32.exe" -b 22 -c "D:\Games\HCCE\BARENTS.SCm" -d "D:\Games\HCCE\db\commondb.res"

It ran fine, loaded the HCDB-090427 specified by the command line and opened the specified scenario. Can you perhaps zip and attach all of the files involved in that test. I suspect your trouble may have to do with it being a BSBuilder battleset.

 

 

Re: 2logoption.txt my counter-test was:

"D:\Games\HCCE\Winharp32.exe" -l radar -l missile -b 26 -c "D:\Games\HCCE\AddOnScens\Longer Path Name with Spaces\AAMTEST3.SCq" -d "D:\Games\HCCE\db\commondb.res" -g 001111000

Logging begins. Build Date = Jun 27 2009, Build Time=14:53:54

0 harpoon.c:542 - BattleSet Specified: 26

0 harpoon.c:569 - Scenario Specified: D:\Games\HCCE\AddOnScens\Longer Path Name with Spaces\AAMTEST3.SCq

0 harpoon.c:619 - Database RES Specified: D:\Games\HCCE\db\commondb.res

0 harpoon.c:675 - Game Options Specified: 001111000

0 harpoon.c:694 - done processing arguments. Activating logging for:

0 harpoon.c:716 - radar

0 harpoon.c:720 - missile

So despite the long command line each option was read correctly (I expect command lines up to 255 to work properly and in some cases even longer ones). I ran that test on Vista x64, what OS are you using for these tests?

 

 

Re: badlogoptns.txt

From your log file fragment I can see that it choked on the -c (Scenario Specified) option. Could you perhaps try running that command line from a command prompt or by modifying a shortcut to Winharp32.exe? Just wondering if you are having a launcher problem instead of a GE issue (i.e. maybe the launcher isn't spawning the process correctly for you but the GE would interpret them correctly if it were fed in correctly).

 

 

Re: greenply.txt

Coolness, I don't think I tried playing as green, yet another good reasons for others to test

 

 

It appears the rest of your attempts worked okay. In testing your tests just now I found that you do have to specify the correct battleset for a scenario given on the command line. I did a -b 22 -c AAMTest3.SCq and was dumped into EC2003 GIUK instead of WestPac.

Ha, you must be all asleep at last.

I've attached some log files after testing the new launcher.

In summary some problems:

didn't have much luck trying to link to a commondatabase by name in another folder.

one logging option disregarded.

problems if the command line too long.

the details are at the start of each log file which are named to indicate the general content.

I just have to work out what all the logging report items mean?

Don.

 

At one time we never slept but you'll catch us napping now and again these days.

 

Re: cmndatab.txt my counter-test was:

"D:\Games\HCCE\Winharp32.exe" -b 22 -c "D:\Games\HCCE\BARENTS.SCm" -d "D:\Games\HCCE\db\commondb.res"

It ran fine, loaded the HCDB-090427 specified by the command line and opened the specified scenario. Can you perhaps zip and attach all of the files involved in that test. I suspect your trouble may have to do with it being a BSBuilder battleset.

 

 

Re: 2logoption.txt my counter-test was:

"D:\Games\HCCE\Winharp32.exe" -l radar -l missile -b 26 -c "D:\Games\HCCE\AddOnScens\Longer Path Name with Spaces\AAMTEST3.SCq" -d "D:\Games\HCCE\db\commondb.res" -g 001111000

Logging begins. Build Date = Jun 27 2009, Build Time=14:53:54

0 harpoon.c:542 - BattleSet Specified: 26

0 harpoon.c:569 - Scenario Specified: D:\Games\HCCE\AddOnScens\Longer Path Name with Spaces\AAMTEST3.SCq

0 harpoon.c:619 - Database RES Specified: D:\Games\HCCE\db\commondb.res

0 harpoon.c:675 - Game Options Specified: 001111000

0 harpoon.c:694 - done processing arguments. Activating logging for:

0 harpoon.c:716 - radar

0 harpoon.c:720 - missile

So despite the long command line each option was read correctly (I expect command lines up to 255 to work properly and in some cases even longer ones). I ran that test on Vista x64, what OS are you using for these tests?

 

 

Re: badlogoptns.txt

From your log file fragment I can see that it choked on the -c (Scenario Specified) option. Could you perhaps try running that command line from a command prompt or by modifying a shortcut to Winharp32.exe? Just wondering if you are having a launcher problem instead of a GE issue (i.e. maybe the launcher isn't spawning the process correctly for you but the GE would interpret them correctly if it were fed in correctly).

 

 

Re: greenply.txt

Coolness, I don't think I tried playing as green, yet another good reasons for others to test

 

 

It appears the rest of your attempts worked okay. In testing your tests just now I found that you do have to specify the correct battleset for a scenario given on the command line. I did a -b 22 -c AAMTest3.SCq and was dumped into EC2003 GIUK instead of WestPac.

One, I have to learn how to use these quotes when replying,

Two, re my previous badlogoptions, Ive run the program from a shortcut and from the launcher useing the same command line and whizzo, the shortcut worked and the launcher passed on a gooped up scenario name. I used the launcher with the scenario by number (a different scenario of course) but all else the same and that worked.

Attached is a zip with the three log files.

I'll work on the other stuff ASAP.

Don.

ScenByName3LogOptions.zip

Ha, you must be all asleep at last.

I've attached some log files after testing the new launcher.

........... out what all the logging report items mean?

Don.

 

At one time we never slept but you'll catch us napping now and again these days.

 

Re: cmndatab.txt my counter-test was:

"D:\Games\HCCE\Winharp32.exe" -b 22 -c "D:\Games\HCCE\BARENTS.SCm" -d "D:\Games\HCCE\db\commondb.res"

It ran fine, loaded the HCDB-090427 specified by the command line and opened the specified scenario. Can you perhaps zip and attach all of the files involved in that test. I suspect your trouble may have to do with it being a BSBuilder battleset.

 

 

Re: 2logoption.txt my counter-test was:

"D:\Games\HCCE\Winharp32.exe" -l radar -l missile -b 26 -c "D:\Games\HCCE\AddOnScens\Longer Path Name with Spaces\AAMTEST3.SCq" -d "D:\Games\HCCE\db\commondb.res" -g 001111000

Logging begins. Build Date = Jun 27 2009, Build Time=14:53:54

0 harpoon.c:542 - BattleSet Specified: 26

0 harpoon.c:569 - Scenario Specified: D:\Games\HCCE\AddOnScens\Longer Path Name with Spaces\AAMTEST3.SCq

0 harpoon.c:619 - Database RES Specified: D:\Games\HCCE\db\commondb.res

0 harpoon.c:675 - Game Options Specified: 001111000

0 harpoon.c:694 - done processing arguments. Activating logging for:

0 harpoon.c:716 - radar

0 harpoon.c:720 - missile

So despite the long command line each option was read correctly (I expect command lines up to 255 to work properly and in some cases even longer ones). I ran that test on Vista x64, what OS are you using for these tests?

 

 

Re: badlogoptns.txt

From your log file fragment I can see that it choked on the -c (Scenario Specified) option. Could you perhaps try running that command line from a command prompt or by modifying a shortcut to Winharp32.exe? Just wondering if you are having a launcher problem instead of a GE issue (i.e. maybe the launcher isn't spawning the process correctly for you but the GE would interpret them correctly if it were fed in correctly).

 

 

Re: greenply.txt

Coolness, I don't think I tried playing as green, yet another good reasons for others to test

 

 

It appears the rest of your attempts worked okay. In testing your tests just now I found that you do have to specify the correct battleset for a scenario given on the command line. I did a -b 22 -c AAMTest3.SCq and was dumped into EC2003 GIUK instead of WestPac.

following on from your comments:

re: 2logoption -

In my previous file (concerning starting paused) 2logoptions.txt, at the log segment at the line"0 harpoon.c:675" it seems that the -g options have not been passed correctly into the program. When I run the same command line in the shortcut it runs correctly.

As it works in shosrtcut I don't know if you want to persue this but I've made the following notes if you do>

The fault doesn't happen if scenario by number is chosen. the same fault seems to happen irrespective of battleset, eg I tried GUIK original and GuikHDSIII with same fault.

You asked for my OS, here are the main computer details including OS details:

my Computer:

-------------------------------------------------------------------------------------------

5.1 Name : ACER

5.2 Total Memory : 494 Mb

5.3 Free Memory : 222 Mb

5.4 Total Disk : 27.47 Gb

5.5 Free Disk : 8.23 Gb

5.6 System Up Time: 4 days, 23 hours, 52 minutes, 11 seconds

5.7 Processor : Intel® Celeron® CPU 2.80GHz

5.8 Display Mode : 1024 x 768, 16 bit

5.9 Display DPI : 96

5.10 Video Card : Intel® 82852/82855 GM/GME Graphics Controller (driver 6.13.10.3510)

5.11 Printer : Canon iP4600 series (driver 2.20.2.80)

 

Operating System:

------------------------------------

6.1 Type : Microsoft Windows XP

6.2 Build # : 2600

6.3 Update : Service Pack 2

6.4 Language: English

6.5 Charset : 0

 

re: cmndatab-

regarding my previous cmndatab.txt, I looked over your comments and tried a different battleset and scenario.

 

Command Line: "C:\Matrix Games\HCE\Winharp32.exe" -b 22 -c "C:\Matrix Games\HCE\addonscenerios\HFAST.SCm" -d "C:\Matrix

 

Games\HCE\Backup\200906rel\commondb.res"

So I'm in GUIK EC2003 and used (someones) scenario holdfast. The database is the most recent I have - 28/04/009.

When I copy the simple comand line and transfer it to my winharp shortcut it works, correct database and correct operation.

When I use launcher it works if I Don't specidy the database but when I specify the database (as in the above 'command line') I get the 'program' has encounted an

 

error and has to close etc.

Again as the GE seems to be OK is it worth persuing?

If I get a problem I can just build the command line in the launcher and transfer it to the shortcut - that has worked every time.

Don.

Thanks Don, I'll pursue it since eventually the launcher should be made into a handy tool but I'm happy to see the GE reading the options correctly. I mentioned 255 in an earlier post, that should have been 255 characters not 255 widgets or options or anything else.

 

I'll see if I can snag Brad with his multi-core processor to test the -p option for affinity.