by Guest » Sat Nov 20, 2010 10:26 am
I think there's more to this than meets the eye.
Every windows source port outputting 35fps does exhibit some degree of stuttering at 70khz, because normally it really isn't a perfect 70khz, and here's where it gets interesting. In other ports, said stuttering occurs every few seconds, however, in ZDoom we're talking about once per second.
In order to circumvent the 69.8-70.2 problem, I came up with a custom timing which's exactly 70.000000000000000khz (yes, that's 15 0's after 70.), and at this degree of precision, the stuttering is effectively gone as long as vsync is on and framerate stays a solid 35.
In the case of prBoom+ and Chocolate Doom, it works flawlessly, no more stuttering, it simply does not happen anymore. However, ZDoom (and also Eternity, just for the record) continue to stutter bad.
Basically stuttering can be successfully suppressed in other ports so it has to be something ZDoom isn't doing efficiently enough.
I think there's more to this than meets the eye.
Every windows source port outputting 35fps does exhibit some degree of stuttering at 70khz, because normally it really isn't a perfect 70khz, and here's where it gets interesting. In other ports, said stuttering occurs every few seconds, however, in ZDoom we're talking about once per second.
In order to circumvent the 69.8-70.2 problem, I came up with a custom timing which's exactly 70.000000000000000khz (yes, that's 15 0's after 70.), and at this degree of precision, the stuttering is effectively gone as long as vsync is on and framerate stays a solid 35.
In the case of prBoom+ and Chocolate Doom, it works flawlessly, no more stuttering, it simply does not happen anymore. However, ZDoom (and also Eternity, just for the record) continue to stutter bad.
Basically stuttering can be successfully suppressed in other ports so it has to be something ZDoom isn't doing efficiently enough.