Matrix Games Forums

Maybe the term shipped in was not right. I am toaking about the amount that just shows up each day.
The amount shown here for the United States I am referring to are the 6000 oil and 3900 resources.
These do not show up as part of production so the numbers look wrong.

Good point Nomad ... I'll get to it fixing that.

Ny59 ... would be nice wouldn't it. The problem is that some planes are used by different services. Aircraft are not assigned to nationality, air groups are... so there will be problems doing this (but will think about a work around)

Local Yokel ... the air production screen will be fixed completely next release (I hope). As for the LCU pop up, I've never had a problem ... will do some testing ...

Damien and Floyd, I just want to thank you both for all your work on this tool, and to congratulate you for producing such a usefull tool! [&o]
 
I've been admiring from afar for a long time now, and finally installed 1.4.  Just browsing through the tool to see what it's features are, I've found some oil and resources hidden at bases I rarely check, and found several replacement issues that I need to address.  I hope you guys are learning and having as much fun with this thing as we all are using it!  [8D]

Thanks Mike (USS A),
Floyd and I are working hard to get a new release out with fixes and suggestions in place fairly soon[;)]

I fly home (Brisbane) tonight for the family festivities over Xmas etc (I live in Pusan, Sth Korea). Anyway have a good weekend guys and I'll pop in to update in a few days / today if there are other issues.

I'll leave you in the hands of my much more capable partner in "code".

Cheers
Damian

ORIGINAL: Local Yokel
Tracker continues to be invaluable, particularly since I keep finding new nuggets that I'd not previously noticed. I do, however, have a couple of minor glitches. One is that I'm not seeing any grand totals (ID 250) in the Air Production Overview tab. The other is that one of the child windows opened by clicking a button on the main form correctly presents a drilled-down display of information a few times then ceases to so so. I think it's in LCU history, but will need to check. I assume that the code has to fetch data from the database afresh in order to generate these subordinate displays - could it be that the fetch doesn't working correctly after it is invoked a few times?

I've not seen that, but when (if) it stops working, are there any Java error messages in the console window?

And yes, each time you ask for history, we fetch information from the database, as keeping it all in memory is wasteful, time-consuming, and sure to cause the JVM to run out of memory...

Air leader problems on the Air Group screen.

A considerable number off active air units are showing an 'unknown leader' but not in the game.
Changing the leader makes no difference. I'm also getting some java errors when I load a new turn but I've closed the screen screen my mistake so i'll post the it next turn.

I wonder Chris ... can you check and see whether it is a pilot from the Sqd that has assumed command or whether it is a "named" leader ... we are trying to get it right (and I doubt it is a fighter jock in command ... )

Maybe there is a switch that Floyd and I are missing here / the leaders expand like the pilots ? I'd have to do more testing ... which is all I seem to do these days... grumble grumble...[;)][:D][;)]

Most of the errors associated with loading turns comes from having a non-static window open when you are loading, but please post the results.

Thanks again
Damian

ORIGINAL: n01487477

I wonder Chris ... can you check and see whether it is a pilot from the Sqd that has assumed command or whether it is a "named" leader ... we are trying to get it right (and I doubt it is a fighter jock in command ... )

Maybe there is a switch that Floyd and I are missing here / the leaders expand like the pilots ? I'd have to do more testing ... which is all I seem to do these days... grumble grumble...[;)][:D][;)]

Thanks again
Damian

Both the old and new leaders were named leaders. In the jpg the one highlighted is the old one while Finley N (five down) is the new leader.

ORIGINAL: n01487477

Most of the errors associated with loading turns comes from having a non-static window open when you are loading, but please post the results.

Thanks again
Damian

Loading error. What do you mean by non-static window?

More about leader problems.  Nether Farmer nor Finley are listed in the leader screen.  I've checked another unit with 'unknown leader' and that one isn't in the list of leaders either.

ORIGINAL: floydg

ORIGINAL: Local Yokel
Tracker continues to be invaluable, particularly since I keep finding new nuggets that I'd not previously noticed. I do, however, have a couple of minor glitches. One is that I'm not seeing any grand totals (ID 250) in the Air Production Overview tab. The other is that one of the child windows opened by clicking a button on the main form correctly presents a drilled-down display of information a few times then ceases to so so. I think it's in LCU history, but will need to check. I assume that the code has to fetch data from the database afresh in order to generate these subordinate displays - could it be that the fetch doesn't working correctly after it is invoked a few times?

I've not seen that, but when (if) it stops working, are there any Java error messages in the console window?

And yes, each time you ask for history, we fetch information from the database, as keeping it all in memory is wasteful, time-consuming, and sure to cause the JVM to run out of memory...

OK, managed to trigger this in Airgroups and Pilots, Airgroups tab when clicking the 'History' button:

"C:\Games\WitP-CHS\NewTracker>java -jar "WitPTracker.jar"
Exception occurred during event dispatching:
java.lang.OutOfMemoryError: Java heap space
at java.awt.image.DataBufferInt.<init>(Unknown Source)
at java.awt.image.Raster.createPackedRaster(Unknown Source)
at java.awt.image.DirectColorModel.createCompatibleWritableRaster(Unknown Source)
at sun.awt.image.SunVolatileImage.getBackupImage(Unknown Source)
at sun.awt.image.VolatileSurfaceManager.getBackupSurface(Unknown Source)

at sun.awt.image.VolatileSurfaceManager.initialize(Unknown Source)
at sun.awt.image.SunVolatileImage.<init>(Unknown Source)
at sun.awt.image.SunVolatileImage.<init>(Unknown Source)
at sun.awt.image.SunVolatileImage.<init>(Unknown Source)
at sun.awt.image.SunVolatileImage.<init>(Unknown Source)
at sun.awt.windows.WComponentPeer.createVolatileImage(Unknown Source)
at java.awt.Component.createVolatileImage(Unknown Source)
at java.awt.Component$BltBufferStrategy.createBackBuffers(Unknown Source)
at java.awt.Component$BltBufferStrategy.<init>(Unknown Source)
at java.awt.Component$BltSubRegionBufferStrategy.<init>(Unknown Source)
at java.awt.Component.createBufferStrategy(Unknown Source)
at java.awt.Window.createBufferStrategy(Unknown Source)
at javax.swing.BufferStrategyPaintManager$BufferInfo.createBufferStrategy(Unknown Source)
at javax.swing.BufferStrategyPaintManager$BufferInfo.createBufferStrategy(Unknown Source)
at javax.swing.BufferStrategyPaintManager$BufferInfo.getBufferStrategy(Unknown Source)
at javax.swing.BufferStrategyPaintManager.prepare(Unknown Source)
at javax.swing.BufferStrategyPaintManager.paint(Unknown Source)
at javax.swing.RepaintManager.paint(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at java.awt.GraphicsCallback$PaintCallback.run(Unknown Source)
at sun.awt.SunGraphicsCallback.runOneComponent(Unknown Source)
at sun.awt.SunGraphicsCallback.runComponents(Unknown Source)
at java.awt.Container.paint(Unknown Source)
at javax.swing.RepaintManager.paintDirtyRegions(Unknown Source)
at javax.swing.RepaintManager.paintDirtyRegions(Unknown Source)
at javax.swing.RepaintManager.seqPaintDirtyRegions(Unknown Source)
at javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(Unknown Source)"

The newly spawned window completely fails to paint its internal canvas: all you see is whatever happens to be next below it in the Z-order - though the new window's borders display correctly, including the 'close window' control in top r/h corner, which correctly functions to close the new window.

HTH.

ORIGINAL: Chris H

More about leader problems.  Nether Farmer nor Finley are listed in the leader screen.  I've checked another unit with 'unknown leader' and that one isn't in the list of leaders either.

Okay, it must be that we're not reading the leader in for some reason. Can you send me a save file and the witptracker.properties file and I'll try to find these guys and why they're not being read in.

Floyd

ORIGINAL: Chris H

ORIGINAL: n01487477

Most of the errors associated with loading turns comes from having a non-static window open when you are loading, but please post the results.

Thanks again
Damian

Loading error. What do you mean by non-static window?

This happens when you load a new turn and do something to a window that contains information which changes from turn to turn ("non-static"). I was being fancy in the programming and made the turn loading a background task, so the screens can still be used when the loading is going on -- not such a great idea. These errors are harmless and once the turn loads, things should function fine.

ORIGINAL: Local Yokel

ORIGINAL: floydg

ORIGINAL: Local Yokel
Tracker continues to be invaluable, particularly since I keep finding new nuggets that I'd not previously noticed. I do, however, have a couple of minor glitches. One is that I'm not seeing any grand totals (ID 250) in the Air Production Overview tab. The other is that one of the child windows opened by clicking a button on the main form correctly presents a drilled-down display of information a few times then ceases to so so. I think it's in LCU history, but will need to check. I assume that the code has to fetch data from the database afresh in order to generate these subordinate displays - could it be that the fetch doesn't working correctly after it is invoked a few times?

I've not seen that, but when (if) it stops working, are there any Java error messages in the console window?

And yes, each time you ask for history, we fetch information from the database, as keeping it all in memory is wasteful, time-consuming, and sure to cause the JVM to run out of memory...

OK, managed to trigger this in Airgroups and Pilots, Airgroups tab when clicking the 'History' button:

"C:\Games\WitP-CHS\NewTracker>java -jar "WitPTracker.jar"
Exception occurred during event dispatching:
java.lang.OutOfMemoryError: Java heap space
at java.awt.image.DataBufferInt.<init>(Unknown Source)
at java.awt.image.Raster.createPackedRaster(Unknown Source)
at java.awt.image.DirectColorModel.createCompatibleWritableRaster(Unknown Source)
at sun.awt.image.SunVolatileImage.getBackupImage(Unknown Source)
at sun.awt.image.VolatileSurfaceManager.getBackupSurface(Unknown Source)

at sun.awt.image.VolatileSurfaceManager.initialize(Unknown Source)
at sun.awt.image.SunVolatileImage.<init>(Unknown Source)
at sun.awt.image.SunVolatileImage.<init>(Unknown Source)
at sun.awt.image.SunVolatileImage.<init>(Unknown Source)
at sun.awt.image.SunVolatileImage.<init>(Unknown Source)
at sun.awt.windows.WComponentPeer.createVolatileImage(Unknown Source)
at java.awt.Component.createVolatileImage(Unknown Source)
at java.awt.Component$BltBufferStrategy.createBackBuffers(Unknown Source)
at java.awt.Component$BltBufferStrategy.<init>(Unknown Source)
at java.awt.Component$BltSubRegionBufferStrategy.<init>(Unknown Source)
at java.awt.Component.createBufferStrategy(Unknown Source)
at java.awt.Window.createBufferStrategy(Unknown Source)
at javax.swing.BufferStrategyPaintManager$BufferInfo.createBufferStrategy(Unknown Source)
at javax.swing.BufferStrategyPaintManager$BufferInfo.createBufferStrategy(Unknown Source)
at javax.swing.BufferStrategyPaintManager$BufferInfo.getBufferStrategy(Unknown Source)
at javax.swing.BufferStrategyPaintManager.prepare(Unknown Source)
at javax.swing.BufferStrategyPaintManager.paint(Unknown Source)
at javax.swing.RepaintManager.paint(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at java.awt.GraphicsCallback$PaintCallback.run(Unknown Source)
at sun.awt.SunGraphicsCallback.runOneComponent(Unknown Source)
at sun.awt.SunGraphicsCallback.runComponents(Unknown Source)
at java.awt.Container.paint(Unknown Source)
at javax.swing.RepaintManager.paintDirtyRegions(Unknown Source)
at javax.swing.RepaintManager.paintDirtyRegions(Unknown Source)
at javax.swing.RepaintManager.seqPaintDirtyRegions(Unknown Source)
at javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(Unknown Source)"

The newly spawned window completely fails to paint its internal canvas: all you see is whatever happens to be next below it in the Z-order - though the new window's borders display correctly, including the 'close window' control in top r/h corner, which correctly functions to close the new window.

HTH.

Looks like your java program ran out of memory. There are ways to run the JVM with more memory allocated, if your PC can handle it.

Floyd, looks like there's no shortage of physical memory on my machine. Will see what I can do get more memory allocated. Many thanks![&o]

<edit> Cool! Increased heap size to 64MB - not only has this cured the air unit history display problem, it's also cured the problem with the air production total not showing. Just gets better and better! [8D] </edit>

ORIGINAL: Local Yokel

Floyd, looks like there's no shortage of physical memory on my machine. Will see what I can do get more memory allocated. Many thanks![&o]

<edit> Cool! Increased heap size to 64MB - not only has this cured the air unit history display problem, it's also cured the problem with the air production total not showing. Just gets better and better! [8D] </edit>

Excellent. Any problem I can fix without changing any code is a great fix... [;)]

ORIGINAL: Local Yokel

Floyd, looks like there's no shortage of physical memory on my machine. Will see what I can do get more memory allocated. Many thanks![&o]

<edit> Cool! Increased heap size to 64MB - not only has this cured the air unit history display problem, it's also cured the problem with the air production total not showing. Just gets better and better! [8D] </edit>

How do you do that?

ORIGINAL: Nomad

ORIGINAL: Local Yokel

Floyd, looks like there's no shortage of physical memory on my machine. Will see what I can do get more memory allocated. Many thanks![&o]

<edit> Cool! Increased heap size to 64MB - not only has this cured the air unit history display problem, it's also cured the problem with the air production total not showing. Just gets better and better! [8D] </edit>

How do you do that?

You do it by adding a switch to the command line in the witptracker.bat file. e.g. -Xms64m will increase the min heap size from 32mb to 64mb. The switch -xmx(size) controls the maximum size of the heap which by default is 128mb. I'm unsure which was changed in this case as changing the lower value shouldn't make any difference and the max is already greater than 64mb?

ORIGINAL: Nomad

ORIGINAL: Local Yokel

Floyd, looks like there's no shortage of physical memory on my machine. Will see what I can do get more memory allocated. Many thanks![&o]

<edit> Cool! Increased heap size to 64MB - not only has this cured the air unit history display problem, it's also cured the problem with the air production total not showing. Just gets better and better! [8D] </edit>

How do you do that?

I googled something like 'java virtual machine heap' and came up with a number of likely hits. The one I worked from was here on devX.com. The relevant tip says this:

"If your Java program requires a large amount of memory, it's possible that the virtual machine will begin to throw OutOfMemoryError instances when attempting to instantiate objects. In some cases, this may be the result of a programming error, but in others, it's simply a result of your program legitimately using more memory than is available. In this latter case, you can increase the "heap size" allocated by the Java Virtual Machine (JVM) by using command line options. When not specified, the heap size defaults to 1 MB, and can increase to as much as 16 MB if your program requires more memory. To set the initial amount of memory allocated for your program, use the -ms option with a 1.1 JVM, and the -Xms option with a 1.2 (also known as Java 2) JVM. To set the maximum amount of memory that can be allocated for your program, use the -mx or -Xmx for Java 1.1 or 1.2, respectively. For example:

java -ms32m -mx128m MyClassName (Java 1.1)
java -Xms32m -Xmx128m MyClassName (Java 1.2 / 2.0)

In each case, the options specify that 32 MB of memory should be allocated initially for the program to run in, and that up to 128 MB may be allocated if necessary.
You should note the presence of the "X" on the Java 1.2 / 2.0 options. It indicates that these are non-standard options that might not function the same way or could even be removed in future JVMs. In the meantime, you may find it necessary to take advantage of these options if your program requires a large amount of memory."

So I set a minimum 64MB heap size for the Tracker VM by changing the syntax of my WitPTracker.bat file so that it reads:

java -Xms64m -jar "WitPTracker.jar"

I've put the bit that sets a 64MB heap size in bold text. Not sure whether that may be over the top, but didn't cause a problem on my machine. I could also have set a maximum heap size using the '-Xmx' notation, but see no reason to do so unless/until its absence causes me a problem.

ORIGINAL: floydg

ORIGINAL: Chris H

More about leader problems.  Nether Farmer nor Finley are listed in the leader screen.  I've checked another unit with 'unknown leader' and that one isn't in the list of leaders either.

Okay, it must be that we're not reading the leader in for some reason. Can you send me a save file and the witptracker.properties file and I'll try to find these guys and why they're not being read in.

Floyd

Lt. Finley has been found. We weren't reading in enough leaders. I think I got 'em now...