TonyE

Allright, in the same fashion as the KC-45 awarding of the contract, the nays with 2 votes takes the day against the yeays with 3 votes. For the time being the beta testing defects will be tracked separately from the defects in released versions. Please make new defect reports for released versions of the game in the HCE Bug Tracking area http://harpgamer.com/harpforum/index.php?a...p;showproject=6 For the moment, defects in beta versions should continue to be reported here but I'll probably open up a beta area section within bug tracking so I have a more trackable list to work from. Also for the time being I'll transfer anything from Mantis and the defect tracking forum at HG as I see fit and will continue for the most part to use the existing reports where they are instead of moving them. Thanks for the input, I was swayed

, funny indeed! I still must say it will be nice to see whatever kind of 'score' sheet the Air Force produces for the GAO detailing the weighting of the individual points on the requirements list. I don't think Boeing is all that wrong to question the outcome based on the requirements, but is perhaps outside the best interests of the country to push this in a self-serving general appeal. That didn't come out very clearly... From what little I know on the topic, Boeing met the criteria of the Air Force tanker request better and more fully than EADS but in the end the EADS solution is better, despite not meeting the criteria as well.

I'm really torn on what to do. The easy way out is to do as Larry says and have split lists, one for public use and/or current public patch level, and a beta only list for unreleased builds. As for the limited access to the beta area, everything within the "HC Beta Testing" is limited at present to 15 people, a few will be kicked out any day now who did not renew their NDAs with AGSI or have not contributed meaningfully since the HCE release. So our group here is small and access to the beta areas will remain limited even if there ends up being a single defect list. Hmm, that just gave me an future feature idea on what to ask the people who make that Bug Tracker module, setting visibility of each defect based on the group the user belongs to (so we of the HCBeta group would see everything, Members would only see defects from release versions). However that is down the road and isn't a viable solution at this moment. Brad, Akula, your input would be appreciated.

The 2008.024 beta patch is now an official patch and available from Matrix Games. See the earlier announcements for details about what benefits the patch brings to the base 2007.000 release: http://harpgamer.com/harpforum/index.php?showtopic=2644 Where to get the patch: http://www.matrixgames.com/games/downloads.asp?gid=325 Yes, it is big, thanks to the map graphics needed for the BattleSet Builder

HCE - 2008.027 ============== - Chg:0000 GE Split graphics out of Harpoon32.dll and Winharp32.exe and into individual files within the Graphics directory.

HCE - 2008.027 ============== - Chg:0000 GE Split graphics out of Harpoon32.dll and Winharp32.exe and into individual files within the Graphics directory. So in addition to testing the things in 2008.026 release notes, note if images are missing from dialogs (victory, staff assistant, etc.) in various battlesets. If you are a bit more advanced, try replacing some of the graphics and see what happens. If you are really advanced, look for memory leaks as there are two parts of the changed code that may be leaking memory with each load of one of the graphics.

I didn't find any applicable rules in H3 paper but there is one in H4.1 paper. Rule 7.2.5 Damage to Stealthy Ships blah blah blah If a ship or submarine sustains 10% damage or more from an underwater attach, treat them as a Noisy target for sonar detection (equivalent to a BSL of 48). Vessel also loses benefit of anechoic coating, if carried.

I think Sitrep #32, page 22 offers some related guidance. Paul Kopplin asks... What if a plane doesn't have fuel to dogfight in burner, can the fighter stay at military power and at what penatly? Larry Bond replies... If a plane has burner and chooses not to use it, hit maneuver rating is reduced by 1.5, so a burner F-16 @ 4.5 would be reduced to a military power F-16 @ 3.0. I think that applies well do your situation, only we don't know why your plane can't reach maximum thrust but I think the reasoning applied by Bond makes sense in your situation as well.

I'm somewhere between you two gentlemen. I don't see any harm in treating submarines differently than surface craft and find Brad's argument there very convincing (about above waterline damage not materially harming the passive sonar noise level). I also think the equations to determine the increase in noise might be somewhat related to displacement (a field handily enough available to us). Or maybe noice increases by 2 points per 10% damage until 50% damage, and 1 point per 10% damage thereafter (on the premise that once it is damaged to 50%, it isn't going to get much noisier).

In theory there are 25 beta testers if you count myself, CV32, and Akula, in practice we have about 7 contributing on a regular basis.

I voted Yes, but somewhat reluctantly. Benefits of one area, Bug Tracker, publicly accessible: * As coder guy I like the idea of looking in one place for all of the defect reports. * I don't trust mantis, the fact that many of the saved games there no longer exist (the files are zero length, AGSI lost em) reinforces that idea. Mantis is also not public, one of the prime reasons for using the Defect Reports forum here at HG. * Public accessibility. If someone has the initiative to look and see if a bug is already known, they can do so. * I trust the data won't disappear or be edited, my coworker does weekly backups of everything at HG, that is in addition to the backups done by the hosting provider. At most we'll lose a week of effort. Detriments of one area: * Moving all the crap over there I would tend to finish out anything of value at Mantis rather than move it all over. Still, it will be a pain to consolidate. * I'm going to be breaking HC in a lot of ways and very severly on the way to a 2nd patch. That will mean beta testers reporting dire situations that the general public could interpret very unpleasantly. * Public accessibility - I think the above states my hesitancy well.

File Name: WestPac 1.0 Orders PDF File Submitter: TonyE File Submitted: 10 Mar 2008 File Category: Tools/Docs Authors: TonyE Quick and dirty printout of orders for tutorial scenario. Click here to download this file

Due to recent upgrades to the forum software and components here at HarpGamer, the Bug Tracker referenced just under the HG logo has become useful for defect tracking. I'm wondering what everyone's thoughts are on just having one set of defects listed for HCE, all of them being in that single area. http://harpgamer.com/harpforum/index.php?a...p;showproject=6 Please explain your choice. With this change I think we'll stop making new entries into Mantis as the Bug Tracker is doing all of the key steps of Mantis. Thank you

Addressed long ago as you'll see in the patch. If you want to work around, make the tanker type planes transports in the PE.

Place holder

Nothing wrong, just still uploading that file, it is now uploaded.

HCE - 2008.026 ============== - Chg:0000 GE For pre-commondb battlesets, play prop launch sound only when propulsion type == 1. (thanks NAVMAN) http://www.matrixgames.com/forums/tm.asp?m=1732358 - Chg:0000 GE In debug builds, show when the GE expires. - Chg:0000 GE Split sounds out of Harpoon32.dll and into individual files within the Sounds directory. - Chg:0000 GE Allow high PicIDs for commondb battlesets. - Chg:0000 GE Ignore BattleSetPath from registry, make it the same directory as the one the game was launched from. - Chg:0000 SE Allow high PicIDs for commondb battlesets. - Chg:0000 SE Ignore BattleSetPath from registry, make it the same directory as the one the game was launched from. - Chg:0000 BS EC2003 IOPG Scenario 5.0 victory conditions fixed, AOE ship type changed to MPS. (thanks Maromak)

HCE - 2008.026 ============== - Chg:0000 GE For pre-commondb battlesets, play prop launch sound only when propulsion type == 1. (thanks NAVMAN) http://www.matrixgames.com/forums/tm.asp?m=1732358 - Chg:0000 GE In debug builds, show when the GE expires. - Chg:0000 GE Split sounds out of Harpoon32.dll and into individual files within the Sounds directory. - Chg:0000 GE Allow high PicIDs for commondb battlesets. - Chg:0000 GE Ignore BattleSetPath from registry, make it the same directory as the one the game was launched from. - Chg:0000 SE Allow high PicIDs for commondb battlesets. - Chg:0000 SE Ignore BattleSetPath from registry, make it the same directory as the one the game was launched from. - Chg:0000 BS EC2003 IOPG Scenario 5.0 victory conditions fixed, AOE ship type changed to MPS. (thanks Maromak) HCE - 2008.025 ============== - Chg:2415 GE Started to kludge a workaround for situations where planes are within the minimum range of one weapon but outside minimum range of the next, resulting in a request to attack with cannon fire. This kludge only affects AAM engagements! (thanks Herman) Pretty obviously some things to test there gents. Note also that BattlesetPath is now ignored from the registry and is assumed to be the directory from which you launched the GE or SE. This means you can now do lots of HC installations and not worry about the BattlesetPath (in this version and in the future).

HCE - 2008.025 ============== - Chg:2415 GE Started to kludge a workaround for situations where planes are within the minimum range of one weapon but outside minimum range of the next, resulting in a request to attack with cannon fire. This kludge only affects AAM engagements! (thanks Herman)

Addressed in 2008.025 for AAMs only, this will not help any situations with ASMs.

Are you by chance using 'large fonts' on the LG? HC really doesn't understand large fonts but I suppose we'll have to figure something out eventually as more and more people use them.

Addressed in 2008.026, the artificial limit is removed for commondb battlesets, wonder what the next limit will be...

Will the travesty never end! Down with the Bugs, use some of the money to grease the JSF wheels.

A little birdie told me HC is coded in C, the PE is obvious Access (97), and some of the utilities in Delphi.