O.T. Tech Help.

[Grau]

I came here because I believe the people here will understand my problem.

First, Apologies to Niceguy from sgray. I thought there would be a wiki link. Primate state of computer use, see it, click it.

The problem:
WITP no mods fully patched, turns are one day, about January 20, 1943 about 396 turns. No technical problems before this.
Beginning couple of days ago, when I click on the port symbol the ships in port list prints over the map not on the normal background.

I have reloaded and replayed prior saves of two days ago and it does not have the same problem initially, however when the turn is over and save it, the next time I load the saved came it has the same problem.

I'm only doing one turn a day so this is a major problem for me.[&:]

[rtrapasso]

ORIGINAL: Grau

I came here because I believe the people here will understand my problem.

First, Apologies to Niceguy from sgray. I thought there would be a wiki link. Primate state of computer use, see it, click it.

The problem:
WITP no mods fully patched, turns are one day, about January 20, 1943 about 396 turns. No technical problems before this.
Beginning couple of days ago, when I click on the port symbol the ships in port list prints over the map not on the normal background.

I have reloaded and replayed prior saves of two days ago and it does not have the same problem initially, however when the turn is over and save it, the next time I load the saved came it has the same problem.

I'm only doing one turn a day so this is a major problem for me.[&:]

It could be you are running out of memory... reboot, and make sure you do not have any other major programs running (i.e. aside from antivirus, etc), then load WITP, and see if the problem recurs.

If this does not resolve the problem and it is a PBEM, it may be a file got corrupted in transmission.

[wdolson]

That sort of problem isn't really a memory problem, it sounds like a Windows handles problem.  Windows creates a thing called a handle for every object like an image used.  The mouse cursor has a handle, each icon has a handle, etc.

WitP uses a gigantic number of handles.  If the system already has a number allocated, WitP can end up doing weird things with the graphics because it's run out of handles.  This frequently happens if a program has crashed since the computer was last rebooted.  The handles used by the program may not be released and Windows thinks a lot more are in use.

BTW, we did work in AE to drastically reduce the number of handles used so this happens a lot less frequently.

Bill

[rtrapasso]

This frequently happens if a program has crashed since the computer was last rebooted. The handles used by the program may not be released and Windows thinks a lot more are in use.

As i said: reboot! And don't run any other programs (they will use up handle "slots".)

Maybe not memory exactly - but it works the same... the amount of available resources the computer has was exceeded and thus the glitch.