|
|
Post by cdrsubron7 on Sept 27, 2016 18:18:54 GMT
A quick FYI for you pb. I still have the career loaded where I had problems with the DDs. After I get home tonight I will head out and see if the same things happen again. I make note of the exact date and time and try to get an exact Nav map location for you. Till later.
|
|
|
|
Post by propbeanie on Sept 27, 2016 18:27:46 GMT
Sounds good. So your save doesn't corrupt on you? Just lag, and patience, and you get through? I keep thinking that if it was a game bug, that unless there's a mission file coded into the game, that it wouldn't be the same ships so many times. You just can't have a memory location getting overwritten with the same data so often, from what I experienced when doing bad memory allocations as a young programming pup many, many moons ago... the thing gets stuck on destroyers over 9 out of ten times in the reports...
|
|
|
|
Post by cdrsubron7 on Sept 27, 2016 19:01:01 GMT
Sounds good. So your save doesn't corrupt on you? Just lag, and patience, and you get through? I keep thinking that if it was a game bug, that unless there's a mission file coded into the game, that it wouldn't be the same ships so many times. You just can't have a memory location getting overwritten with the same data so often, from what I experienced when doing bad memory allocations as a young programming pup many, many moons ago... the thing gets stuck on destroyers over 9 out of ten times in the reports... Actually the save did become corrupted, I ended up deleting it. But I can start from the beginning of the patrol again and go back to the Luzon Straits and see if it will happen again. I got a feeling that it will happen again. |
|
|
|
Post by cdrsubron7 on Sept 28, 2016 20:29:13 GMT
Sounds good. So your save doesn't corrupt on you? Just lag, and patience, and you get through? I keep thinking that if it was a game bug, that unless there's a mission file coded into the game, that it wouldn't be the same ships so many times. You just can't have a memory location getting overwritten with the same data so often, from what I experienced when doing bad memory allocations as a young programming pup many, many moons ago... the thing gets stuck on destroyers over 9 out of ten times in the reports... Actually the save did become corrupted, I ended up deleting it. But I can start from the beginning of the patrol again and go back to the Luzon Straits and see if it will happen again. I got a feeling that it will happen again. So much for my feelings. That patrol went off as normal. As a matter of fact I've got a nice big fat TF waiting for me when I go back on patrol.  |
|
|
|
Post by propbeanie on Sept 29, 2016 4:22:59 GMT
... and therein lies the rub - getting the incident to repeat. Some of the posts on SubSim, they tried again and got the same thing, but they back came in the same route, same TC, etc. And if my memory serves me correctly, it's only three out of I don't know how many.
What I would like to find out what is, what is the most efficient way to have traffic in the Campaign? Is it easier for the computer to generate and track hundreds of RGGs, with single or multiple ships, all over the place, or is it easier for it to track a "Unit" that might have upwards of two dozen ships following it around, including the "Stop And Go" technique at some harbors.
Which reminds me, I found a thread at SubSim where they discussed what they termed the "Stop and go" technique, where you might have a ship do less than 1 knot, say 0.1 or 0.01, or even slower, at one or more waypoints, especially in harbors, to simulate loading / off-loading of cargo, or fueling, and then when they "drift" to the next waypoint finally, off they go. While they're there, they're "sitting ducks" for the cautiously entrepreneurial skipper... |
|
