3DS Virtual Console - Revision history

TuxSH: Fix confusion about CAA descriptor type

2025-01-05T22:54:12Z

Fix confusion about CAA descriptor type

← Older revision		Revision as of 01:54, 6 January 2025
Line 215:		Line 215:
	\| 0x0		\| 0x0
	\| 0x4		\| 0x4
	\| ~~If 1, then this config descriptor is used~~. If 0, and ~~the following value is not~~ 0~~, then the GBA VC load~~ fails ~~outright (causes~~ result 0xC900464F). ~~Otherwise~~, ~~this config descriptor is skipped.~~		\| Entry type. 0 is the ROM itself (without the CAA stuff) and offset must be 0 (otherwise fails w/ result 0xC900464F). 1 is ROM metadata, see below
	\|-		\|-
	\| 0x4		\| 0x4
	\| 0x4		\| 0x4
	\| Offset to ~~config~~		\| Offset to entry data
	\|-		\|-
	\| 0x8		\| 0x8
	\| 0x4		\| 0x4
	\| Size of ~~config~~ (unused by the function that parses this, which hardcodes the config size (0x324) to memcpy)		\| Size of entry data (unused by the function that parses this, which hardcodes the config size (0x324) to memcpy for type 1)
	\|-		\|-
	\| 0xC		\| 0xC
Line 230:		Line 230:
	\|}		\|}

	====~~Config~~====		====AGB ROM metadata====

	{\| class="wikitable" border="1"		{\| class="wikitable" border="1"
Line 264:		Line 264:
	\| 0x020		\| 0x020
	\| 0x4		\| 0x4
	\| ~~LCD ghosting~~ (01-FF, lower values equal more ghosting)		\| "Accumulated" interframe alpha blending (01-FF, lower values equal more "ghosting"). Uses previous output instead of previous input
	\|-		\|-
	\| 0x024		\| 0x024

TimmSkiller: /* Config */

2021-09-03T16:48:28Z

Config

← Older revision		Revision as of 20:48, 3 September 2021
Line 237:		Line 237:
	! SIZE		! SIZE
	! DESCRIPTION		! DESCRIPTION
			\|-
			\| 0x000
			\| 0x4
			\| Padding
	\|-		\|-
	\| 0x004		\| 0x004
Line 245:		Line 249:
	\| 0x4		\| 0x4
	\| Save type (see below for supported values and [[ARM7_Registers#ARM7_SAVE_MODE\|here]] for details)		\| Save type (see below for supported values and [[ARM7_Registers#ARM7_SAVE_MODE\|here]] for details)
			\|-
			\| 0x00C
			\| 0x2
			\| Padding (set to FF FF usually?)
	\|-		\|-
	\| 0x00E		\| 0x00E

AuroraWright at 03:25, 31 May 2020

2020-05-31T01:25:44Z

← Older revision		Revision as of 05:25, 31 May 2020
Line 165:		Line 165:
	The 0x60 header is followed by the SNES ROM, often altered to replace audio samples with pointers to external PCM audio files converted from the game, presumably to speed up emulation (these pointers can be found by looking for "PCMF" in the ROM, as seen on [https://github.com/Plombo/vcromclaim/blob/master/snesrestore.py Wii VC]).		The 0x60 header is followed by the SNES ROM, often altered to replace audio samples with pointers to external PCM audio files converted from the game, presumably to speed up emulation (these pointers can be found by looking for "PCMF" in the ROM, as seen on [https://github.com/Plombo/vcromclaim/blob/master/snesrestore.py Wii VC]).
	The ROM is then optionally followed by the PCM audio files, by the SDD-1 decompressed graphics data (the emulator doesn't properly emulate the chip, presumably because of hardware constraints) and by a footer which appears to be an index for the PCM audio data.		The ROM is then optionally followed by the PCM audio files, by the SDD-1 decompressed graphics data (the emulator doesn't properly emulate the chip, presumably because of hardware constraints) and by a footer which appears to be an index for the PCM audio data.
	There are no setting fields for ~~specific~~ cart features~~, with the exception of Special Chip~~, and it appears that the emulator has "game presets" stored in its own code, which ~~determines more~~ game-specific settings~~. The Special Chip can also be enabled by~~ the ~~game Preset~~ ID. Each official VC release has [https://docs.google.com/spreadsheets/d/1PbIPVA4NpFEXs1zk249aR3FSuBTY3r-ajpTq3dP3GnQ/edit#gid=490971147 a different preset ID] ~~in the header~~. The supported ~~Special Chips~~ are: DSP1, C4 and DSP2.		There are no separate setting fields for individual cart features, and it appears that the emulator has "game presets" stored in its own code, which determine the game-specific settings (such as the expansion chip, and presumably the presence of SRAM), selectable via the preset ID in the header. Each official VC release has [https://docs.google.com/spreadsheets/d/1PbIPVA4NpFEXs1zk249aR3FSuBTY3r-ajpTq3dP3GnQ/edit#gid=490971147 a different preset ID]. The supported SNES expansion chips are: DSP1, C4 and DSP2.

	A similar structure can be found on Wii U, SNES Classic and Switch Mini emulator [https://gist.github.com/anpage/c1085055db0242ea3c7558dab56712a5]		A similar structure can be found on the Wii U, SNES Classic and Switch Mini emulator [https://gist.github.com/anpage/c1085055db0242ea3c7558dab56712a5]

	==Savedata==		==Savedata==

Owowhatsthis at 23:40, 24 May 2020

2020-05-24T21:40:23Z

← Older revision		Revision as of 01:40, 25 May 2020
Line 244:		Line 244:
	\| 0x008		\| 0x008
	\| 0x4		\| 0x4
	\| Save type (see below)		\| Save type (see below for supported values and [[ARM7_Registers#ARM7_SAVE_MODE\|here]] for details)
			\|-
			\| 0x00E
			\| 0x2
			\| Sleep mode button combo (utilizes the same bit masks as the [[HID_Registers#HID_PAD\|HID_PAD register]], with flipped bits).<br/>If the GBA title supports a button-combo based sleep mode and it's set here, Agbbg spoofs this combo when closing the 3DS' lid to enter proper sleep mode.
			\|-
			\| 0x010
			\| 0x10
			\| Flash and EEPROM configuration (see the target registers [[ARM7_Registers\|here]])
	\|-		\|-
	\| 0x020		\| 0x020
Line 256:		Line 264:

	Save types:		Save types:
	* 0x0: EEPROM 8k for < 256 Mbit ~~games~~		* 0x0: EEPROM 8k for < 256 Mbit titles
	* 0x1: EEPROM 8k for 256 Mbit ~~games~~		* 0x1: EEPROM 8k for 256 Mbit titles
	* 0x2: EEPROM 64k for < 256 Mbit ~~games~~		* 0x2: EEPROM 64k for < 256 Mbit titles
	* 0x3: EEPROM 64k for 256 Mbit ~~games~~		* 0x3: EEPROM 64k for 256 Mbit titles
	* 0x4: Flash 512k (Atmel, ID: 0x3D1F) + RTC		* 0x4: Flash 512k (Atmel, ID: 0x3D1F) + RTC
	* 0x5: Flash 512k (Atmel, ID: 0x3D1F)		* 0x5: Flash 512k (Atmel, ID: 0x3D1F)

Owowhatsthis: Fix GBA VC savedata info

2020-05-24T20:17:26Z

Fix GBA VC savedata info

← Older revision		Revision as of 00:17, 25 May 2020
Line 256:		Line 256:

	Save types:		Save types:
	* 0x0: EEPROM 8k		* 0x0: EEPROM 8k for < 256 Mbit games
	* 0x1: EEPROM 8k ~~(?)~~		* 0x1: EEPROM 8k for 256 Mbit games
	* 0x2: EEPROM 64k		* 0x2: EEPROM 64k for < 256 Mbit games
	* 0x3: EEPROM 64k ~~(?)~~		* 0x3: EEPROM 64k for 256 Mbit games
	* 0x4: Flash 512k (Atmel, ID: 0x3D1F) + RTC		* 0x4: Flash 512k (Atmel, ID: 0x3D1F) + RTC
	* 0x5: Flash 512k (Atmel, ID: 0x3D1F)		* 0x5: Flash 512k (Atmel, ID: 0x3D1F)

GingerbreadMan: /* data.bin structure */

2019-10-17T23:27:36Z

data.bin structure

← Older revision		Revision as of 03:27, 18 October 2019
Line 165:		Line 165:
	The 0x60 header is followed by the SNES ROM, often altered to replace audio samples with pointers to external PCM audio files converted from the game, presumably to speed up emulation (these pointers can be found by looking for "PCMF" in the ROM, as seen on [https://github.com/Plombo/vcromclaim/blob/master/snesrestore.py Wii VC]).		The 0x60 header is followed by the SNES ROM, often altered to replace audio samples with pointers to external PCM audio files converted from the game, presumably to speed up emulation (these pointers can be found by looking for "PCMF" in the ROM, as seen on [https://github.com/Plombo/vcromclaim/blob/master/snesrestore.py Wii VC]).
	The ROM is then optionally followed by the PCM audio files, by the SDD-1 decompressed graphics data (the emulator doesn't properly emulate the chip, presumably because of hardware constraints) and by a footer which appears to be an index for the PCM audio data.		The ROM is then optionally followed by the PCM audio files, by the SDD-1 decompressed graphics data (the emulator doesn't properly emulate the chip, presumably because of hardware constraints) and by a footer which appears to be an index for the PCM audio data.
	There are no setting fields for specific cart features, with the ~~except~~ of Special Chip, and it appears that the emulator has "game presets" stored in its own code, which determines more game-specific settings. The Special Chip can also be enabled by the game Preset ID. Each official VC release has a different preset ID in the header. The supported Special Chips are: DSP1, C4 and DSP2.		There are no setting fields for specific cart features, with the exception of Special Chip, and it appears that the emulator has "game presets" stored in its own code, which determines more game-specific settings. The Special Chip can also be enabled by the game Preset ID. Each official VC release has [https://docs.google.com/spreadsheets/d/1PbIPVA4NpFEXs1zk249aR3FSuBTY3r-ajpTq3dP3GnQ/edit#gid=490971147 a different preset ID] in the header. The supported Special Chips are: DSP1, C4 and DSP2.

	A similar structure can be found on Wii U, SNES Classic and Switch Mini emulator [https://gist.github.com/anpage/c1085055db0242ea3c7558dab56712a5]		A similar structure can be found on Wii U, SNES Classic and Switch Mini emulator [https://gist.github.com/anpage/c1085055db0242ea3c7558dab56712a5]

GingerbreadMan: /* data.bin structure */

2019-10-17T23:25:44Z

data.bin structure

← Older revision		Revision as of 03:25, 18 October 2019
Line 164:		Line 164:

	The 0x60 header is followed by the SNES ROM, often altered to replace audio samples with pointers to external PCM audio files converted from the game, presumably to speed up emulation (these pointers can be found by looking for "PCMF" in the ROM, as seen on [https://github.com/Plombo/vcromclaim/blob/master/snesrestore.py Wii VC]).		The 0x60 header is followed by the SNES ROM, often altered to replace audio samples with pointers to external PCM audio files converted from the game, presumably to speed up emulation (these pointers can be found by looking for "PCMF" in the ROM, as seen on [https://github.com/Plombo/vcromclaim/blob/master/snesrestore.py Wii VC]).
	The ROM is then optionally followed by the PCM audio files, by the SDD-1 decompressed graphics data (~~presumably~~ the emulator doesn't properly emulate the chip because of hardware constraints) and by a footer which appears to be an index for the PCM audio data.		The ROM is then optionally followed by the PCM audio files, by the SDD-1 decompressed graphics data (the emulator doesn't properly emulate the chip, presumably because of hardware constraints) and by a footer which appears to be an index for the PCM audio data.
	There are no setting fields for specific cart features, and it appears that the emulator has "game presets" stored in its own code, which ~~determine the cart expansion chip and probably~~ more game-specific settings. Each official VC release has a different preset ID in the header.		There are no setting fields for specific cart features, with the except of Special Chip, and it appears that the emulator has "game presets" stored in its own code, which determines more game-specific settings. The Special Chip can also be enabled by the game Preset ID. Each official VC release has a different preset ID in the header. The supported Special Chips are: DSP1, C4 and DSP2.

	A similar structure can be found on Wii U, SNES Classic and Switch Mini emulator [https://gist.github.com/anpage/c1085055db0242ea3c7558dab56712a5]		A similar structure can be found on Wii U, SNES Classic and Switch Mini emulator [https://gist.github.com/anpage/c1085055db0242ea3c7558dab56712a5]

GingerbreadMan: /* data.bin structure */

2019-10-14T02:06:17Z

data.bin structure

← Older revision		Revision as of 06:06, 14 October 2019
Line 132:		Line 132:
	\| 0x3D		\| 0x3D
	\| 0x2		\| 0x2
	\| ~~Game preset~~ ID? (varies for each game). ~~Incremental, started with 0x10XX values in old releases, newest ones have 0x11XX~~ (~~with XX being back to low values~~).		\| Preset ID (varies for each game). A full list of know Preset IDs (shared by WiiU/SNESC/Switch SNES emulators) can be found [https://docs.google.com/spreadsheets/d/1PbIPVA4NpFEXs1zk249aR3FSuBTY3r-ajpTq3dP3GnQ here]
	\|-		\|-
	\| 0x3F		\| 0x3F
Line 166:		Line 166:
	The ROM is then optionally followed by the PCM audio files, by the SDD-1 decompressed graphics data (presumably the emulator doesn't properly emulate the chip because of hardware constraints) and by a footer which appears to be an index for the PCM audio data.		The ROM is then optionally followed by the PCM audio files, by the SDD-1 decompressed graphics data (presumably the emulator doesn't properly emulate the chip because of hardware constraints) and by a footer which appears to be an index for the PCM audio data.
	There are no setting fields for specific cart features, and it appears that the emulator has "game presets" stored in its own code, which determine the cart expansion chip and probably more game-specific settings. Each official VC release has a different preset ID in the header.		There are no setting fields for specific cart features, and it appears that the emulator has "game presets" stored in its own code, which determine the cart expansion chip and probably more game-specific settings. Each official VC release has a different preset ID in the header.

			A similar structure can be found on Wii U, SNES Classic and Switch Mini emulator [https://gist.github.com/anpage/c1085055db0242ea3c7558dab56712a5]

	==Savedata==		==Savedata==

Hiccup: /* NES/GB/GBC VC */

2018-01-06T13:07:31Z

NES/GB/GBC VC

← Older revision		Revision as of 16:07, 6 January 2018
Line 7:		Line 7:
	The original emulator builds include support for all these three platforms, not specific to just the included ROM platform. However, releases intended for NES games have a red menu, optional switching between the two controllers, a different X button mapping (B instead of menu), optional [[Download Play]] support, and [http://s27.postimg.org/60v4yuw8z/IMG_20140921_001103.jpg a never used multi-rom support]; while Game Boy versions have a green theme and optional 3D border.		The original emulator builds include support for all these three platforms, not specific to just the included ROM platform. However, releases intended for NES games have a red menu, optional switching between the two controllers, a different X button mapping (B instead of menu), optional [[Download Play]] support, and [http://s27.postimg.org/60v4yuw8z/IMG_20140921_001103.jpg a never used multi-rom support]; while Game Boy versions have a green theme and optional 3D border.

	Early builds (Ambassador NES games at least) did not support savestates.		Early builds (of Ambassador NES games at least) did not support savestates.

	The emulator officially used for Pokemon games removes savestate support in favor of a Link Cable "implementation" involving hooking the games' network functions according to the patch files. ([https://gbatemp.net/attachments/vc-wireless-link-patch-documentation-txt.72966/ Partial documentation of the patch format])		The emulator officially used for Pokemon games removes savestate support in favor of a Link Cable "implementation" involving hooking the games' network functions according to the patch files. ([https://gbatemp.net/attachments/vc-wireless-link-patch-documentation-txt.72966/ Partial documentation of the patch format])

Ryccardo: /* NES/GB/GBC VC */ factz

2017-12-29T19:37:06Z

NES/GB/GBC VC: factz

← Older revision		Revision as of 22:37, 29 December 2017
Line 3:		Line 3:

	=NES/GB/GBC VC=		=NES/GB/GBC VC=
	An emulator application + VC ROM in the NCCH [[RomFS]] (among other things in the RomFS). The emulator ~~build includes~~ support for all these three platforms, not specific to just the included ROM platform.		An emulator application + VC ROM in the NCCH [[RomFS]] (among other things in the RomFS).

			The original emulator builds include support for all these three platforms, not specific to just the included ROM platform. However, releases intended for NES games have a red menu, optional switching between the two controllers, a different X button mapping (B instead of menu), optional [[Download Play]] support, and [http://s27.postimg.org/60v4yuw8z/IMG_20140921_001103.jpg a never used multi-rom support]; while Game Boy versions have a green theme and optional 3D border.

			Early builds (Ambassador NES games at least) did not support savestates.

			The emulator officially used for Pokemon games removes savestate support in favor of a Link Cable "implementation" involving hooking the games' network functions according to the patch files. ([https://gbatemp.net/attachments/vc-wireless-link-patch-documentation-txt.72966/ Partial documentation of the patch format])

	This emulator includes GBA support, however the GBA emulation for this this is somewhat slow. This was presumably implemented before AGB_FIRM was.		This emulator includes GBA support, however the GBA emulation for this this is somewhat slow. This was presumably implemented before AGB_FIRM was.