Uploaded April 2011 | Updated November 2026, 3 hours ago
I recently found that Gish stops saturating my CPU when it has been in the background, even after switching it to the foreground again. What's annoying is that my usual high-quality recording necessitates a brief switch. At first I thought it was the recording itself, but just switching to the background and back causes it. This fullscreen QuickTime recording really wants to saturate both cores, but it's still clearly visible. At least in the numbers, as the recording framerate is a joke.
Chronic Logic? Any explanation?
Edit: I thought Gish's physics ran at 50 FPS, or somewhat faster in turbo mode. Apparently the render loop doesn't care if it renders the same frame three times in a row? Well, at least when it renders redundant frames, it's smooth, unlike when it drops frames.
I recently found that Gish stops saturating my CPU when it has been in the background, even after switching it to the foreground again. What's annoying is that my usual high-quality recording necessitates a brief switch. At first I thought it was the recording itself, but just switching to the background and back causes it. This fullscreen QuickTime recording really wants to saturate both cores, but it's still clearly visible. At least in the numbers, as the recording framerate is a joke.
Chronic Logic? Any explanation?
Edit: I thought Gish's physics ran at 50 FPS, or somewhat faster in turbo mode. Apparently the render loop doesn't care if it renders the same frame three times in a row? Well, at least when it renders redundant frames, it's smooth, unlike when it drops frames.










