Event camera askew

Mios 4Me · 07-14-19, 09:16 PM

Is there a geographic component to these errors?

I'd been running without issues as long as I stayed out of Empire waters, but after finally being transferred back to Pearl, I'm running into it every patrol now. The oddest part is that I'm running at TC 8100 with no issues until I approach Iwo Jima. Then one or two blinking destroyer-only task forces approach, ones I've come to recognize as harbingers of game instability, either three or four ships, and the game starts lagging badly above 512 TC.

This is coming at the beginning of a new patrol, no kills, no prior encounters, nada. I've done full computer restarts twice but it repeats.

propbeanie · 07-15-19, 06:33 AM

What is your mod list now? There are issues with what I describe as "run-a-way spawns" in a few mods, where a couple of DD Random Generated Groups were supposed to be an anchored destroyer, but the "anchor chain broke", so to speak, and the DD instead circles the "globe" at 5 knots, joined by more and more of its sisters, each spawn cycle. This is what generates the DD-only "Task Groups" that are seen. These will eventually grow too large for the computer system to keep up with, and you will see performance degradation, eventually to the point of a CTD.

Mios 4Me · 07-15-19, 07:26 AM

Zero mods, other than the originally installed Balao systems hacks, and no recent changes other than the transfers to Brissie and then Pearl. No issue on the Brisbane patrols but noticed the askew issue when I hit Hiroshima after a photo mission to Osaka.

I've been very careful regarding the file commands you mentioned earlier; however, the laptop manufacturer thoughtfully pushed an upgrade notification, which I declined, right in the middle of a patrol. I suspect that may have corrupted not only the patrol but the game as well.

If memory serves, the DD issues way back in unmodded 1.3 occurred off the Ryukyus and continued under 1.5 GFO.

Speaking of oddities, what's with the unescorted carrier patrolling the Kii Suido? One doesn't always get credit for its sinking and there may be an association with the problem above as it's virtually assured when encountering the CV.

propbeanie · 07-15-19, 10:46 AM

Unescorted CV (and other capital ships) were not at all uncommon in "home" waters, in other words, close in to shore, as the IJN would transfer ships between bases sometimes, and would rely upon regular local shore patrol vessels to guard them. They were also known to do shakedown cruises in home waters, preparing a vessel for missions, again relying on local patrol vessels for protection - at least until they realized the US subs were actually able to "sneak" into the "home" waters.

My guess with the run away spawns you encountered in GFO, those were probably from using the previous Save folder with the v1.3 files still in it. Even if you do not create a Save, the game writes to the Save folder, and uses the data there to pull most of its information from. Then, as you mention, the interruption from Windows "shelled" you out from the game, and that can lead to corruption in all things in the game, especiall 3D. I was just doing a "test" mission for PhotoTargets I'm doing for FotRSU, and I was also interrupted by Windows 10 update, and lo and behold, the 3D artwork for the shore that I was about 3500 yards off of completely disappeared. All I saw after that was water. If I looked on the NavMap, there was land, still being the same distance from shore - but when I looked through my periscope, there was no land visible. I could still target the PhotoTarget and take a picture, but even the "picture" that goes to the Captain's Log was nothing but open water... very strange, and unfortunately, "normal" game activity. I Saved the scenario, exited the game, came back in and loaded the scenario, and my "land" is back, and the pictures now look fine also - except that one... There is still just open water in it... weird

Mios 4Me · 07-16-19, 01:48 PM

Those are good points, especially in the Inland Sea, though I would have expected one DD on at least routine pilot rescue duty, if not ASW. This is December 1943 and the CV is still cruising solo around the margin of the Pacific. Wish I could find a Yamato as easily.

The 1.3 installation was on the old laptop; the new one started afresh with 1.5, yet I had the TC/destroyer TF/camera askew issues on both. After this career is over, I'll wipe the laptop, reinstall with GFO and the 1945 Balao adjustments, and pay very close attention to the file issues you've so kindly listed. I suspect that's the common thread.

I went back to the end of the previous patrol and started Patrol 20 anew, then passed the Volcano Islands far to the south with no issues before heading to my ECS patrol zone. I'm surprised glitch survived ending Patrol 19 in previous attempts and that a circuitous route may have been the key to avoiding it.

07-15-19, 06:33 AM	#2
propbeanie CTD - it's not just a job Join Date: May 2016 Location: One hour from Music City USA! Posts: 10,116 Downloads: 451 Uploads: 2	What is your mod list now? There are issues with what I describe as "run-a-way spawns" in a few mods, where a couple of DD Random Generated Groups were supposed to be an anchored destroyer, but the "anchor chain broke", so to speak, and the DD instead circles the "globe" at 5 knots, joined by more and more of its sisters, each spawn cycle. This is what generates the DD-only "Task Groups" that are seen. These will eventually grow too large for the computer system to keep up with, and you will see performance degradation, eventually to the point of a CTD. __________________ "...and bollocks to the naysayers" - Jimbuna

07-15-19, 10:46 AM	#4
propbeanie CTD - it's not just a job Join Date: May 2016 Location: One hour from Music City USA! Posts: 10,116 Downloads: 451 Uploads: 2	Unescorted CV (and other capital ships) were not at all uncommon in "home" waters, in other words, close in to shore, as the IJN would transfer ships between bases sometimes, and would rely upon regular local shore patrol vessels to guard them. They were also known to do shakedown cruises in home waters, preparing a vessel for missions, again relying on local patrol vessels for protection - at least until they realized the US subs were actually able to "sneak" into the "home" waters. My guess with the run away spawns you encountered in GFO, those were probably from using the previous Save folder with the v1.3 files still in it. Even if you do not create a Save, the game writes to the Save folder, and uses the data there to pull most of its information from. Then, as you mention, the interruption from Windows "shelled" you out from the game, and that can lead to corruption in all things in the game, especiall 3D. I was just doing a "test" mission for PhotoTargets I'm doing for FotRSU, and I was also interrupted by Windows 10 update, and lo and behold, the 3D artwork for the shore that I was about 3500 yards off of completely disappeared. All I saw after that was water. If I looked on the NavMap, there was land, still being the same distance from shore - but when I looked through my periscope, there was no land visible. I could still target the PhotoTarget and take a picture, but even the "picture" that goes to the Captain's Log was nothing but open water... very strange, and unfortunately, "normal" game activity. I Saved the scenario, exited the game, came back in and loaded the scenario, and my "land" is back, and the pictures now look fine also - except that one... There is still just open water in it... weird __________________ "...and bollocks to the naysayers" - Jimbuna

Thread Tools
Show Printable Version Email this Page
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

07-14-19, 09:16 PM	#1
Mios 4Me Sonar Guy Join Date: Feb 2019 Posts: 394 Downloads: 38 Uploads: 0	Is there a geographic component to these errors? I'd been running without issues as long as I stayed out of Empire waters, but after finally being transferred back to Pearl, I'm running into it every patrol now. The oddest part is that I'm running at TC 8100 with no issues until I approach Iwo Jima. Then one or two blinking destroyer-only task forces approach, ones I've come to recognize as harbingers of game instability, either three or four ships, and the game starts lagging badly above 512 TC. This is coming at the beginning of a new patrol, no kills, no prior encounters, nada. I've done full computer restarts twice but it repeats.

07-15-19, 07:26 AM	#3
Mios 4Me Sonar Guy Join Date: Feb 2019 Posts: 394 Downloads: 38 Uploads: 0	Zero mods, other than the originally installed Balao systems hacks, and no recent changes other than the transfers to Brissie and then Pearl. No issue on the Brisbane patrols but noticed the askew issue when I hit Hiroshima after a photo mission to Osaka. I've been very careful regarding the file commands you mentioned earlier; however, the laptop manufacturer thoughtfully pushed an upgrade notification, which I declined, right in the middle of a patrol. I suspect that may have corrupted not only the patrol but the game as well. If memory serves, the DD issues way back in unmodded 1.3 occurred off the Ryukyus and continued under 1.5 GFO. Speaking of oddities, what's with the unescorted carrier patrolling the Kii Suido? One doesn't always get credit for its sinking and there may be an association with the problem above as it's virtually assured when encountering the CV.

07-16-19, 01:48 PM	#5
Mios 4Me Sonar Guy Join Date: Feb 2019 Posts: 394 Downloads: 38 Uploads: 0	Those are good points, especially in the Inland Sea, though I would have expected one DD on at least routine pilot rescue duty, if not ASW. This is December 1943 and the CV is still cruising solo around the margin of the Pacific. Wish I could find a Yamato as easily. The 1.3 installation was on the old laptop; the new one started afresh with 1.5, yet I had the TC/destroyer TF/camera askew issues on both. After this career is over, I'll wipe the laptop, reinstall with GFO and the 1945 Balao adjustments, and pay very close attention to the file issues you've so kindly listed. I suspect that's the common thread. I went back to the end of the previous patrol and started Patrol 20 anew, then passed the Volcano Islands far to the south with no issues before heading to my ECS patrol zone. I'm surprised glitch survived ending Patrol 19 in previous attempts and that a circuitous route may have been the key to avoiding it.