WHDLoad choppy

demolition · 03 November 2012, 19:58

Whenever I've tried WHDLoad it always seems to be a little choppy as if there's interrupts happening in the background. James Pond 2 is one example. Is it just a badly made slave perhaps?

This is the same on both my A600 and A1200. If I run the game directly from floppy, everything is as smooth as it is supposed to.

fryguy · 04 November 2012, 01:56

Do you have any fastmem? Are you using the preload tooltype?

demolition · 04 November 2012, 02:45

Quote:

Originally Posted by fryguy

Do you have any fastmem? Are you using the preload tooltype?

This happens with either an A600 with ACA620 (11MB fastmem) and an A1200 with ACA1232 (127MB fastmem).
And yes, preload was specified as tooltype.

AmmoJammo · 04 November 2012, 03:56

I have the same thing happen running Flimbos Quest on my A500 (havent tried many games), either at the stock 7mhz, or running the 030 at 36Mhz, 8meg fast ram, 1meg chip.

fryguy · 04 November 2012, 13:22

I believe WHDLoad works best with Blizzard cards. But you can try the following tool types: NOAUTOVEC and NOMMU

They made WHDLoad work better on my MBX1230.

demolition · 04 November 2012, 14:25

Quote:

Originally Posted by fryguy

I believe WHDLoad works best with Blizzard cards. But you can try the following tool types: NOAUTOVEC and NOMMU

I'm already using Noautovec in the prefs file. As I understand it, MMU is disabled as default on 030 cards and I've tried enabling it with MMU in the prefs file, but it's not really changing anything.

Retro-Nerd · 04 November 2012, 19:36

It has nothing to do with a specific turbo card maker. WHDLoad works also perfectly fine on M-Tec or the newer ACA cards. Wait if Wepl could tell you more.

demolition · 04 November 2012, 20:01

Quote:

Originally Posted by Retro-Nerd

It has nothing to do with a specific turbo card maker. WHDLoad works also perfectly fine on M-Tec or the newer ACA cards. Wait if Wepl could tell you more.

Shouldn't most WHDLoad'ed old single-disk games also run fine on a plain 68k CPU? When I try James Pond 2 for example on my plain A600 with 2MB chip + 2MB SRAM i get the same micro-stuttering, and nothing if I boot it from disk on the same machine.

StingRay · 04 November 2012, 20:10

This is because of the added blitter waits. It has nothing to do with WHDLoad, the slaves need to be updated to allow the user to disable the blitter waits.

Retro-Nerd · 04 November 2012, 20:10

They should. What happens if you try other single disk games like Turrican or Hybris without S-Ram card. The WHDLoad versions run without fastmem.

Quote:

- Lots of blitter waits inserted

Or maybe this could a problem in James Pond 2 on 68k machines.

Edit: Stingy was faster.

Abaddon · 05 November 2012, 02:17

Give the attached slave a go. Set Custom2=1 to skip patching the blitter waits

manic23 · 07 May 2013, 20:52

I know this is an old thread, but does this slave work with the AGA or ECS versions?

StingRay · 08 May 2013, 07:13

manic23 · 08 May 2013, 08:45

Yes but that install has separate slaves for the ECS and AGA versions, I was just asking if the slave that Abaddon posted on this thread was ecs or AGA

Wepl · 08 May 2013, 09:02

in regard to the filesize it must be the OCS slave, also the AGA slave has probably no (less) blitter waits

Abaddon · 08 May 2013, 13:22

The attached slave is for the ecs version. The source for the AGA version was not included in the install package. This was just a quick fix to see if the blitter waits were the culprit making it choppy. Since there was no response the install package never got updated.

manic23 · 08 May 2013, 13:25

OK thanks for clarifying, I will test over the weekend and report back.

03 November 2012, 19:58	#1
demolition Unregistered User Join Date: Sep 2012 Location: Copenhagen / DK Age: 43 Posts: 4,190	WHDLoad choppy Whenever I've tried WHDLoad it always seems to be a little choppy as if there's interrupts happening in the background. James Pond 2 is one example. Is it just a badly made slave perhaps? This is the same on both my A600 and A1200. If I run the game directly from floppy, everything is as smooth as it is supposed to.

08 May 2013, 07:13	#13
StingRay move.l #$c0ff33,throat Join Date: Dec 2005 Location: Berlin/Joymoney Posts: 6,863	According to the readme it supports the ECS and AGA version ("That install applies to "James Pond 2 ECS/AGA" © 1991-93 Millennium - 1 disk").

08 May 2013, 08:45	#14
manic23 Only Amiga! Join Date: Jan 2008 Location: London / UK Age: 53 Posts: 512	Yes but that install has separate slaves for the ECS and AGA versions, I was just asking if the slave that Abaddon posted on this thread was ecs or AGA Last edited by manic23; 08 May 2013 at 08:56.

08 May 2013, 13:22	#16
Abaddon Registered User Join Date: Apr 2010 Location: Chicago/USA Age: 54 Posts: 651	Re: WHDLoad choppy The attached slave is for the ecs version. The source for the AGA version was not included in the install package. This was just a quick fix to see if the blitter waits were the culprit making it choppy. Since there was no response the install package never got updated.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
gaming system with most choppy scrolling?	s2325	Retrogaming General Discussion	46	31 May 2020 00:05
Mouse movement too fast and "choppy"	kwah	support.WinUAE	2	14 January 2010 10:41
WHDload issues (Complete WHDload nub, apologies in advance)	dire_wolf	project.WHDLoad	31	09 October 2009 20:41
Choppy sound when in full screen mode	UncleSpam	support.WinUAE	7	16 January 2007 02:03
FIXED Slowdown Problem/Choppy Sound	darkseid	support.WinUAE	9	20 April 2002 00:29

04 November 2012, 01:56	#2
fryguy Registered User Join Date: Aug 2005 Location: Skarabörg, Sweden Age: 44 Posts: 1,019	Do you have any fastmem? Are you using the preload tooltype?

04 November 2012, 03:56	#4
AmmoJammo Registered User Join Date: Nov 2012 Location: Adelaide, Australia Posts: 57	I have the same thing happen running Flimbos Quest on my A500 (havent tried many games), either at the stock 7mhz, or running the 030 at 36Mhz, 8meg fast ram, 1meg chip.

04 November 2012, 13:22	#5
fryguy Registered User Join Date: Aug 2005 Location: Skarabörg, Sweden Age: 44 Posts: 1,019	I believe WHDLoad works best with Blizzard cards. But you can try the following tool types: NOAUTOVEC and NOMMU They made WHDLoad work better on my MBX1230.

04 November 2012, 19:36	#7
Retro-Nerd Missile Command Champion Join Date: Aug 2005 Location: Germany Age: 52 Posts: 12,438	It has nothing to do with a specific turbo card maker. WHDLoad works also perfectly fine on M-Tec or the newer ACA cards. Wait if Wepl could tell you more.

04 November 2012, 20:10	#9
StingRay move.l #$c0ff33,throat Join Date: Dec 2005 Location: Berlin/Joymoney Posts: 6,863	This is because of the added blitter waits. It has nothing to do with WHDLoad, the slaves need to be updated to allow the user to disable the blitter waits.

07 May 2013, 20:52	#12
manic23 Only Amiga! Join Date: Jan 2008 Location: London / UK Age: 53 Posts: 512	I know this is an old thread, but does this slave work with the AGA or ECS versions?

08 May 2013, 09:02	#15
Wepl Moderator Join Date: Nov 2001 Location: Germany Posts: 866	in regard to the filesize it must be the OCS slave, also the AGA slave has probably no (less) blitter waits

08 May 2013, 13:25	#17
manic23 Only Amiga! Join Date: Jan 2008 Location: London / UK Age: 53 Posts: 512	OK thanks for clarifying, I will test over the weekend and report back.

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