Combat Reporter - report monitoring tool (Full Version)

All Forums >> [New Releases from Matrix Games] >> War in the Pacific: Admiral's Edition >> Scenario Design and Modding



Message


bretg80 -> Combat Reporter - report monitoring tool (5/3/2010 2:05:15 AM)

Make sure you don't use Java 64bit as I have tested it and it does not work because of a 3rd party library I'm using that only supports 32 bit java.

If you are getting a black map, it is probably a java heap issue, which means you don't have enough memory to load the map.

Some possible solutions are to change the combatreporter.bat file as follows:

java -splash:UV1024.jpg -Xmx768m -server -jar combatreporter.jar

to

java -splash:UV1024.jpg -Xmx1024m -server -jar combatreporter.jar

you can increase it to 2048m if you want, but you shouldn't have to.

if that doesn't work, feel free to PM me.


Latest version of Combat Reporter is out on 4/4/2011. Link is here:

https://sites.google.com/site/witpaecombatreporter/

Release notes for 1.0521

1. added additional logging to diagnose map loading and out of memory issues
2. changed timeout for map load failure to 10 mins to address slow or virtual machines.

Release notes for 1.052

1. Fixed a potential deadlock condition when an error occurs during loading of the map file.
2. Added some logging output to the cmd window to assist in troubleshooting.
3. Fixed the array out of bounds condition found by BigDuke66.

1. Fixed a parse bug for radio transmissions in the Sigint report.

Release notes for 1.05

1. New map scrolling. You can now move the cursor on the map to scroll. Kinda like google maps. The hand icon will change to indicate scroll mode when you push the mouse button. I was really tired of the old clunky way it worked, so I fixed it. :-)

2. Map scrolling should be faster and more fluid. Enjoy !!


Release notes for 1.041

1. When mouse is over the map and you don't move it for a second or so, the hex coordinates for the mouse location will show on the map. They will go away when you move the mouse again.

2. Fixed a bug where some locations were not found in the database and thus the map navigator was not finding the location. If you find anymore of these, please send me a copy of the report file and I will try to figure out what I am missing :-)

3. Added a progress bar to show map load status. You can still open reports while the map is loading, but if you have a slower machine, this will give you an idea of progress. If you have a fast machine, you may not see it. Also, the map should load a lot faster now. Turns out the old version was trying to load it twice. Bummer :-)

4. 1.04 fixes the hex coordinate display. It was erroneously reporting the hex location in some cases.

5. 1.04 fixes a number of parsing bugs. You should be able to find more locations now.

6. 1.041 fixed the hex placement and hex display bug for odd Y coordinates. Should work properly now.




Combat Reporter road map - target date for next update is now Summer 2011 (too busy at work)

1. New UI - Calendar will show the air/sea/land summary results - select a day and see details

2. Display sighted ships / planes with speed and direction vectors on the Map.

3. Show combat by location over a period of time to allow historical views. I have some ideas on how to do this using the map. I'll share my concepts later this summer.

4. Enhance the readability of the reports through better organization.

If you would like more information on how to use CombatReporter I have also included a users guide and have incorporated feedback from the community.

Thanks everyone for your support and great ideas.

A few changes to note from the beta.

1. The map is no longer included and you need to tell Combat Reporter where you installed WitPAE so it can find the WitPAE map. You will set this in the preferences when you start the application. This reduces the overall size of the download and the extra handling of a separate map. The only requirement is that you have to be using patch 3 with the enhanced map sizes. I think they were lower res before patch 3. If not, then no issues for earlier releases.

2. The preferences dialog will help you configure Combat reporter to work on your system. Read the user guide for assistance if needed. It should be more intuitive now.

3. Post questions on the forum if you need help. The tool is being used by quite a few people and they should be able to help if I can't get back to you quickly enough.

Enjoy !!!!!!

Bret

P.S. I have run this by the AE team and have their permission to release this tool.

Here is a picture of the main screen. [8D]

[image]local://upfiles/32017/4C604C5708E8407B8874D7094B3A1696.jpg[/image]




khyberbill -> RE: Combat Reporter Beta (5/3/2010 2:37:01 AM)

Can this handle two day turns?




rjopel -> RE: Combat Reporter Beta (5/3/2010 2:43:35 AM)

Where's the link?




sdevault -> RE: Combat Reporter Beta (5/3/2010 3:15:44 AM)

I think I love you...




bretg80 -> RE: Combat Reporter Beta (5/3/2010 3:40:53 AM)

I believe two day turns are reported in a single file, and if so, this will work. I haven't tested it it with multi-day turns yet. So if you are a multi-day player, please let me know if you want to test it.

Okay, I went ahead and published the link (see first posting in this thread), but I really want a few grognards to test it first so I know that it will work for others. I don't want too much egg on my face when I release it as I want it to work for most of you and so I need a few good testers first.

A few things I want to double check before releasing it:

1) Does it run on XP? I run it on Win 7.
2) How well does it run on older machines. I have a quad core 8 GB monster machine. How well does it run on a single core XP machine with only 2GB?
3) What kind of things did I miss. Is it reporting everything properly?
4) How easy is it to use?
5) Is it useful? I believe so, but what do you think?
6) Are the docs good enough. What did I miss?


PM me or let me know your interest in testing on this thread. You have the link, so you can download and get started. If you sign up to be a tester - I will support your endeavor to get it installed and running. [8D]

I'm very excited about getting this out to everyone, so sign up and help test it so I can release it to everyone. [:D]

I can't play WITP anymore without this. It is now my crutch [:D][;)]




bretg80 -> RE: Combat Reporter Beta (5/3/2010 4:43:27 AM)

First tester signed up. Four to go. I'll keep everyone appraised of our progress. He is a win7 dual monitor tester. Any XP testers out there?




Baloogan -> RE: Combat Reporter Beta (5/3/2010 5:24:12 AM)

This utility is great. 




bretg80 -> RE: Combat Reporter Beta (5/3/2010 5:50:41 AM)

First bug fixed. When clicking on sigInt reports about moving ships, CombatReporter was confused and could not figure out which keyword "on" in the report string it should use to find the location. B1.01 now corrects this problem.

Thanks for the help on this Baloogan.




Sredni -> RE: Combat Reporter Beta (5/3/2010 10:34:49 AM)

I wish my computer could handle dual monitors, this mod sounds awesome :D

Good luck with the testing.




Knavey -> RE: Combat Reporter Beta (5/3/2010 8:43:06 PM)

This looks really good. Similar to Bodhi's utility for WitP which I used extensively.

Keeping an eye out for its release. Will be very helpful.

Thanks for putting the effort into it.





aristoteles -> RE: Combat Reporter Beta (5/3/2010 9:47:21 PM)

Wow, a really nice utility, thanks a lot for your effort!!




tbridges -> RE: Combat Reporter Beta (5/3/2010 10:19:51 PM)

Outstanding! This will be a terrific help! [&o][&o][&o]




Baloogan -> RE: Combat Reporter Beta (5/3/2010 11:32:51 PM)

I like playing without combat animations or combat reports on and using this utility to review the combat




kaleun -> RE: Combat Reporter Beta (5/4/2010 3:56:32 AM)

This sounds great! I never could get WITP tracker to work (too complicated to make it run) If this works as promised it should be fantastic.




bretg80 -> RE: Combat Reporter Beta (5/4/2010 5:22:52 AM)

I'm very pleased to hear that CombatReporter is working well. I only have one tester right now and so far aside from an initial defect,the tool is working as advertised. I plan to make a few more changes this week and if all goes well, I'll release it to the community next week.

Thanks for your support everyone. [:)]




Baloogan -> RE: Combat Reporter Beta (5/4/2010 6:54:31 AM)

Seriously useful :) I never looked at all the intel available to the allied player.




Lifer -> RE: Combat Reporter Beta (5/4/2010 3:18:50 PM)

When you click the About menu choice, the program exits without warning.  Minor I know.  Very useful tool to go back and review reports.  How does this do with multiple games that overlap the dates in both games?

Greg




hused84 -> RE: Combat Reporter Beta (5/4/2010 4:11:38 PM)

Error:?? only open 1 time, configure, restart, crash


Microsoft Windows XP [Versión 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

D:\juegos\War in the Pacific Admiral's Edition\tools\Combat report>combat report

"combat" no se reconoce como un comando interno o externo,
programa o archivo por lotes ejecutable.

D:\juegos\War in the Pacific Admiral's Edition\tools\Combat report>combatreport.
bat

D:\juegos\War in the Pacific Admiral's Edition\tools\Combat report>java -Xmx1024
m -jar combatreport.jar
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader.main(JarRsrcLoa
der.java:56)
Caused by: org.codehaus.groovy.control.MultipleCompilationErrorsException: start
up failed:
script1272985580625873073245.groovy: 1: unexpected char: '\' @ line 1, column 13
.
watchDir="D:\juegos\War in the Pacific Admiral's Edition\SAVE"
^

1 error

at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollecto
r.java:296)
at org.codehaus.groovy.control.ErrorCollector.addFatalError(ErrorCollect
or.java:143)
at org.codehaus.groovy.control.ErrorCollector.addError(ErrorCollector.ja
va:113)
at org.codehaus.groovy.control.ErrorCollector.addError(ErrorCollector.ja
va:125)
at org.codehaus.groovy.control.SourceUnit.addError(SourceUnit.java:353)
at org.codehaus.groovy.antlr.AntlrParserPlugin.transformCSTIntoAST(Antlr
ParserPlugin.java:97)
at org.codehaus.groovy.antlr.AntlrParserPlugin.parseCST(AntlrParserPlugi
n.java:69)
at org.codehaus.groovy.control.SourceUnit.parse(SourceUnit.java:249)
at org.codehaus.groovy.control.CompilationUnit$1.call(CompilationUnit.ja
va:158)
at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(Compil
ationUnit.java:831)
at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(Compilat
ionUnit.java:519)
at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(Co
mpilationUnit.java:495)
at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.j
ava:472)
at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:291)
at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:262)
at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:206)
at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:216)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoCachedMet
hodSiteNoUnwrapNoCoerce.invoke(PojoMetaMethodSite.java:229)
at org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite.call(PojoMeta
MethodSite.java:52)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSi
teArray.java:40)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCa
llSite.java:117)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCa
llSite.java:125)
at groovy.util.ConfigSlurper.parse(ConfigSlurper.groovy:148)
at groovy.util.ConfigSlurper$parse.call(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSi
teArray.java:40)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCa
llSite.java:117)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCa
llSite.java:125)
at com.bret.witpae.CombatReport.main(CombatReport.groovy:41)
... 5 more




hused84 -> RE: Combat Reporter Beta (5/4/2010 4:18:19 PM)

Jeje solution, the instalation game is D:\juegos\War in the Pacific Admiral's Edition\SAVE but the program requerit this path
D:/juegos/War in the Pacific Admiral's Edition/SAVE ,note the diferent \ and /




Mistmatz -> RE: Combat Reporter Beta (5/4/2010 4:26:38 PM)

Seems to be a nice tool. Is there a way to zoom closer into the map with the next build?




Rainer -> RE: Combat Reporter Beta (5/4/2010 4:53:26 PM)

combatreport 1.0 - b1.01

It should be pointed out that the date required is the Real Time Date of the save, not the Game Date.
For the benefit of our international friends it also should be made clear what that Time Format really is.

The default (during initialization) simply says 04/01/2010 12:00 AM which means
Month/Day/Year or MM/DD/YYYY

So you enter in this field the earliest real date from the save you want the reports to begin with.

Say you have a save dated March, 23, 2010 and you want the reports to start with that save.
Then you would enter in the date field: 03/23/2010 12:00 AM
Make sure your entry looks exactly like the example above including the time.
Otherwise the utility will fail (the exact time doesn't seem to matter but the entry must be there and it must be in this form).

If the utility fails to start delete the file named combatReport.properties (or all files in the tool's directory) and restore this file (or all files) from the zip file.
Then try again.
Tip: To enter the save files home folder it may be best to use cut and paste in order to avoid typoes.


EDIT: The file combatReport.properties seems to be a plain ASCII file, and thus can be edited with any ASCII editor, like Wordpad. Just make sure to save the file as a plain text file, and also make sure there is NO extension after the save. Meaning the file is still named combatReport.properties (and not combatReport.properties.txt).




Rainer -> RE: Combat Reporter Beta (5/4/2010 5:11:38 PM)


combatreport 1.0 - b1.01

As an afterthought to my last message: if the date/time given is invalid it would be great if the tool would default to the last save in the save folder (looking it up there).

In fact, there should be a selectable default (start up switch?) to always load only the last save. But of course not exluding the current way to load all saves from a given date if so desired.




Rainer -> RE: Combat Reporter Beta (5/4/2010 5:32:17 PM)

combatreport 1.0 - b1.01

quote:

1) Does it run on XP?


Yes, it does (WinXP 32 SP3 US version)




bretg80 -> RE: Combat Reporter Beta (5/4/2010 7:38:12 PM)

Thanks for the feedback on this. I will make this change to help with this issue. I also plan to add a browse button to help people with selecting the file location directory.

On my list of To do's.




bretg80 -> RE: Combat Reporter Beta (5/4/2010 7:48:38 PM)

Please use forward slashes in the directory name for the AE diretory. If you use backslashes, you will need to use \\ as this is a java string requirement, so forward slashes are preferred.

ex: E:/Matrix Games/War in the Pacific Admiral's Edition/SAVE - preferred way

or
E:\\Matrix Games\\War in the Pacific Admiral's Edition\\SAVE

If you save with double backslashes it will return with single backslashes and you will have to edit the string the next time you make a change. I will correct this, but if you use forward slahses "/" you don't have to worry.

I have updated the first post to make this clear and I will update the user guide.

Thx,

Bret




bretg80 -> RE: Combat Reporter Beta (5/4/2010 8:08:44 PM)


quote:

ORIGINAL: Mistmatz

Seems to be a nice tool. Is there a way to zoom closer into the map with the next build?


Yes, I have actually restricted the zooming to these two levels because of the included map resolution. The current resolution on the map I included with the Beta version is only 1024 x 768 and gets grainy as you zoom in I can increase the map resolution to full WITP AE resolution and then you can zoom in quite far, but it will take a little longer to load the map during startup. It will also increase the size of the download. I think the current map is 20 MB and will go to 50MB. Not a big issue in size, but it does take about twice the amount of time to startup the app. The good news is that once the program is running there is no additional penalty.

I can also allow the map to zoom out much further as well.

Thoughts from the community?




DarkestHour -> RE: Combat Reporter Beta (5/4/2010 10:58:33 PM)

Good tool. I would be happy to have a bigger download for a bigger map. Used the reporter last night on a few turns. XP OS. The 20 second refresh kept refreshing the reports list displaying just the turn directories so I had to continually open a turn I was going through and select the next detail. I changed the 20 to 120 and the problem disappeared. This was just a quick test of the tool and the only problem I encountered. Very useful. The map links are great.




captskillet -> RE: Combat Reporter Beta (5/4/2010 11:00:31 PM)

Great tool!!!! bigger download for larger more detailed map no problem for me!




bretg80 -> RE: Combat Reporter Beta (5/5/2010 2:55:43 PM)

quote:

ORIGINAL: DarkestHour

Good tool. I would be happy to have a bigger download for a bigger map. Used the reporter last night on a few turns. XP OS. The 20 second refresh kept refreshing the reports list displaying just the turn directories so I had to continually open a turn I was going through and select the next detail. I changed the 20 to 120 and the problem disappeared. This was just a quick test of the tool and the only problem I encountered. Very useful. The map links are great.


Yes, this problem may occur on slower machines because WITPAE actually writes to those files several times while a turn is taking place and CombatReporter (CR) will see the change in the file modification date and refresh the tree. Your solution is the correct one by adding more time to the monitor interval. 120 is 120 seconds or 2 minutes. The only downside to that duration is that you may have to wait for a minute or so after the turn before CR updates. I'll set the default up to 60 and see how that works for everyone. The good news is that you can change it to whatever works best for you. [:)]

Thanks for the feedback.

P.S. not to imply that you have a slow machine [8D]




bretg80 -> RE: Combat Reporter Beta (5/5/2010 3:08:50 PM)

quote:

ORIGINAL: captskillet

Great tool!!!! bigger download for larger more detailed map no problem for me!


When I release the next version of the beta here shortly, I'll include the higher resolution map and let everyone give it a shot. I'll allow zooming all the way out and in and see how everyone likes it. If the feedback is positive, I'll leave it in for the final release.

Thanks for the feedback.

Bret




Page: [1] 2 3 4 5   next >   >>

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
2.929688E-02