Neuromancer graphics corruption

Crowley · 08 July 2009, 12:54

I've been introducing a friend of mine to the wonderful world of Amiga, and he reported this odd problem when playing Neuromancer:

Quote:

Keep getting these odd graphical glitches. Started off as some odd flashing pixels in the upper left corner after Ratz finished talking. Next thing I know, various character sprites started merging with the borders.

I've just suggested trying different hardware setups and different versions of the game, and haven't heard back yet. I just thought I'd throw this out here to see what people might think, mostly because this sounds very unusual and it got me very curious.

skateblind · 08 July 2009, 18:44

It's either his setup or the ADF he is using, if he is using one. Maybe try a different ADF by another cracker if the he can't get it to work on different hardware settings.

Toni Wilen · 09 July 2009, 10:22

Graphics corruption around moving objects is "standard" problem if program does not wait for blitter and CPU is "too fast".

Use quickstart A500 configuration. (or enable immediate blitter if you want to use wrong configuration, usually it helps)

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Graphics corruption on scrolling	demolition	project.WHDLoad	3	11 November 2012 23:50
A1200 Graphics Corruption	darkwave	support.Hardware	10	07 November 2011 18:10
Graphics corruption on Lotus 2	azy	support.Games	4	15 November 2006 14:49
Graphics corruption	Minuous	support.WinUAE	9	21 July 2005 17:42
Graphics Corruption	DW7	support.WinUAE	3	09 November 2003 01:45

08 July 2009, 18:44	#2
skateblind Village Idiot Join Date: Feb 2009 Location: UK, England Age: 38 Posts: 580	It's either his setup or the ADF he is using, if he is using one. Maybe try a different ADF by another cracker if the he can't get it to work on different hardware settings.

09 July 2009, 10:22	#3
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,573	Graphics corruption around moving objects is "standard" problem if program does not wait for blitter and CPU is "too fast". Use quickstart A500 configuration. (or enable immediate blitter if you want to use wrong configuration, usually it helps)

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