[freespace2] audio/video out of sync?

[Taylor Richards]

In src/freespace2/freespace.cpp look for this line "int Framerate_cap =
120;" and change the 120 to something like 500.  If that works I'm going
to be pissed ;-)  It did the trick for me but I just woke up and may be
dreaming still.  Jacek or someone else with a V3 check this out as
well.  I had tried this before to help the V3 and it didn't work but
make sure that's still the case.  If this works then I'll just remove
the framerate cap completely if it looks like it doesn't help anymore.


Taylor


On Sun, 2003-04-13 at 11:15, Andreas wrote:
> Well, I've been doing some tests with current nvidia driver and the 
> venerable 3123 version, and I get the same problem.
> 
> What I observe is that whenever the framerate gets to 120, the slowdown
> happens, like "bullet time" in the matrix movie :)
> 
> In a more complex battle or scene, the framerate is lower and I can then play
> normally, without this "special effect". There has got to be some timing problem,
> maybe the game designers didn't envision this game being played at frame rates
> higher than 100 :)
> 
> That would also explain why I don't always get this problem at 1024x768, the FPS
> is lower, but, in some missions (like the one I'm in now) it does get to 120fps,
> and it then slows down.  To get regular time at 120fps, I have to use SHIFT-. to
> "accelerate" time to x2.
> 
> This is a funny problem, the higher the FPS, the slower the game gets :)
> 
> 
> On Thu, Apr 10, 2003 at 09:03:43PM -0300, Andreas wrote:
> > On Wed, Apr 09, 2003 at 08:26:55PM -0400, Taylor Richards wrote:
> > > If you do go back to an older nvidia driver release please let us know
> > > if it fixes the problem.  I'm going to keep my current drivers with the
> > 
> > Go figure, I just fired the game up and got no more slowdowns, I'm still
> > using Nvidia's 4349 driver. I even changed back to 1024x768, but it's
> > still working flawlessy. Maybe it's the mission I'm on.
> > 
> > Will keep playing, and if I ever see this slowdown again, I'll switch
> > back to the 3123 drivers to see if that fixes it.
-- 
Taylor Richards <mtrs at bellsouth.net>