HCE - 2008.067

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

- Chg:B047 GE Limited how the AI will execute BOL air to surface and

Surface to Surface missile launches. If the axis of the

uncertainty zone as seen by the firing unit to the target

is greater than 50nm (uncertainty zone width when drawing a

line from attacker to target), the AI will not fire. The

AI will also not fire if the weapon range/5 is less than

the uncertainty zone width. If the uncertainty zone is

range ASMs). (thanks Herman)

http://harpgamer.com/harpforum/index.php?a...&showbug=47

- Chg:B054 GE No longer show the correct count of land units and damaged

land units at a base if those units are not currently detected.

(thanks Herman)

http://harpgamer.com/harpforum/index.php?a...&showbug=54

- Chg:B048 GE Don't prompt the player to use air-to-air cannon fire against subs.

Do prompt player to close range to launch depth charges.

(thanks Herman)

http://harpgamer.com/harpforum/index.php?a...&showbug=48

 

 

Note about logging the uncertainty zone stuff.

 

example command line:

winharp32.exe -f c:\mylog.txt -l missile

 

in mylog.txt you are then looking for lines that contain:

ValidBOAttack returns FALSE

those are indicating an abandoned BOL due to a larger than acceptable uncertainty zone.

- Chg:B054 GE No longer show the correct count of land units and damaged

land units at a base if those units are not currently detected.

(thanks Herman)

http://harpgamer.com/harpforum/index.php?a...&showbug=54

 

This one has already been accounted for.

 

As for the other two, I defer to anyone who has the Demo/USNI battleset on their machine (Herman?).

- Chg:B048 GE Don't prompt the player to use air-to-air cannon fire against subs.

Do prompt player to close range to launch depth charges.

(thanks Herman)

http://harpgamer.com/harpforum/index.php?a...&showbug=48

 

Ran the test scenario with beta .023.

This seems to be fixed.

- Chg:B047

 

Oh God, how I can't do this command line stuff.

Please explain it again like I'm four.

- Chg:B047

 

Oh God, how I can't do this command line stuff.

Please explain it again like I'm four.

 

If you need lots of pictures we could result to that, until then.

 

Make yourself a shortcut to Winharp32.exe..

1. Right-click winharp32.exe and click Copy

2. Right-click a blank spot in that same window and click Paste Shortcut

3. Now right-click that new shortcut and click Properties

4. Look at the target line, it either ends in Winharp32.exe or Winharp32.exe", either way add a space at the end then get on with your logging items.

5. My target line for ECM Logging is: D:\Games\HCCE\Winharp32.exe -l ecm -f d:\games\hcce\ecmlog.txt

6. That line says I have HCE installed in D:\Games\HCCE, you probably don't so keep your own path, the -l ecm says to log ECM information, -f d:\games\hcce\ecmlog.txt says where to put the logged information.

7. A more simple example is to add the following to the right of your winharp32.exe -l ecm c:\ecmlog.txt

8. That will dump the logging information to a file you can open with notepad at the root of your C:\ drive.

 

Hopefully that will get you started.

When you draw me those pictures, use lots of pretty colored crayons so I can hang them next to my Horsey and my Puppy drawings, because I can't get this to work like it says.

 

What I did get was a Message Log that shows that within the 0:19:36 Time Remaining period, Goas were shooting down Sandboxes and a Sandbox hit and sank a Red ship.

I also have a GE log of this game with a lot of ECM data that I don't know how to interpret.

 

Based on the Red ship being sunk by Red missiles, though, I'd guess this still isn't fixed.

Logs.zip

You were close except we needed missile logging not ECM logging (I should have used missile in my example if I would have been thinking). Please try again (ge.log in your zip was the right file)

 

Change the -l ecm to -l missile in your command line.

 

Getting there

I'm now getting the missile data logs.

So, all I have to do now is play this until Red attacks Red and send in the logs?

That sounds like a plan to me. It is tough to know when you've seen the right activity (hence the log) since what we're doing is preventing red from committing fratricide in some situations.

I wonder, would a quick and dirty scenario with a red ASuW unit, a few red merchies and blue merchies in the same area produce the desired results? At least it would be a more controllable test.

That might provoke the desired result Akula, yep.

After spending a lot of fruitless time waiting for some Red fratricide last night, I thought of taking the Slava and surrounding it with assorted ships and letting it find a Blue sacrificial unit. I haven't been able to run this test scenario yet.

Akula, please write and run yours in the meantime - I'll pack for vacation instead.

After spending a lot of fruitless time waiting for some Red fratricide last night, I thought of taking the Slava and surrounding it with assorted ships and letting it find a Blue sacrificial unit. I haven't been able to run this test scenario yet.

Akula, please write and run yours in the meantime - I'll pack for vacation instead.

 

Do you have your log file to post? We are after all trying to prevent the stupid fratricide so you shouldn't see it, but the log should note when Red was eager to commit fratricide.

Larry sent over a log but it did match the title of his zip, fruitless...

 

From the original post, the log will have "ValidBOAttack returns FALSE" in it somewhere if the adjusted code is being activated.

 

In the next build I've added the opposite logging line, ValidBOAttack returns FALSE but that doesn't really make any difference in this testing, we're trying to get that first message with the False.

 

Hint, with your log file open in notepad or wherever, go to Edit\Find then paste in ValidBOAttack returns FALSE and do the search.

Another fruitless day....

This is something that's going to happen accidently, so I'll just be playing normal scenarios with the logging on and hope for a bite.

I don't think this should hold up the patch release.

Leaving in 15 minutes for Gettysburg. see you in a week.