Atheory's Project: PzB-Normandy Campaign

[berto]

Apart from the unresolved mystery why on your end your setup is attempting file reads while they don't happen here (must be due to some difference in our two data sets?) ...


Don't rule out file system or hard disk corruption.  Several years back, we had a strange case like this where the player suffered from some mysterious low-level file/disk corruption.  We had to provide him with a special Graphics folder download to work around his difficulties.

Before you get too far, consider having Windows scan your disk for file system errors.  Beyond that, try to do a BIOS-level scan of your disk for hardware errors.  Either wouldn't hurt.

Is your video RAM perhaps insufficient?  Such that the game engine is throttled when attempting too many .bmp file reads?

Again, these are just guesses.

Good luck.

[Ricky B]

At the highlighted lines, note the 50 second gap between log entries.  See how slowly things are logged thereafter.

It is curious also to see this at the tail end of your pbedit.log:

2020-08-25 13:14:51 pbedit.exe: [INFO ID 1] in Dib:ib(), opening American/Units/M-8 HMC-.bmp for reading
2020-08-25 13:14:52 pbedit.exe: [INFO ID 1] in Dib:ib(), opening American/Units/M-8 HMC-.bmp for reading
2020-08-25 13:14:54 pbedit.exe: [INFO ID 1] in Dib:ib(), opening American/Units/M-8 HMC-.bmp for reading

Why is the program attempting, attempting, and attempting again to open for reading that one file?  I couldn't say, because on my end, no such attempt (file read) is made.

We don't have an explanation why your data, and log entries, differ from mine.  Without being able to reproduce your file load sequence, I am left to guess what your difficulties might be.  <shrug>

Ugh, I lost my reply Berto, sorry. I took the gap in times to be the units being added to the scenario, thus the gap. This last unit, for example, is not in it, but assume it would show in the log when he added it. And I thought it is then failing on adding this unit in for whatever reason.

That is my guess though, not knowing low the log exactly works.

And I wondered if somehow the odd naming with the - at the end of the unit name is breaking things? I know they don't matter in the middle of the unit name, but maybe don't work right at the end?

Rick

[Ocito80]

I will try a scan. I also sent a request to jts helpdesk to get the download. I will install a fresh copy on my main drive and see what happens. I have all my PzC downloads saved, no clue where I put the PzB game though, frustrates me.

Anyway, cheers.

[berto]

At the highlighted lines, note the 50 second gap between log entries.  See how slowly things are logged thereafter.

It is curious also to see this at the tail end of your pbedit.log:

2020-08-25 13:14:51 pbedit.exe: [INFO ID 1] in Dib:ib(), opening American/Units/M-8 HMC-.bmp for reading
2020-08-25 13:14:52 pbedit.exe: [INFO ID 1] in Dib:ib(), opening American/Units/M-8 HMC-.bmp for reading
2020-08-25 13:14:54 pbedit.exe: [INFO ID 1] in Dib:ib(), opening American/Units/M-8 HMC-.bmp for reading

Why is the program attempting, attempting, and attempting again to open for reading that one file?  I couldn't say, because on my end, no such attempt (file read) is made.

We don't have an explanation why your data, and log entries, differ from mine.  Without being able to reproduce your file load sequence, I am left to guess what your difficulties might be.  <shrug>

Ugh, I lost my reply Berto, sorry. I took the gap in times to be the units being added to the scenario, thus the gap. This last unit, for example, is not in it, but assume it would show in the log when he added it. And I thought it is then failing on adding this unit in for whatever reason.

That is my guess though, not knowing low the log exactly works.

[Yes, I hadn't thought of that.  D'oh!  Indeed, those likely log his ongoing unit additions.  That would easily explain the time gaps.]

And I wondered if somehow the odd naming with the - at the end of the unit name is breaking things? I know they don't matter in the middle of the unit name, but maybe don't work right at the end?

[Something to consider, yes.]

[Ocito80]

At the highlighted lines, note the 50 second gap between log entries.  See how slowly things are logged thereafter.

It is curious also to see this at the tail end of your pbedit.log:

2020-08-25 13:14:51 pbedit.exe: [INFO ID 1] in Dib:ib(), opening American/Units/M-8 HMC-.bmp for reading
2020-08-25 13:14:52 pbedit.exe: [INFO ID 1] in Dib:ib(), opening American/Units/M-8 HMC-.bmp for reading
2020-08-25 13:14:54 pbedit.exe: [INFO ID 1] in Dib:ib(), opening American/Units/M-8 HMC-.bmp for reading

Why is the program attempting, attempting, and attempting again to open for reading that one file?  I couldn't say, because on my end, no such attempt (file read) is made.

We don't have an explanation why your data, and log entries, differ from mine.  Without being able to reproduce your file load sequence, I am left to guess what your difficulties might be.  <shrug>

Ugh, I lost my reply Berto, sorry. I took the gap in times to be the units being added to the scenario, thus the gap. This last unit, for example, is not in it, but assume it would show in the log when he added it. And I thought it is then failing on adding this unit in for whatever reason.

That is my guess though, not knowing low the log exactly works.

And I wondered if somehow the odd naming with the - at the end of the unit name is breaking things? I know they don't matter in the middle of the unit name, but maybe don't work right at the end?

Rick

You are correct, it is the placement of units on the map.

I don't think its the name. Those units listed above are when i was placing the 3rd armored division. In another attempt, I didn't place them, and started on the 43rd Wessex division and ran into the same issue.

[berto]

Yes, the extra entries are due to newly placing units in the scenario.  

And right, there is no problem with the name.  Some recent log entries from my ongoing test run:

...
2020-08-25 17:07:45 pbedit.exe: [INFO ID 1] in Dib:ib(), opening Luftwaffe/Units_50/Obst Teuffel.bmp for reading
2020-08-25 17:07:45 pbedit.exe: [INFO ID 1] in Dib:ib(), opening Luftwaffe/Units_100/Obst Teuffel.bmp for reading
2020-08-25 17:09:53 pbedit.exe: [INFO ID 1] in Dib:ib(), opening American/Units/M-8 HMC-.bmp for reading
2020-08-25 17:09:53 pbedit.exe: [INFO ID 1] in Dib:ib(), opening American/Units_100 - NATO/M-8 HMC-.bmp for reading
2020-08-25 17:09:53 pbedit.exe: [INFO ID 1] in Dib:ib(), opening American/Units_50/M-8 HMC-.bmp for reading
2020-08-25 17:09:53 pbedit.exe: [INFO ID 1] in Dib:ib(), opening American/Units_100/M-8 HMC-.bmp for reading
2020-08-25 17:09:57 pbedit.exe: [INFO ID 1] in Dib:ib(), opening American/Units/US HQ Recon Bn (mot).bmp for reading
2020-08-25 17:09:57 pbedit.exe: [INFO ID 1] in Dib:ib(), opening American/Units_100 - NATO/US HQ Recon Bn (mot).bmp for reading
2020-08-25 17:09:57 pbedit.exe: [INFO ID 1] in Dib:ib(), opening American/Units_50/US HQ Recon Bn (mot).bmp for reading
2020-08-25 17:09:57 pbedit.exe: [INFO ID 1] in Dib:ib(), opening American/Units_100/US HQ Recon Bn (mot).bmp for reading
2020-08-25 17:11:02 pbedit.exe: [INFO ID 1] in Dib:ib(), opening American/Units/US Treadway Bridge (mot).bmp for reading
2020-08-25 17:11:02 pbedit.exe: [INFO ID 1] in Dib:ib(), opening American/Units_100 - NATO/US Treadway Bridge (mot).bmp for reading
2020-08-25 17:11:02 pbedit.exe: [INFO ID 1] in Dib:ib(), opening American/Units_50/US Treadway Bridge (mot).bmp for reading
2020-08-25 17:11:02 pbedit.exe: [INFO ID 1] in Dib:ib(), opening American/Units_100/US Treadway Bridge (mot).bmp for reading

No slowdowns etc. from file reading those BMPs.

[berto]

I don't think its the name. Those units listed above are when i was placing the 3rd armored division. In another attempt, I didn't place them, and started on the 43rd Wessex division and ran into the same issue.

Are you perhaps constrained by inadequate video RAM?

[Ocito80]

I wish it was that simple, but no.

[berto]

When you next try this, at the point of lock-up, please launch Task Manager to display real-time CPU etc. usage, sorted by CPU usage, then use the Snipping Tool to capture a screenshot.  Post the screenshot here.

Also capture and post a screenshot sorting on GPU usage.

[Ocito80]

Not sure the Screen shots are necessary. But its easy enough to get pbedit to lock up. I looked at the CPU usage right away. It doesn't rise above 3%, GPU never above 2% and my memory usage is never above 28% (out of 32gig)

I close the program and my gpu spikes to 8%, then settles.