Periscope "wash" causes huge lag.

05-20-09, 05:35 PM

I've had this issue ever since I started playing SH3 again a few months ago. Whenever I'm looking out the periscope (attack or obs) and it's either underwater or showing the "wet windshield" effect of the water running down the glass, my frame rate takes a huge hit. As soon as that watery effect stops, my frame rate goes back to normal. It's not a huge deal when the weather is nice as the slowdown only happens once each time I raise the scope, and it only lasts a few seconds. However, when the seas are rough it makes using the scope nearly impossible because every time a wave washes over, the frame rate goes down the toilet.

I tried turning down the graphical options (particle effects) and that didn't help any. My machine is a MacBook Pro with an ATI X1600M video chipset. I'm running under XP using Boot Camp - no emulation. I'm using GWX 3.0. I haven't played the stock version on this machine, so I don't know if it happens in the vanilla game or not.

Anyone else ever seen this problem?

05-20-09, 05:35 PM	#1
Cue-Ball909 Stowaway Posts: n/a Downloads: Uploads:	Periscope "wash" causes huge lag. I've had this issue ever since I started playing SH3 again a few months ago. Whenever I'm looking out the periscope (attack or obs) and it's either underwater or showing the "wet windshield" effect of the water running down the glass, my frame rate takes a huge hit. As soon as that watery effect stops, my frame rate goes back to normal. It's not a huge deal when the weather is nice as the slowdown only happens once each time I raise the scope, and it only lasts a few seconds. However, when the seas are rough it makes using the scope nearly impossible because every time a wave washes over, the frame rate goes down the toilet. I tried turning down the graphical options (particle effects) and that didn't help any. My machine is a MacBook Pro with an ATI X1600M video chipset. I'm running under XP using Boot Camp - no emulation. I'm using GWX 3.0. I haven't played the stock version on this machine, so I don't know if it happens in the vanilla game or not. Anyone else ever seen this problem?