P96 Screen and Sound Issues

hurtz · 06 November 2007, 21:47

I have these exact symptoms described in the FAQ section of WHDLoad's documentation:

Question: When run games they are running quicker than normal (Music sounds strange) and the bottom of the display is missing. I have tried both PAL & NTSC tooltypes but nothing helps. Answer: If you are using the Voodoo monitor driver, turn off the "FakeNativeModes" in the tooltypes of the monitor drive.
However setting FakeNativeModes to No does not resolve the problem for me.

My specs are:
A2000HD w/GVP 030/50, 16MB, 2MB Chip, Picasso II, P96, running ClassicWB ADV. 1GB hard drive.

thomas · 06 November 2007, 22:34

AFAIK an A2000 can only be either NTSC or PAL, not both and no way to switch by software. So if you have a NTSC model and run a PAL game, it runs too fast (60 fps instead of 50) and the bottom is cut off (200 lines instead of 256).

The tooltypes probably only work on AGA machines (A1200 or A4000).

StrategyGamer · 06 November 2007, 22:52

Any Amiga with an Enhanced Agnus can instantly switch from PAL to NTSC whenever it gets the urge.

All my A2000s and A500s can do it. How else would we Americans play all the thousands of PAL games in the Amigaverse? Easy we boot our Amigas into PAL.

thomas · 06 November 2007, 22:57

In the A500 era most games were NTSC, even in Europe. In the real A500 era, A500s and A2000s didn't have ECS chips.

Chain · 06 November 2007, 23:13

FakeNativeModes with mediator is really hacky feature

hurtz · 07 November 2007, 21:36

Ok, I figured it out. I set PAL in WHDLoad.prefs.

Is that recommended on a NTSC Amiga? I'm wondering if I'll run into a game that requires or acts screwy with that set globally.

hurtz · 09 November 2007, 16:55

Everything I've tested works in this configuration, only problem is that the screen size is too small. The games don't fill the screen, theres lots of black space.

My A2000 has a 2320 connected to the Picasso II, then out to my NEC Multisync 3D.

Any ideas?

StrategyGamer · 09 November 2007, 17:43

Adjust your monitor using the little buttons and menus to stretch the screen to fill the glass.

hurtz · 09 November 2007, 18:51

Right, thats the obvious solution. My concern was that since this is a NTSC Amiga and I'm forcing PAL in the WHDLoad.prefs and experiencing this if there was a software setting or driver that needed to be tweaked.

Bamiga2002 · 10 November 2007, 09:29

Yes, don't use fakenativemodes. And if you have a mediator set VoodooInt=No, because even if the current WHDLoad handles VoodooInt=Yes, i noticed after exiting a game via quitkey the mouse cursor did things on it's own. Open windows scrolling and WB icons activating itself (not launching though). After VoodooInt=No, no such things happened.

06 November 2007, 21:47	#1
hurtz Registered User Join Date: Sep 2007 Location: IA, USA Posts: 28	P96 Screen and Sound Issues I have these exact symptoms described in the FAQ section of WHDLoad's documentation: Question: When run games they are running quicker than normal (Music sounds strange) and the bottom of the display is missing. I have tried both PAL & NTSC tooltypes but nothing helps. Answer: If you are using the Voodoo monitor driver, turn off the "FakeNativeModes" in the tooltypes of the monitor drive. However setting FakeNativeModes to No does not resolve the problem for me. My specs are: A2000HD w/GVP 030/50, 16MB, 2MB Chip, Picasso II, P96, running ClassicWB ADV. 1GB hard drive.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Sound issues?	thermalthong	support.Hardware	18	02 November 2012 18:14
Sound speed issues.	Hemppo	support.Other	2	28 March 2010 15:04
A1200 sound issues	arnljot	support.Hardware	5	06 February 2008 13:16
Even more sound timing issues...	andreas	support.WinUAE	11	30 November 2005 11:23
P96 Screen Grabber (Real Amiga)	blackcornflake	support.Apps	2	17 October 2002 15:39

06 November 2007, 22:34	#2
thomas Registered User Join Date: Jan 2002 Location: Germany Posts: 6,985	AFAIK an A2000 can only be either NTSC or PAL, not both and no way to switch by software. So if you have a NTSC model and run a PAL game, it runs too fast (60 fps instead of 50) and the bottom is cut off (200 lines instead of 256). The tooltypes probably only work on AGA machines (A1200 or A4000).

06 November 2007, 22:52	#3
StrategyGamer Total Chaos AGA is fun! Join Date: Jun 2005 Location: USA Posts: 873	Any Amiga with an Enhanced Agnus can instantly switch from PAL to NTSC whenever it gets the urge. All my A2000s and A500s can do it. How else would we Americans play all the thousands of PAL games in the Amigaverse? Easy we boot our Amigas into PAL.

06 November 2007, 22:57	#4
thomas Registered User Join Date: Jan 2002 Location: Germany Posts: 6,985	In the A500 era most games were NTSC, even in Europe. In the real A500 era, A500s and A2000s didn't have ECS chips.

06 November 2007, 23:13	#5
Chain A-Collector, repairments Join Date: Jul 2001 Location: Czech Rep. Age: 50 Posts: 1,536	FakeNativeModes with mediator is really hacky feature

07 November 2007, 21:36	#6
hurtz Registered User Join Date: Sep 2007 Location: IA, USA Posts: 28	Ok, I figured it out. I set PAL in WHDLoad.prefs. Is that recommended on a NTSC Amiga? I'm wondering if I'll run into a game that requires or acts screwy with that set globally.

09 November 2007, 16:55	#7
hurtz Registered User Join Date: Sep 2007 Location: IA, USA Posts: 28	Everything I've tested works in this configuration, only problem is that the screen size is too small. The games don't fill the screen, theres lots of black space. My A2000 has a 2320 connected to the Picasso II, then out to my NEC Multisync 3D. Any ideas?

09 November 2007, 17:43	#8
StrategyGamer Total Chaos AGA is fun! Join Date: Jun 2005 Location: USA Posts: 873	Adjust your monitor using the little buttons and menus to stretch the screen to fill the glass.

09 November 2007, 18:51	#9
hurtz Registered User Join Date: Sep 2007 Location: IA, USA Posts: 28	Right, thats the obvious solution. My concern was that since this is a NTSC Amiga and I'm forcing PAL in the WHDLoad.prefs and experiencing this if there was a software setting or driver that needed to be tweaked.

10 November 2007, 09:29	#10
Bamiga2002 BlizzardPPC'less Join Date: May 2004 Location: Finland Age: 46 Posts: 3,210	Yes, don't use fakenativemodes. And if you have a mediator set VoodooInt=No, because even if the current WHDLoad handles VoodooInt=Yes, i noticed after exiting a game via quitkey the mouse cursor did things on it's own. Open windows scrolling and WB icons activating itself (not launching though). After VoodooInt=No, no such things happened.

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