Space Gun - Revision history

Polluks: /* Shame */

2023-12-05T10:06:07Z

Shame

← Older revision		Revision as of 10:06, 5 December 2023
Line 41:		Line 41:
	This game is not really good indeed.		This game is not really good indeed.

	The reason is that it is a shamefull Speccy Port.		The reason is that it is a shamefull [[Speccy Port]].

	Just look at the Spectrum version to see what i mean.		Just look at the Spectrum version to see what i mean.

Polluks: /* Use of Plus Features */

2023-12-05T10:02:13Z

Use of Plus Features

← Older revision		Revision as of 10:02, 5 December 2023
Line 87:		Line 87:

	*'''Mode change :''' the texts during Menu page or cinematics, and the upper HUD (top of the screen) are in Mode2 (1bpp) while the rest is in mode0 (4bpp). Despite being Mode2, the letters (characters) used 16 pixels and could have been done in mode1. This part seem to slightly bug on emulator.		*'''Mode change :''' the texts during Menu page or cinematics, and the upper HUD (top of the screen) are in Mode2 (1bpp) while the rest is in mode0 (4bpp). Despite being Mode2, the letters (characters) used 16 pixels and could have been done in mode1. This part seem to slightly bug on emulator.

	**multiloadings are used as the game must be quite heavy on memory requirements. on cartridge, this game properly done would have needed 256K or even 512K ROM cartridge. As a result only the 6128 config can play this (with no ROM).		**multiloadings are used as the game must be quite heavy on memory requirements. on cartridge, this game properly done would have needed 256K or even 512K ROM cartridge. As a result only the 6128 config can play this (with no ROM).

	** The '''cinematic screens''' look a lot like the C64 version ones but more coloured and with a bit less attributes limitation remains.		** The '''cinematic screens''' look a lot like the C64 version ones but more coloured and with a bit less attributes limitation remains.

	** The "find graphics" option on WinApe enables to find the graphics for the 2nd player's HUD... but this multiplayer feature is simply disabled, so just those graphics just became a waste of RAM.		** The "find graphics" option on WinApe enables to find the graphics for the 2nd player's HUD... but this multiplayer feature is simply disabled, so just those graphics just became a waste of RAM.

Arnoldemu: /* Plus Features */

2013-12-04T13:21:48Z

Plus Features

← Older revision		Revision as of 13:21, 4 December 2013
Line 72:		Line 72:
	The playfield also use some raster which are quite similar to the Arcade... but sadly this simply displays even more the unmasked tiles/characters from the sprites. could have been better provided the sprites were properly 4bpp coded as the "raster ink" would be used as a "sort of a mask".		The playfield also use some raster which are quite similar to the Arcade... but sadly this simply displays even more the unmasked tiles/characters from the sprites. could have been better provided the sprites were properly 4bpp coded as the "raster ink" would be used as a "sort of a mask".

	== Plus Features ==		== Use of Plus Features ==

	*~~'''HardSprites :'''~~ used ~~for the title page~~ (~~golden/yellow logo~~, ~~to get easier~~ extra colours ~~and ink cycling~~) ~~and~~ for ~~the visor and bullets, also~~ for ~~the Scanner/Radar at bottom of~~ screen ~~HUD.~~.~~. those visor and scanner use some ink rotation/cycles. The Visor uses 2 Hardsprites with some colour cycles and those sprites may change if you change the selected weapon (new content~~ is loaded into the ASIC's sprite inner RAM), bullets use 2 HardSprites slots per frames (6 frames, so 12 slots) and Radar uses 2 Sprites with colour cycles too. Those sprites are all magnified into pseudo Mode0 sized pixels (X=4 and Y=1). ~~To use Harsprite for the visor~~ is ~~and easy way to get this one masked and with smooth movement while the game is non masked and attribute movement based~~.		* Plus palette is used throughout (colour fading, extra colours throughout)
			* Plus raster line interrupts are used (for changing modes for example)
			* Plus screen split is used.
			* Plus hardware scrolling is not used.
			* Plus DMA sound is not used.

	*~~'''HardScrolling :''' not confirmed~~. ~~Being a character based graphic engine~~, ~~it is quite probable that~~ the ~~exact ZX Spectrum routines were used~~.		* Plus hardware sprites are used. (used for the title page logo, your aiming reticule, bullets, and the Scanner/Radar at bottom of screen HUD).

	*'''Palette :''' this game clearly uses ~~colours unavailable~~ to ~~old Amstrad CPC palette~~.		The hardware sprites use ink cycling. The Visor uses 2 sprites with some colour cycling and those sprites may change if you change the selected weapon , bullets use 2 sprites slots per frames (6 frames, so 12 slots) and Radar uses 2 Sprites with colour cycles too. Those sprites are all magnified into pseudo Mode0 sized pixels (X=4 and Y=1). To use sprite for the aiming reticule is an easy way to get masked and smooth movement while the game is non masked and attribute movement based.

	*'''~~DMA sound channels~~ :''' ~~the sounds are minimalist... the game even do not features the Spectrum128/Atari ST chiptune (which is quite good) so it is most probable the DMA channel weren't used.~~		*'''Others :'''

	*'''Raster interrupts :''' one Bitmap ink on the Mode0 part of the screen is used to display some raster effects, actually even betterly done as on the 16bit Atari ST/Amiga versions, and closer to the Arcade version. Sadly, as said before, this just displays even more the non-masked attributes from the sprites (with a lot of diagonal designs...). When not "Software attribute based sprites" are displayed, the games manages to look quite good.

	*'''Mode change :''' the texts during Menu page or cinematics, and the upper HUD (top of the screen) are in Mode2 (1bpp) while the rest is in mode0 (4bpp). Despite being Mode2, the letters (characters) used 16 pixels and could have been done in mode1. This part seem to slightly bug on emulator.		*'''Mode change :''' the texts during Menu page or cinematics, and the upper HUD (top of the screen) are in Mode2 (1bpp) while the rest is in mode0 (4bpp). Despite being Mode2, the letters (characters) used 16 pixels and could have been done in mode1. This part seem to slightly bug on emulator.

	*'''Others :'''

	**multiloadings are used as the game must be quite heavy on memory requirements. on cartridge, this game properly done would have needed 256K or even 512K ROM cartridge. As a result only the 6128 config can play this (with no ROM).		**multiloadings are used as the game must be quite heavy on memory requirements. on cartridge, this game properly done would have needed 256K or even 512K ROM cartridge. As a result only the 6128 config can play this (with no ROM).

MacDeath: /* Plus Features */

2011-08-20T03:20:15Z

Plus Features

← Older revision		Revision as of 03:20, 20 August 2011
Line 74:		Line 74:
	== Plus Features ==		== Plus Features ==

	*'''HardSprites :''' used for the title page (golden/yellow logo, to get easier extra colours and ink cycling) and for the visor and bullets, also for the Scanner/Radar at bottom of screen HUD... those visor and scanner use some ink rotation/cycles. The Visor uses 2 ~~Haardsprites~~ with some colour cycles, bullets use 2 HardSprites slots per frames (6 frames, so 12 slots) and Radar uses 2 Sprites with colour cycles too. Those sprites are all magnified into pseudo Mode0 sized pixels (X=4 and Y=1). To use Harsprite for the visor is and easy way to get this one masked and with smooth movement while the game is non masked and attribute movement based.		*'''HardSprites :''' used for the title page (golden/yellow logo, to get easier extra colours and ink cycling) and for the visor and bullets, also for the Scanner/Radar at bottom of screen HUD... those visor and scanner use some ink rotation/cycles. The Visor uses 2 Hardsprites with some colour cycles and those sprites may change if you change the selected weapon (new content is loaded into the ASIC's sprite inner RAM), bullets use 2 HardSprites slots per frames (6 frames, so 12 slots) and Radar uses 2 Sprites with colour cycles too. Those sprites are all magnified into pseudo Mode0 sized pixels (X=4 and Y=1). To use Harsprite for the visor is and easy way to get this one masked and with smooth movement while the game is non masked and attribute movement based.

	*'''HardScrolling :''' not confirmed. Being a character based graphic engine, it is quite probable that the exact ZX Spectrum routines were used.		*'''HardScrolling :''' not confirmed. Being a character based graphic engine, it is quite probable that the exact ZX Spectrum routines were used.

MacDeath: /* Plus Features */

2011-08-20T03:17:26Z

Plus Features

← Older revision		Revision as of 03:17, 20 August 2011
Line 74:		Line 74:
	== Plus Features ==		== Plus Features ==

	*'''HardSprites :''' used for the title page (golden/yellow logo, to get easier extra colours and ink cycling) and for the visor and bullets, also for the Scanner/Radar at bottom of screen HUD... those visor and scanner use some ink rotation/cycles. The Visor uses 2 Haardsprites with some colour cycles, bullets use 2 HardSprites slots per frames (6 frames, so 12 slots) and Radar uses 2 Sprites with colour cycles too. Those sprites are all magnified into pseudo Mode0 sized pixels (X=4 and Y=1).		*'''HardSprites :''' used for the title page (golden/yellow logo, to get easier extra colours and ink cycling) and for the visor and bullets, also for the Scanner/Radar at bottom of screen HUD... those visor and scanner use some ink rotation/cycles. The Visor uses 2 Haardsprites with some colour cycles, bullets use 2 HardSprites slots per frames (6 frames, so 12 slots) and Radar uses 2 Sprites with colour cycles too. Those sprites are all magnified into pseudo Mode0 sized pixels (X=4 and Y=1). To use Harsprite for the visor is and easy way to get this one masked and with smooth movement while the game is non masked and attribute movement based.

	*'''HardScrolling :''' not confirmed. Being a character based graphic engine, it is quite probable that the exact ZX Spectrum routines were used.		*'''HardScrolling :''' not confirmed. Being a character based graphic engine, it is quite probable that the exact ZX Spectrum routines were used.

MacDeath: /* Plus Features */

2011-08-20T03:15:53Z

Plus Features

← Older revision		Revision as of 03:15, 20 August 2011
Line 74:		Line 74:
	== Plus Features ==		== Plus Features ==

	*'''HardSprites :''' used for the title page (golden/yellow logo, to get easier extra colours and ink cycling) and for the visor and bullets, also for the Scanner/Radar at bottom of screen HUD... those visor and scanner use some ink rotation/cycles. ~~the Hardsprites are all magnified in pseudo Mode0 ( X=4 and Y=1).~~ Visor uses 2 Haardsprites with some colour cycles, bullets use 2 HardSprites slots per frames (6 frames, so 12 slots) and Radar uses 2 Sprites with colour cycles too. Those sprites are all magnified into pseudo Mode0 sized pixels (X=4 and Y=1).		*'''HardSprites :''' used for the title page (golden/yellow logo, to get easier extra colours and ink cycling) and for the visor and bullets, also for the Scanner/Radar at bottom of screen HUD... those visor and scanner use some ink rotation/cycles. The Visor uses 2 Haardsprites with some colour cycles, bullets use 2 HardSprites slots per frames (6 frames, so 12 slots) and Radar uses 2 Sprites with colour cycles too. Those sprites are all magnified into pseudo Mode0 sized pixels (X=4 and Y=1).

	*'''HardScrolling :''' not confirmed. Being a character based graphic engine, it is quite probable that the exact ZX Spectrum routines were used.		*'''HardScrolling :''' not confirmed. Being a character based graphic engine, it is quite probable that the exact ZX Spectrum routines were used.

MacDeath: /* Plus Features */

2011-08-20T03:14:33Z

Plus Features

← Older revision		Revision as of 03:14, 20 August 2011
Line 74:		Line 74:
	== Plus Features ==		== Plus Features ==

	*HardSprites : used for the title page (golden/yellow logo, to get easier extra colours and ink cycling) and for the visor and bullets, also for the Scanner/Radar at bottom of screen HUD... those visor and scanner use some ink rotation/cycles. the Hardsprites are all magnified in pseudo Mode0 ( X=4 and Y=1). Visor uses 2 Haardsprites with some colour cycles, bullets use 2 HardSprites slots per frames (6 frames, so 12 slots) and Radar uses 2 Sprites with colour cycles too. Those sprites are all magnified into pseudo Mode0 sized pixels (X=4 and Y=1).		*'''HardSprites :''' used for the title page (golden/yellow logo, to get easier extra colours and ink cycling) and for the visor and bullets, also for the Scanner/Radar at bottom of screen HUD... those visor and scanner use some ink rotation/cycles. the Hardsprites are all magnified in pseudo Mode0 ( X=4 and Y=1). Visor uses 2 Haardsprites with some colour cycles, bullets use 2 HardSprites slots per frames (6 frames, so 12 slots) and Radar uses 2 Sprites with colour cycles too. Those sprites are all magnified into pseudo Mode0 sized pixels (X=4 and Y=1).

	*HardScrolling : not confirmed. Being a character based graphic engine, it is quite probable that the exact ZX Spectrum routines were used.		*'''HardScrolling :''' not confirmed. Being a character based graphic engine, it is quite probable that the exact ZX Spectrum routines were used.

	*Palette : this game clearly uses colours unavailable to old Amstrad CPC palette.		*'''Palette :''' this game clearly uses colours unavailable to old Amstrad CPC palette.

	*DMA sound channels : the sounds are minimalist... the game even do not features the Spectrum128/Atari ST chiptune (which is quite good) so it is most probable the DMA channel weren't used.		*'''DMA sound channels :''' the sounds are minimalist... the game even do not features the Spectrum128/Atari ST chiptune (which is quite good) so it is most probable the DMA channel weren't used.

	*Raster interrupts : one Bitmap ink on the Mode0 part of the screen is used to display some raster effects, actually even betterly done as on the 16bit Atari ST/Amiga versions, and closer to the Arcade version. Sadly, as said before, this just displays even more the non-masked attributes from the sprites (with a lot of diagonal designs...). When not "Software attribute based sprites" are displayed, the games manages to look quite good.		*'''Raster interrupts :''' one Bitmap ink on the Mode0 part of the screen is used to display some raster effects, actually even betterly done as on the 16bit Atari ST/Amiga versions, and closer to the Arcade version. Sadly, as said before, this just displays even more the non-masked attributes from the sprites (with a lot of diagonal designs...). When not "Software attribute based sprites" are displayed, the games manages to look quite good.

	*Mode change : the texts during Menu page or cinematics, and the upper HUD (top of the screen) are in Mode2 (1bpp) while the rest is in mode0 (4bpp). Despite being Mode2, the letters (characters) used 16 pixels and could have been done in mode1. This part seem to slightly bug on emulator.		*'''Mode change :''' the texts during Menu page or cinematics, and the upper HUD (top of the screen) are in Mode2 (1bpp) while the rest is in mode0 (4bpp). Despite being Mode2, the letters (characters) used 16 pixels and could have been done in mode1. This part seem to slightly bug on emulator.

	*Others :		*'''Others :'''

	**multiloadings are used as the game must be quite heavy on memory requirements. on cartridge, this game properly done would ~~even~~ have needed 256K or even 512K ROM cartridge. As a result only the 6128 config can play this (with no ROM).		**multiloadings are used as the game must be quite heavy on memory requirements. on cartridge, this game properly done would have needed 256K or even 512K ROM cartridge. As a result only the 6128 config can play this (with no ROM).

	** ~~the~~ cinematic screens ~~looks~~ a lot like the C64 version ones but more coloured and with a bit less attributes limitation remains.		** The '''cinematic screens''' look a lot like the C64 version ones but more coloured and with a bit less attributes limitation remains.

	** ~~the~~ "find graphics" option on WinApe enables to find the graphics for the 2nd player's HUD... but this multiplayer feature is simply disabled, so just those graphics just became a waste of RAM.		** The "find graphics" option on WinApe enables to find the graphics for the 2nd player's HUD... but this multiplayer feature is simply disabled, so just those graphics just became a waste of RAM.

	== Links ==		== Links ==

MacDeath: /* Plus Features */

2011-08-20T03:13:06Z

Plus Features

← Older revision		Revision as of 03:13, 20 August 2011
Line 82:		Line 82:
	*DMA sound channels : the sounds are minimalist... the game even do not features the Spectrum128/Atari ST chiptune (which is quite good) so it is most probable the DMA channel weren't used.		*DMA sound channels : the sounds are minimalist... the game even do not features the Spectrum128/Atari ST chiptune (which is quite good) so it is most probable the DMA channel weren't used.

	*Raster interrupts : one Bitmap ink is used to display some raster ~~effets~~, actually even betterly done as on the 16bit Atari ST/Amiga versions, and closer to the Arcade version. ~~sadly~~, as said before, this just displays even more the non-masked attributes from the sprites (with a lot of diagonal designs...)		*Raster interrupts : one Bitmap ink on the Mode0 part of the screen is used to display some raster effects, actually even betterly done as on the 16bit Atari ST/Amiga versions, and closer to the Arcade version. Sadly, as said before, this just displays even more the non-masked attributes from the sprites (with a lot of diagonal designs...). When not "Software attribute based sprites" are displayed, the games manages to look quite good.

			*Mode change : the texts during Menu page or cinematics, and the upper HUD (top of the screen) are in Mode2 (1bpp) while the rest is in mode0 (4bpp). Despite being Mode2, the letters (characters) used 16 pixels and could have been done in mode1. This part seem to slightly bug on emulator.

	*Others :		*Others :

MacDeath: rdsprites, bulets use 2 Hardsprites per frames (12 slots used) and scanner/radar uses 2 slots too (with colour cycles)

2011-08-20T03:05:33Z

rdsprites, bulets use 2 Hardsprites per frames (12 slots used) and scanner/radar uses 2 slots too (with colour cycles)

← Older revision		Revision as of 03:05, 20 August 2011
Line 74:		Line 74:
	== Plus Features ==		== Plus Features ==

	*HardSprites : used for the title page (golden/yellow logo) and for the visor and bullets, also for the Scanner/Radar at bottom of screen HUD... those visor and scanner use some ink rotation/cycles.		*HardSprites : used for the title page (golden/yellow logo, to get easier extra colours and ink cycling) and for the visor and bullets, also for the Scanner/Radar at bottom of screen HUD... those visor and scanner use some ink rotation/cycles. the Hardsprites are all magnified in pseudo Mode0 ( X=4 and Y=1). Visor uses 2 Haardsprites with some colour cycles, bullets use 2 HardSprites slots per frames (6 frames, so 12 slots) and Radar uses 2 Sprites with colour cycles too. Those sprites are all magnified into pseudo Mode0 sized pixels (X=4 and Y=1).

	*HardScrolling : not confirmed.		*HardScrolling : not confirmed. Being a character based graphic engine, it is quite probable that the exact ZX Spectrum routines were used.

	*Palette : this game clearly uses colours unavailable to old Amstrad CPC palette.		*Palette : this game clearly uses colours unavailable to old Amstrad CPC palette.

MacDeath: /* Plus Features */

2011-08-20T02:59:53Z

Plus Features

← Older revision		Revision as of 02:59, 20 August 2011
Line 90:		Line 90:
	** the cinematic screens looks a lot like the C64 version ones but more coloured and with a bit less attributes limitation remains.		** the cinematic screens looks a lot like the C64 version ones but more coloured and with a bit less attributes limitation remains.

	** the find graphics option on WinApe enables to find the graphics for the 2nd player's HUD... but this feature is simply disabled, so just became a waste of RAM.		** the "find graphics" option on WinApe enables to find the graphics for the 2nd player's HUD... but this multiplayer feature is simply disabled, so just those graphics just became a waste of RAM.

	== Links ==		== Links ==