Woos -> RE: witpDecoder for the Allies (12/2/2006 10:30:17 PM)
|
quote:
ORIGINAL: Oliver Heindorf also da kann ich mir auch linux drauf machen, das hat dann den selben charm Now that explains the problem. You didn't read the fine print (see last bullet of post 71). Besides that, not all errors stem from mods/WitP. Sometimes the internal checks catch what they were intended to do: an internal error. So the "bad LCU count" is witpDecoders fault and should have hit most Allied players (as I said, Allies are badly tested). New version with fix is uploaded (same name and URL and same procedure to install but with another database format change). As additional goodie you get: [image]local://upfiles/16906/3FB75A4D6B3C4389A961AE354C96AC58.jpg[/image] I liked the WitPShips.xls file someone posted a few weeks ago (sorry, forgot who it was) but it was for the wrong scenario. So I shamelessly stole the idea and integrated it into witpDecoder so now one can get the same information for all scenarios. The tab probably still has bugs (this is a release to fix the LCU count problem) and no documentation yet. Concerning the ease of installation: If you want to write an installer for witpDecoder to ease everyone's job, great, just do it! Otherwise you will have to live with my plans for development which still include new functionality as the highest priority because that's what I want from the tool. Sooner or later database setup will be completely GUI driven (if only to reduce the support requests), but since setup is only a one time effort for everyone that's low priority.
|
|
|
|