Are you able to leave it running for 5 minutes without doing anything? Then see if the same frame drop occurs.
I've started a couple of games, PAUSED it immediately then let it sit there... 5 minutes later, bang... I started disabling things, but it kept happening, the only way to get rid of it was to render nothing. Even without render3d(), render2d() blows up.
On a 600MHz machine the pathing patch will help some, that stops the UnitUpdater from blowing up, but there is something wrong with the Renderer.
I'd be curious as to how many people experience this problem, and the kind of hardware they're on. Unfortunately I don't think we'd get much of a response... Those who don't experience it probably don't care, those who do come here, post once, don't get an solution in a day and promptly move on...
@Hailstone, if you experience this yourself, check out the PathFinder branch and turn on (uncomment the #defines) GAME_RENDER_PROFILING & LOG_FRAMERATE_DROPS at the top of game.h (the actual FPS that will cause logging is 'hard-coded', change it in Game::tick() if needed).
