Frame rate lock?!?!

shadyguido · 6th September 2001, 18:14

the max framerate I can get in 32 bit color 1280x960 is 25 fps when I'm running at 1.2ghz. I overclock to 1.4 ghz, I get the same framerate... BUT HERE'S THE PROBLEM: I underclock to 900mhz and I GET THE SAME FRAMERATE...I didn't set 25fps in the options, so what the hell is going on?! I'm in win2k with 256megs of ram. Geforce 2 PRO running the latest drivers.

Why is my framerate capped at 25? I KNOW i have cpu cycles to spare. Is it a software problem? Geiss, where are you?!!?

-Shady

Krash · 8th September 2001, 05:21

Dunno why it's capped, but you'll find that if you turn off all the overly text, the plugin becomes noticeably faster. If you bring up the fps counter just long enough to read it, and send it away again, you will find the REAL fps you are doing.
Even that is locked though - I can't get it higher than 34fps.

- Krash

feltmate · 8th September 2001, 06:31

Milkdrop simply isn't CPU-limited at those CPU speeds. I'm not sure if the bottleneck is the vidcard's memory or the GPU, but I'm pretty sure the only thing that'll help you is a faster videocard.

geiss · 11th September 2001, 18:42

Yup... 75 / 3 = 25; 75 is probably your monitor's refresh rate, and if MilkDrop didn't wait for a vertical refresh each frame, you'd be getting something between 25 to 37.5 fps (notive 37.5 is 75/2).

Think of it this way: the revolving door opens 75 times a second, and milkdrop is trying to send people through at a rate of 25-37 people per second (these are the frames), but as each one is ready, he or she has to wait up to 1/75th of a second. It turns out that every frame milkdrop renders takes between 2 and 3 1/75ths of a second, so they can only display on the third 1/75th.

You could let them display earlier (without waiting for a vertical refresh), which would give you a slightly higher frame rate, but it would be ugly (lots of page tearing)... and the page tearing is especially noticeable at higher frame rates.

6th September 2001, 18:14	#1
shadyguido Junior Member Join Date: Sep 2001 Location: elysian fields Posts: 1	Frame rate lock?!?! the max framerate I can get in 32 bit color 1280x960 is 25 fps when I'm running at 1.2ghz. I overclock to 1.4 ghz, I get the same framerate... BUT HERE'S THE PROBLEM: I underclock to 900mhz and I GET THE SAME FRAMERATE...I didn't set 25fps in the options, so what the hell is going on?! I'm in win2k with 256megs of ram. Geforce 2 PRO running the latest drivers. Why is my framerate capped at 25? I KNOW i have cpu cycles to spare. Is it a software problem? Geiss, where are you?!!? -Shady

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

8th September 2001, 05:21	#2
Krash Major Dude Join Date: Jun 2001 Location: Sydney, Australia Posts: 977	Dunno why it's capped, but you'll find that if you turn off all the overly text, the plugin becomes noticeably faster. If you bring up the fps counter just long enough to read it, and send it away again, you will find the REAL fps you are doing. Even that is locked though - I can't get it higher than 34fps. - Krash

8th September 2001, 06:31	#3
feltmate Junior Member Join Date: Jul 2001 Posts: 3	Milkdrop simply isn't CPU-limited at those CPU speeds. I'm not sure if the bottleneck is the vidcard's memory or the GPU, but I'm pretty sure the only thing that'll help you is a faster videocard.

11th September 2001, 18:42	#4
geiss Nullsoft Visualization Developer Join Date: May 2001 Posts: 146	Yup... 75 / 3 = 25; 75 is probably your monitor's refresh rate, and if MilkDrop didn't wait for a vertical refresh each frame, you'd be getting something between 25 to 37.5 fps (notive 37.5 is 75/2). Think of it this way: the revolving door opens 75 times a second, and milkdrop is trying to send people through at a rate of 25-37 people per second (these are the frames), but as each one is ready, he or she has to wait up to 1/75th of a second. It turns out that every frame milkdrop renders takes between 2 and 3 1/75ths of a second, so they can only display on the third 1/75th. You could let them display earlier (without waiting for a vertical refresh), which would give you a slightly higher frame rate, but it would be ugly (lots of page tearing)... and the page tearing is especially noticeable at higher frame rates.