HCE - 2009.034

==============

- Chg:0000 GE More command line option modifications.

-g, added a 9th digit to set the initial time compression.

0=paused, 1=1:1, 2=5:1, 3=10:1, 4=30:1, 5=60:1, 6=300:1,

7=600:1, 8=1800:1

so -g 111111118 would result in 30min:1sec initial time

compression.

-p option to set the CPU affinity mask.

examples...

-p 1 (run on CPU 0)

-p 2 (run on CPU 1)

-p 3 (run on CPU 0 and 1)

-p 4 (run on CPU 2)

-p 8 (run on CPU 3)

-p 16 (run on CPU 4, see a pattern yet?)

and so on and so forth

you can read about affinity masks various places on the

Internet, our command line option is decimal, many

sources on the Internet list only hexadecimal so you

may have to do conversions in some cases.

- Chg:0000 GE Fixed a situation where an assertion could be thrown in

the Sonar function.

- Chg:0000 GE Disabled "AutoTest is Activated" dialog when the -a command

line is used so that scenarios can be started from the

command line without user input.

- Chg:0000 GE Disabled the "Debug version..." dialog when the -a command

line option is used. Same reason as above.

- Chg:0000 SE Added command line options with the same functions

as the GE -b -c -d -r.

Added -t command line switch to specify working directory

i.e. -t d:\games\hcce

Note that the SE is a 16-bit application and hence works

on short filename

wrong: -d "C:\Matrix Games\HCE\commondb.res"

right: -d C:\Matrix~1\HCE\commondb.res

- Chg:0000 Big improvements to the patch installer script. It will

now properly read the previous installation directory,

make a backup of replaced files, and register itself

correctly.

 

Obviously it is time to edit your shortcuts to try different command line options

another testing note, from here on out please comment on any installer inconsistencies and problems. I made a concerted effort with this build to make the installer do things smarter, make backups, etc.

Installer installed fine.

The command switches seem to be working.

The command switches seem to be working.

 

Can you provide some more detail? For instance did you try the SE applicable switches, did you load a saved game from the command line, etc.

 

Thanks

Tony,

 

At the risk of showing my age, I was banging out DOS commands on a PC when Windows was still a pipe dream. As an old DOS hand, I'm certainly familiar with "Command line switches", but I'm lost as to how they apply to Harpoon.

 

Do I modify the shortcut to run with the switches?

 

Thanx,

 

Buddha

Tony,

 

At the risk of showing my age, I was banging out DOS commands on a PC when Windows was still a pipe dream. As an old DOS hand, I'm certainly familiar with "Command line switches", but I'm lost as to how they apply to Harpoon.

 

Do I modify the shortcut to run with the switches?

 

Thanx,

 

Buddha

 

You can modify the shortcut, or open a command prompt and navigate to your HCE directory then use the switches since that may be more familiar to you.

 

here's an example from a batch file I have for auto-testing

Winharp32.exe -f 01-01b.txt -a -b 01 -c 01 -g 011111118 -p 1

 

Winharp32.exe - the name of the executable

-f 01-01b.txt - use 01-01b.txt as the log file instead of ge.log

-a - autotest activated

-b 01 - battleset #1 aka original GIUK

-c 01 - scenario 1.0 aka introductory scen

-g 011111118 - game options 0=Blue side, 1=Possible Nuclear Release, 1=Snorkeling Subs, 1=Realistic Weather, 1=Normal Maint Failures, 1=Start with full ordnance, 1=Auto Formation Air Pats, 8=30min:1 time compression

-p 1 - run the game on the first CPU core

 

The various options are explained in the 2009.034, 2009.033 release notes and earlier ones in the beta tester manual.

Tony,

 

At the risk of showing my age, I was banging out DOS commands on a PC when Windows was still a pipe dream. As an old DOS hand, I'm certainly familiar with "Command line switches", but I'm lost as to how they apply to Harpoon.

 

Do I modify the shortcut to run with the switches?

 

Thanx,

 

Buddha

 

You can modify the shortcut, or open a command prompt and navigate to your HCE directory then use the switches since that may be more familiar to you.

 

here's an example from a batch file I have for auto-testing

Winharp32.exe -f 01-01b.txt -a -b 01 -c 01 -g 011111118 -p 1

 

Winharp32.exe - the name of the executable

-f 01-01b.txt - use 01-01b.txt as the log file instead of ge.log

-a - autotest activated

-b 01 - battleset #1 aka original GIUK

-c 01 - scenario 1.0 aka introductory scen

-g 011111118 - game options 0=Blue side, 1=Possible Nuclear Release, 1=Snorkeling Subs, 1=Realistic Weather, 1=Normal Maint Failures, 1=Start with full ordnance, 1=Auto Formation Air Pats, 8=30min:1 time compression

-p 1 - run the game on the first CPU core

 

The various options are explained in the 2009.034, 2009.033 release notes and earlier ones in the beta tester manual.

Tony,

 

That certainly makes sense. I like the DOS window idea, since it leaves my existing shortcuts unchanged.

 

Thanx,

 

Buddha

To help you provide more detail on what you tested, copy the first few lines of your GE.log files (or whatever you had them renamed to), they will list the command line option attempted.

 

example: (hint, I specified a database .res file on the command line)

Logging begins. Build Date = Jun 24 2009, Build Time=20:42:41

0 harpoon.c:619 - Database RES Specified: hcdb-090427.res

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

Yet another attempt to spur you guys on and it only works for the GE. It will error out on occasion, I don't care about that at this point, I only care if it blue screens your computer (it has only done that to me when I run it in the debugger). It should help you form command lines. Post your log fragments and results as indicated in earlier posts.

 

2009/07/25 uploaded version 2009.037

Maximum length of command line options increased from 80 characters to 2048 to coincide with Windows 2000+

Idiot prompt added to make sure the listed GE file actually exists.

2009/07/14 uploaded version 0.1.0.1

ComboBoxes are a little more responsive (still easy to fool them)

BattleSet by filename option greyed out since the GE doesn't support it

Log options now each get their own -l

Launcher_v2009.037.zip

I just don't get it.

 

When you type it out for me, I can make it work. Trying to do it on my own...not so much.

To help you provide more detail on what you tested, copy the first few lines of your GE.log files (or whatever you had them renamed to), they will list the command line option attempted.

 

example: (hint, I specified a database .res file on the command line)

Logging begins. Build Date = Jun 24 2009, Build Time=20:42:41

0 harpoon.c:619 - Database RES Specified: hcdb-090427.res

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

 

Ejem, I´ll love to help, but this command line thing is chinese for me. Installer works fine though.

I just don't get it.

 

When you type it out for me, I can make it work. Trying to do it on my own...not so much.

 

I can always keep helping... Don't forget the launcher in earlier post of this thread, unzip to your HCE directory and run it. It'll build a command line based on your chosen options then click "Launch GE". Make sure you actually get the options you chose, grab the first lines of the log file, rinse and repeat.

I just don't get it.

 

When you type it out for me, I can make it work. Trying to do it on my own...not so much.

 

I can always keep helping... Don't forget the launcher in earlier post of this thread, unzip to your HCE directory and run it. It'll build a command line based on your chosen options then click "Launch GE". Make sure you actually get the options you chose, grab the first lines of the log file, rinse and repeat.

Hope it OK, I tried the launcher so as to get a debug type readout log (still trying to see what's happening to close range air 2 air guns) and have noticed a couple of things with the launcher:

If I use batleset by file name (and choose the HDSU.res file) it doesn't launch but if I use battleset by number (#35 - HDSU.res) it works.

In the "game options" I have to select the option value from the pull down window, then rehit the aroow button (like select twice) to register the selction in the "simple text" line (which I assume is the command line being built)

In the logging option I get problems if I select more than one individual option.

 

If of significance here are details of my coputer:

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

 

Don thomas

PS This is more fun than playing the game (nearly)

Thank you Don! I have just about lost all hope, you've restored some.

 

I'm reading in your post two issues with the command line options of the GE:

1. The GE isn't recognizing the use of multiple log specifiers (ex. both radar and sonar on the same command line). I can also confirm this incorrect behavior.

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 would be a great help if you would list the options that you have proven do work (I'm guessing that includes the -g switch), bonus points if you include the ge.log fragment showing the options you chose (see http://harpgamer.com/harpforum/index.php?s...st&p=14844)

 

I'll see about improving the launcher a bit this evening since you put in some effort. You may well like some of the gun changes in 2009.037...

- Chg:0000 GE Added code for intercepts based on air to air guns, both player

and AI. Disabled the internal 3nm guns in commondb battlesets.

in short that means if you give a loadout an air to air gun it will work in terms of honoring intercept requests rather than depending upon the 3nm built-in guns that don't adhere to intercept logic.

 

So keep at the command line options testing so that we can release another build.