Page 6 of 16

RE: Combat Reporter - report monitoring tool

Posted: Wed Apr 06, 2011 4:41 am
by BigDuke66
Thanks but your right it didn't work.

Check out the Alor Star entry, it brings me to Alor not Alor Star.
I guess the problem is that a part of the name also fits to another base, I guess this can get really confusing when we see Port XY or San XY entries as there are a lot bases of with this name scheme.

RE: Combat Reporter - report monitoring tool

Posted: Thu Apr 07, 2011 1:46 am
by bretg80
ORIGINAL: BigDuke66

Thanks but your right it didn't work.

Check out the Alor Star entry, it brings me to Alor not Alor Star.
I guess the problem is that a part of the name also fits to another base, I guess this can get really confusing when we see Port XY or San XY entries as there are a lot bases of with this name scheme.


BigDuke66, I have uploaded 1.04 and thanks to your report file I was able to track down at least 6 bugs (oh and I did fix your issue specifically). Some of which I had not identified in my own report files. There seems to be many permutations that I had not accounted for. I also found a bug in the new hex location display which I hope is correct now.

Let me know and when I hear back from you I'll announce the update to the community. You can use the same link to download it.

Bret

RE: Combat Reporter - report monitoring tool

Posted: Thu Apr 07, 2011 3:03 am
by BigDuke66
So far so good but it looks like the X hex coordinates on map for every unequal line(starting with 5, 7, 9, 11, etc.) are one hex off.
Saigon for example brings us to 60,71 what is correct but on your map Saigon is in 61,71, the lines one below & one above Saigon seem correct but the Saigon line is -1X.
I hope I explained it clear enough.

RE: Combat Reporter - report monitoring tool

Posted: Thu Apr 07, 2011 1:49 pm
by Rainer
So far so good but it looks like the X hex coordinates on map for every unequal line(starting with 5, 7, 9, 11, etc.) are one hex off.
Saigon for example brings us to 60,71 what is correct but on your map Saigon is in 61,71, the lines one below & one above Saigon seem correct but the Saigon line is -1X.
I hope I explained it clear enough.

BigDuke66 is right. I see that too (Makin, Vinh as other examples). The icon is one hex off (to the left).
1.03 does not have that.

RE: Combat Reporter - report monitoring tool

Posted: Fri Apr 08, 2011 1:49 am
by bretg80
Hey guys,

1.041 is published and the hex placement and display error should be fixed. Let me know if you concur. Same location for download.

Bret

RE: Combat Reporter - report monitoring tool

Posted: Fri Apr 08, 2011 2:44 am
by BigDuke66
Yep that's it!
Thanks!

RE: Combat Reporter - report monitoring tool

Posted: Fri Apr 08, 2011 3:14 pm
by Rainer
Looks good [:)]
Thanks.

RE: Combat Reporter - report monitoring tool

Posted: Thu Apr 14, 2011 2:35 am
by bretg80
New 1.05 version fixes the map scrolling. See release notes in first posting. Same location for download.

Bret

RE: Combat Reporter - report monitoring tool

Posted: Thu Apr 14, 2011 3:54 am
by BigDuke66
Thanks!
Could you take a look at the SigIntReport and there at the Radio transmissions?
Seems like he only jumps to locations were hex coordinates stand alone like:
Radio transmissions detected at 99,121.
But when you try:
Radio transmissions detected at Bayombong (80,75).
nothing happens, neither the name nor the hex coordinates make it jump.

RE: Combat Reporter - report monitoring tool

Posted: Fri Apr 15, 2011 12:25 am
by bretg80
Thanks for the feedback BigDuke, you found another parse bug and I have corrected it. Sorry, they keep throwing new challenges at me that I hadn't run into during my testing. Version 1.051 is avail with the fix.

RE: Combat Reporter - report monitoring tool

Posted: Fri Apr 15, 2011 1:45 am
by BigDuke66
My pleasure, but that latest version didn't do the trick.

***
Exception in thread "AWT-EventQueue-0" java.lang.StringIndexOutOfBoundsException
: String index out of range: 0
at java.lang.String.charAt(Unknown Source)
at sun.reflect.GeneratedMethodAccessor54.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.AbstractCallSite.call(AbstractCa
llSite.java:124)
at com.bret.witpae.CombatReport$1.mousePressed(CombatReport.groovy:131)
at java.awt.AWTEventMulticaster.mousePressed(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
***


RE: Combat Reporter Beta

Posted: Fri Apr 15, 2011 7:06 pm
by mikkey
excellent work, thanks Bret!

RE: Combat Reporter - report monitoring tool

Posted: Fri Apr 15, 2011 7:33 pm
by Rainer
BigDuke, 1.051 does not crash on my system.
Maybe a Java issue with your setup?

RE: Combat Reporter - report monitoring tool

Posted: Fri Apr 15, 2011 10:18 pm
by BigDuke66
Just updated from 23 to 24 but still:


I:\WitP Combat Reporter 1.051>java -splash:UV1024.jpg -Xmx1024m -jar combatRepor
t.jar
Exception in thread "AWT-EventQueue-0" java.lang.StringIndexOutOfBoundsException
: String index out of range: 0
at java.lang.String.charAt(Unknown Source)
at sun.reflect.GeneratedMethodAccessor54.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.AbstractCallSite.call(AbstractCa
llSite.java:124)
at com.bret.witpae.CombatReport$1.mousePressed(CombatReport.groovy:131)
at java.awt.AWTEventMulticaster.mousePressed(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
at java.awt.EventQueue.access$000(Unknown Source)
at java.awt.EventQueue$1.run(Unknown Source)
at java.awt.EventQueue$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
Source)
at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
Source)
at java.awt.EventQueue$2.run(Unknown Source)
at java.awt.EventQueue$2.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)

RE: Combat Reporter - report monitoring tool

Posted: Fri Apr 15, 2011 10:25 pm
by bretg80
BigDuke, can you send me the report file. There may be something in one of the strings I'm not accounting for. You are still getting a parse error I see.

Thanks,

Bret

RE: Combat Reporter - report monitoring tool

Posted: Fri Apr 15, 2011 10:52 pm
by BigDuke66
Here the sigint file.

RE: Combat Reporter - report monitoring tool

Posted: Sat Apr 16, 2011 4:06 am
by Roger Neilson II
Just installed the latest version of this tool, running fine except the map simply says "loading Map.....' and never does.

Games patched up to latest official and latest beta - same happening with both - installed as two separate Combat Reporter installs one for each game.

Roger

RE: Combat Reporter - report monitoring tool

Posted: Sat Apr 16, 2011 9:48 pm
by bretg80
Hey Roger,

Sounds like it is not pointing to the proper AE directory. Take a look at the preferences. Maybe the default overrode yours.

Bret

RE: Combat Reporter - report monitoring tool

Posted: Sat Apr 16, 2011 9:59 pm
by bretg80
BigDuke,

I tried the file you sent me and it works fine on 1.051, no errors that I could see. All locations move to the correct spot on the map. Are you sure you have latest version. Please look at the info/about menu and double check.

You sent me sigint file, could it be a different file that is causing problems?

Bret



RE: Combat Reporter - report monitoring tool

Posted: Sat Apr 16, 2011 10:16 pm
by BigDuke66
Sorry I should ahve been more precise, at the moment it's only the Radio messages in the SigInt file that make this problem and of those only the ones with name & coordinates in brackets like this Bayombong (80,75), the others with coordinates only work fine.