FPS problem in TPT

  • Videogamer555
    1st Oct 2012 Member 0 Permalink
    Either the true FPS is 30 (not the reported 60, that is shown in TPT's FPS display), or else it is 60FPS but the R record function is skipping every other frame when it saves the PPM files.

    You see when I convert the PPM to BMP, then use VirtualDub (a well known, bugfree, AVI making freeware) to assemble the BMP files into an AVI file, I notice the resulting AVI file seems to play twice as fast as the simulation in TPT, and the simulation I recorded wasn't even overloading the CPU. It was reporting a full 60FPS, but the resulting video file would (by using this calculation) be running at 120FPS. I checked this in VLC by loading the video file, and checking what it reported the saved FPS in the AVI header showed. It showed that it is in fact a 60FPS AVI file. So I know for certain that the playback is 60FPS.

    This seems to be a bug in TPT.
  • Videogamer555
    3rd Oct 2012 Member 0 Permalink
    Bump. Please respond. This bug needs fixing.
  • Pilihp64
    4th Oct 2012 Developer 0 Permalink

    I can't seem to replicate the issue, it records every single frame.

    Older version of record (before tpt++) there was ctrl-r or something that only recorded every other frame, but I'm pretty sure that is gone now.

    Maybe you lost some pictures in the process, or some other settings are off.... I'm not sure.

  • Videogamer555
    5th Oct 2012 Member 0 Permalink
    Then the FPS counter is to blame, because it indicates running at 60FPS, but the AVI file looks correct when running at 30FPS.
    So apparantly the true Frames Per Second for TPT is 30FPS. Now if you meant Fields Per Second for running it on a CRT TV screen, then yes that FPS would be 60.
  • jacob1
    5th Oct 2012 Developer 0 Permalink
    The FPS counter in tpt is right, if it wasn't, then everyone would notice that it's twice as slow. Maybe there is another problem, or it's just you. I don't know why it would happen, but they could have been lost in converting if you used the wrong settings.