Blitter speed in "cookie cut words per frame" ? - Page 2

roondar · 16 October 2020, 15:07

Yeah the jsfiddle is still awesome

I lowered my ballpark figures (which assumed the 3rd buffer draw/restore method) a bit from the 63 it gave to allow for setting up the Blitter with the CPU. Might even have been a touch optimistic, perhaps 50-55 would be a better range.

AnimaInCorpore · 16 October 2020, 19:54

Quote:

Originally Posted by roondar

Yeah the jsfiddle is still awesome

I lowered my ballpark figures (which assumed the 3rd buffer draw/restore method) a bit from the 63 it gave to allow for setting up the Blitter with the CPU. Might even have been a touch optimistic, perhaps 50-55 would be a better range.

The main credit goes to you! Thanks for your work on this.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Weird Issue - Running "Nemiac IV: Director's Cut" from Workbench 3.1	DamienD	support.Other	7	27 April 2018 16:39
Blizzard 1230 IV "Do Not Cut"	esel	support.Hardware	2	16 July 2015 18:09
Single-frame "recorder" emulation?	LocalH	request.UAE Wishlist	2	19 March 2015 18:49
One "hole" in each scan line to turn off blitter nasty?	mc6809e	Coders. Asm / Hardware	1	03 July 2012 12:12
Propper speed request when recording with "Disable frame rate" turned on.	Ironclaw	request.UAE Wishlist	9	02 August 2006 07:21

16 October 2020, 15:07	#21
roondar Registered User Join Date: Jul 2015 Location: The Netherlands Posts: 3,409	Yeah the jsfiddle is still awesome I lowered my ballpark figures (which assumed the 3rd buffer draw/restore method) a bit from the 63 it gave to allow for setting up the Blitter with the CPU. Might even have been a touch optimistic, perhaps 50-55 would be a better range.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)