English Amiga Board - View Single Post

Toni Wilen · 17 May 2011, 15:58

Moved from beta thread because this isn't going to happen in 2.3.2.

First, any player that uses vblank timing works as designed, playback changes depending on chipset refreshrate (RTG refresh may not be same as chipset refresh on real Amigas either). This is not good enough reason for change

Whole chipset_refresh needs better implementation. Main problem is that it forces all refresh rates to selected value.

Remember that originally it was only meant to slow down or speed up games

Perhaps some kind of multiplier or base unit (clock rate?) is better than direct vertical refresh rate value.

Note that 2 values, one for PAL and one for NTSC is not enough. There are 6 "standard" rates, 312 line PAL, 313 line PAL, interlaced PAL and same for NTSC. (not counting programmed rates but fortunately those aren't used by games or demos that need smooth scrolling)

17 May 2011, 15:58	#5
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,526	Moved from beta thread because this isn't going to happen in 2.3.2. First, any player that uses vblank timing works as designed, playback changes depending on chipset refreshrate (RTG refresh may not be same as chipset refresh on real Amigas either). This is not good enough reason for change Whole chipset_refresh needs better implementation. Main problem is that it forces all refresh rates to selected value. Remember that originally it was only meant to slow down or speed up games Perhaps some kind of multiplier or base unit (clock rate?) is better than direct vertical refresh rate value. Note that 2 values, one for PAL and one for NTSC is not enough. There are 6 "standard" rates, 312 line PAL, 313 line PAL, interlaced PAL and same for NTSC. (not counting programmed rates but fortunately those aren't used by games or demos that need smooth scrolling)