3D rendering - Revision history

Caitemis at 04:19, 15 February 2026

2026-02-15T04:19:25Z

← Older revision		Revision as of 04:19, 15 February 2026
Line 1:		Line 1:
	== 3D Rendering engine ==		== 3D Rendering engine ==
	The Nintendo DS dispose of hardware that can perform 3D rendering in addition to its dedicated 2D system. EoS mostly ~~use~~ the 2D system, but occasionally ~~make~~ use of the 3D engine for some effects. Those are:		The Nintendo DS dispose of hardware that can perform 3D rendering in addition to its dedicated 2D system. EoS mostly uses the 2D system, but occasionally makes use of the 3D engine for some effects. Those are:

	* The dialogue box border and background		* The dialogue box border and background
	* Rendering of the quick status at the top of the bottom screen during a dungeon		* Rendering of the quick status at the top of the bottom screen during a dungeon
	* The various weather ~~effect~~		* The various weather effects
	* Boss transition wipe		* Boss transition wipe
	* A few other ~~effect~~ during cutscenes		* A [[Effect.bin\|few other effects]] during cutscenes



	The 3D engine is capable of rendering in 2D, simply by rendering rectangle in front of the virtual camera, which is what EoS always does. The way this game ~~work~~ is by first buffering the elements to render to a buffer and then a function will submit those to render (probably during VBlank), which will then take effect on the next frame.		The 3D engine is capable of rendering in 2D, simply by rendering rectangle in front of the virtual camera, which is what EoS always does. The way this game works is by first buffering the elements to render to a buffer, and then a function will submit those to render (probably during VBlank), which will then take effect on the next frame.

	The DS 3D hardware can only render on the main screen, which in EoS is the bottom screen. Some game (but not EoS) render on both screen by switching the main screen every frame, dividing by two the frame rate from 60 to 30 FPS.		The DS 3D hardware can only render on the main screen, which in EoS is the bottom screen. Some game (but not EoS) render on both screen by switching the main screen every frame, dividing by two the frame rate from 60 to 30 FPS.
Line 17:		Line 17:
	The bank D is dedicated to storing the textures used for the 3D render, and bank F is used to store the palettes. Bank D is 128KiB large, and bank F is 16KiB large. The game seems to mostly allocate texture on a multiple of 1KiB, and palette on a multiple of 0x100 bytes, thought it is possible to perform allocation not aligned on those arbitrary values (but it still (maybe, untested) need to be 4-bytes aligned).		The bank D is dedicated to storing the textures used for the 3D render, and bank F is used to store the palettes. Bank D is 128KiB large, and bank F is 16KiB large. The game seems to mostly allocate texture on a multiple of 1KiB, and palette on a multiple of 0x100 bytes, thought it is possible to perform allocation not aligned on those arbitrary values (but it still (maybe, untested) need to be 4-bytes aligned).

	The game store its 3D data in WTE files. It contain the texture and the palette, but not where the file will be stored in the RAM, which is specified in the game’s code. Here is table of the (known) ~~allocation~~ the game ~~make~~. It is probably exhaustive.		The game store its 3D data in WTE files. It contain the texture and the palette, but not where the file will be stored in the RAM, which is specified in the game’s code. Here is table of the (known) allocations the game makes. It is probably exhaustive.

	ProcessWTE is the function used to load them (function address is for EU ROM, but palette and texture allocation have no reason to be different).		ProcessWTE is the function used to load them (function address is for EU ROM, but palette and texture allocation have no reason to be different).

RRad: Adding some use cases

2025-10-06T19:22:23Z

Adding some use cases

← Older revision		Revision as of 19:22, 6 October 2025
Line 42:		Line 42:
	\|1007 to 1011 in dungeon pack		\|1007 to 1011 in dungeon pack
	\|dungeon		\|dungeon
	\|		\|Numbers and "Miss" text. Used to display damage taken and misses.
	\|overlay_29::02336200		\|overlay_29::02336200
	\|0x0		\|0x0
Line 51:		Line 51:
	\|1031 or 1003 in dungeon pack		\|1031 or 1003 in dungeon pack
	\|dungeon		\|dungeon
	\|~~both are fogs~~ texture		\|1031: Mist/Steam texture. Visual-only effect paired with some tilesets.<br>1003: Poison mist texture used only during Sky Peak boss fight.
	\|overlay_29::023394e4 or overlay_29::023395f8		\|overlay_29::023394e4 or overlay_29::023395f8
	\|0xB000		\|0xB000
	\|0x2000		\|0x2000
	\|0x1400		\|0x1400
	\|unknown how which one is ~~choosed~~		\|unknown how which one is chosen
	\|-		\|-
	\|1005 in dungeon pack		\|1005 in dungeon pack
	\|dungeon		\|dungeon
	\|		\|Sandstorm texture used during its weather condition.
	\|overlay_29::023394e4		\|overlay_29::023394e4
	\|0xD000		\|0xD000
Line 69:		Line 69:
	\|1001 in dungeon pack		\|1001 in dungeon pack
	\|dungeon		\|dungeon
	\|		\|Fog texture used during its weather condition.
	\|overlay_29::023394e4		\|overlay_29::023394e4
	\|0xF000		\|0xF000
Line 78:		Line 78:
	\|some between 1012 to 1020 in dungeon pack		\|some between 1012 to 1020 in dungeon pack
	\|dungeon		\|dungeon
	\|		\|Level/HP display text and HP bar.
	\|overlay_29::0233614c		\|overlay_29::0233614c
	\|0x1000		\|0x1000
Line 87:		Line 87:
	\|c_wipe.wte or w_wipe2.wte		\|c_wipe.wte or w_wipe2.wte
	\|		\|
	\|~~horizontal~~ bar of differing colors, ~~presumably for wiping the screen~~		\|Horizontal bar of differing colors, used by Team Charm's special wipe effect in SE4.
	\|0x0206afb0		\|0x0206afb0
	\|		\|
Line 96:		Line 96:
	\|w_heart.wte		\|w_heart.wte
	\|		\|
	\|~~multiple~~ hearts symbol, filled and shaded		\|Multiple hearts symbol, filled and shaded. More Team Charm.
	\|0x0206b000		\|0x0206b000
	\|		\|
Line 105:		Line 105:
	\|circle.wte		\|circle.wte
	\|		\|
	\|~~hearth~~ symbol, not filled		\|Heart symbol, not filled. More Team Charm.
	\|0x0206b050		\|0x0206b050
	\|		\|
Line 141:		Line 141:
	\|p03p01t1.wte		\|p03p01t1.wte
	\|overworld		\|overworld
	\|~~fog/mist~~ texture		\|Fog texture for Groudon Statue cutscene.
	\|overlay_11::02314eec		\|overlay_11::02314eec
	overlay_11::022f33d8		overlay_11::022f33d8
Line 160:		Line 160:
	\|t01p01t1.wte		\|t01p01t1.wte
	\|overworld		\|overworld
	\|~~some clouds~~		\|Treasure Town cloud shadows.
	\|overlay_11::022f3368 (loading weather 1)		\|overlay_11::022f3368 (loading weather 1)
	\|0x0		\|0x0
Line 169:		Line 169:
	\|t01p01t2.wte		\|t01p01t2.wte
	\|overworld		\|overworld
	\|~~some clouds~~		\|More Treasure Town cloud shadows.
	\|overlay_11::022f3394 (loading weather 1)		\|overlay_11::022f3394 (loading weather 1)
	\|0x4000		\|0x4000
Line 178:		Line 178:
	\|d73p41t1.wte		\|d73p41t1.wte
	\|overworld		\|overworld
	\|~~another kind of~~ mist~~/fog (~~top of ~~Shaymin mountain?)~~		\|Poison mist. Only used on top of Sky Peak on first visit.
	\|overlay_11::022f341c (loading weather 3)		\|overlay_11::022f341c (loading weather 3)
	\|0x0		\|0x0

Marius851000: /* Loading texture */

2025-10-04T16:39:01Z

Loading texture

← Older revision		Revision as of 16:39, 4 October 2025
Line 188:		Line 188:

	==== Loading texture ====		==== Loading texture ====
	Once you have your texture in the WTE format saved in the rom, you need to call a function to load WTE ('''LoadWteFromRom''') and then copy stuff to RAM with '''ProcessWTEWrapper''', and then call ~~another (unnamed in pmdsky-debug) function~~ '''~~DoSomethingOn3dAllocAndClearInput~~'''.		Once you have your texture in the WTE format saved in the rom, you need to call a function to load WTE ('''LoadWteFromRom''') and then copy stuff to the appropriate texture RAM with '''ProcessWTEWrapper''' (this will create a task to process the copy, once access to texture-RAM is safe), and then call '''DelayWTEFree''' (to make sure the original texture is freed once copy to texture-RAM is finished).

Frostbyte: Frostbyte moved page User:Marius851000/Draft/3drender to 3D rendering without leaving a redirect: Finished page

2024-08-30T14:38:04Z

Frostbyte moved page User:Marius851000/Draft/3drender to 3D rendering without leaving a redirect: Finished page

← Older revision	Revision as of 14:38, 30 August 2024
(No difference)

Marius851000: Improved syntax and some typo

2024-08-30T06:00:27Z

Improved syntax and some typo

← Older revision		Revision as of 06:00, 30 August 2024
Line 1:		Line 1:
	== 3D Rendering engine ==		== 3D Rendering engine ==
	The Nintendo DS dispose of hardware that can perform 3D rendering in addition to ~~it’s~~ dedicated 2D system. EoS mostly use the 2D system, but occasionally make use of the 3D engine for some effects. Those are:		The Nintendo DS dispose of hardware that can perform 3D rendering in addition to its dedicated 2D system. EoS mostly use the 2D system, but occasionally make use of the 3D engine for some effects. Those are:

	* The dialogue box border and background		* The dialogue box border and background
Line 7:		Line 7:
	* Boss transition wipe		* Boss transition wipe
	* A few other effect during cutscenes		* A few other effect during cutscenes
	** (TODO: which one?)
	* (TODO: check that I forgot none)


Line 14:		Line 12:
	The 3D engine is capable of rendering in 2D, simply by rendering rectangle in front of the virtual camera, which is what EoS always does. The way this game work is by first buffering the elements to render to a buffer and then a function will submit those to render (probably during VBlank), which will then take effect on the next frame.		The 3D engine is capable of rendering in 2D, simply by rendering rectangle in front of the virtual camera, which is what EoS always does. The way this game work is by first buffering the elements to render to a buffer and then a function will submit those to render (probably during VBlank), which will then take effect on the next frame.

	The 3D ~~engine~~ can only render on the main screen, which in EoS is the bottom screen. Some game (but not EoS) render on both screen by switching the main screen every frame, dividing by two the ~~framerate~~ from 60 to 30 FPS.		The DS 3D hardware can only render on the main screen, which in EoS is the bottom screen. Some game (but not EoS) render on both screen by switching the main screen every frame, dividing by two the frame rate from 60 to 30 FPS.

	~~=== Memory ===~~
	The bank D is dedicated to store the textures used for the 3D render, and bank F is used to store the palettes. Bank D is 128KiB large, and bank F is 16KiB large. The game seems to mostly allocate texture on a multiple of 1KiB, and palette on a multiple of 0x100B, but there it is possible to perform allocation not aligned on those arbitrary values (but it still (maybe, untested) need to be 4-bytes aligned).


			=== Memory management ===
			The bank D is dedicated to storing the textures used for the 3D render, and bank F is used to store the palettes. Bank D is 128KiB large, and bank F is 16KiB large. The game seems to mostly allocate texture on a multiple of 1KiB, and palette on a multiple of 0x100 bytes, thought it is possible to perform allocation not aligned on those arbitrary values (but it still (maybe, untested) need to be 4-bytes aligned).

	The game store its 3D data in WTE files. It contain the texture and the palette, but not where the file will be stored in the RAM, which is specified in the game’s code. Here is table of the (known) allocation the game make. It is probably exhaustive.		The game store its 3D data in WTE files. It contain the texture and the palette, but not where the file will be stored in the RAM, which is specified in the game’s code. Here is table of the (known) allocation the game make. It is probably exhaustive.

	ProcessWTE is the function used to load them (on EU).		ProcessWTE is the function used to load them (function address is for EU ROM, but palette and texture allocation have no reason to be different).
	{\| class="wikitable"		{\| class="wikitable"
	\|+		\|+
Line 87:		Line 83:
	\|0x400		\|0x400
	\|0x200		\|0x200
	\|which one depend on language		\|which one is loaded depend on language
	\|-		\|-
	\|c_wipe.wte or w_wipe2.wte		\|c_wipe.wte or w_wipe2.wte
Line 100:		Line 96:
	\|w_heart.wte		\|w_heart.wte
	\|		\|
	\|multiple hearts ~~sumbol~~, filled and shaded		\|multiple hearts symbol, filled and shaded
	\|0x0206b000		\|0x0206b000
	\|		\|
Line 127:		Line 123:
	\|d04p31t1.wte		\|d04p31t1.wte
	\|overworld		\|overworld
	\|waterfall cave diamond ~~wave~~		\|big wave of the waterfall cave diamond
	\|overlay_11::02314b9c		\|overlay_11::02314b9c
	\|0x0		\|0x0
Line 153:		Line 149:
	\|		\|
	\|-		\|-
	\|frameX.wte (where X is ~~from~~ 0 to 4)		\|frameX.wte (where X is between 0 to 4)
	\|both		\|both
	\|dialog box frame		\|dialog box frame
Line 189:		Line 185:
	\|		\|
	\|}		\|}
	~~From~~ those allocations, it seems that VRAM from 0x11000 to 0x1EFFF (included) are free to be used both in overworld and dungeon. For the palette, it seems everything from 0x300 to 0x13FF (included) are unused.		Based on those allocations, it seems that VRAM from 0x11000 to 0x1EFFF (included) are free to be used both in overworld and dungeon. For the palette, it seems everything from 0x300 to 0x13FF (included) are unused.

	==== Loading texture ====		==== Loading texture ====
	Once you have your texture in the WTE format saved in the rom, you need to call a function to load WTE ('''LoadWteFromRom''') and then copy stuff to RAM with '''ProcessWTEWrapper''', and then call another (unnamed) function '''DoSomethingOn3dAllocAndClearInput'''.		Once you have your texture in the WTE format saved in the rom, you need to call a function to load WTE ('''LoadWteFromRom''') and then copy stuff to RAM with '''ProcessWTEWrapper''', and then call another (unnamed in pmdsky-debug) function '''DoSomethingOn3dAllocAndClearInput'''.

Marius851000: /* Memory */

2024-06-26T16:22:31Z

Memory

← Older revision		Revision as of 16:22, 26 June 2024
Line 95:		Line 95:
	\|		\|
	\|0x8000		\|0x8000
	\|		\|0x0
	\|		\|
	\|-		\|-
Line 104:		Line 104:
	\|		\|
	\|0x2000		\|0x2000
	\|		\|0x100
	\|		\|
	\|-		\|-
Line 113:		Line 113:
	\|		\|
	\|0x2000		\|0x2000
	\|		\|0x200
	\|		\|
	\|-		\|-
Line 122:		Line 122:
	\|0x8000		\|0x8000
	\|0x8000		\|0x8000
	\|		\|0x100
	\|		\|
	\|-		\|-
Line 131:		Line 131:
	\|0x0		\|0x0
	\|0x4800		\|0x4800
	\|		\|0x0
	\|		\|
	\|-		\|-
Line 140:		Line 140:
	\|0x0		\|0x0
	\|0x8000		\|0x8000
	\|		\|0x0
	\|		\|
	\|-		\|-
Line 150:		Line 150:
	\|0x0		\|0x0
	\|0x6000		\|0x6000
	\|		\|0x0
	\|		\|
	\|-		\|-
Line 168:		Line 168:
	\|0x0		\|0x0
	\|0x4000		\|0x4000
	\|		\|0x0
	\|		\|
	\|-		\|-
Line 177:		Line 177:
	\|0x4000		\|0x4000
	\|0x4000		\|0x4000
	\|		\|0x100
	\|		\|
	\|-		\|-
Line 186:		Line 186:
	\|0x0		\|0x0
	\|0x6000		\|0x6000
	\|		\|0x0
	\|		\|
	\|}		\|}
	From those allocations, it seems that VRAM from 0x11000 to 0x1EFFF (included) are free to be used both in overworld and dungeon. (~~todo: check palette more precisely~~)		From those allocations, it seems that VRAM from 0x11000 to 0x1EFFF (included) are free to be used both in overworld and dungeon. For the palette, it seems everything from 0x300 to 0x13FF (included) are unused.

			==== Loading texture ====
			Once you have your texture in the WTE format saved in the rom, you need to call a function to load WTE ('''LoadWteFromRom''') and then copy stuff to RAM with '''ProcessWTEWrapper''', and then call another (unnamed) function '''DoSomethingOn3dAllocAndClearInput'''.

Marius851000: More info on the table.

2024-06-26T16:14:14Z

More info on the table.

← Older revision		Revision as of 16:14, 26 June 2024
Line 23:		Line 23:
	The game store its 3D data in WTE files. It contain the texture and the palette, but not where the file will be stored in the RAM, which is specified in the game’s code. Here is table of the (known) allocation the game make. It is probably exhaustive.		The game store its 3D data in WTE files. It contain the texture and the palette, but not where the file will be stored in the RAM, which is specified in the game’s code. Here is table of the (known) allocation the game make. It is probably exhaustive.

	ProcessWTE is the function used to load them.		ProcessWTE is the function used to load them (on EU).
	{\| class="wikitable"		{\| class="wikitable"
	\|+		\|+
Line 91:		Line 91:
	\|c_wipe.wte or w_wipe2.wte		\|c_wipe.wte or w_wipe2.wte
	\|		\|
	\|		\|horizontal bar of differing colors, presumably for wiping the screen
	\|0x0206afb0		\|0x0206afb0
	\|		\|
Line 100:		Line 100:
	\|w_heart.wte		\|w_heart.wte
	\|		\|
	\|		\|multiple hearts sumbol, filled and shaded
	\|0x0206b000		\|0x0206b000
	\|		\|
Line 109:		Line 109:
	\|circle.wte		\|circle.wte
	\|		\|
	\|		\|hearth symbol, not filled
	\|0x0206b050		\|0x0206b050
	\|		\|
Line 118:		Line 118:
	\|s13p01t1.wte		\|s13p01t1.wte
	\|overworld		\|overworld
	\|		\|boss wipe graphic
	\|overlay_11::02316d4c		\|overlay_11::02316d4c
	\|0x8000		\|0x8000
	\|		\|0x8000
	\|		\|
	\|		\|
Line 127:		Line 127:
	\|d04p31t1.wte		\|d04p31t1.wte
	\|overworld		\|overworld
	\|		\|waterfall cave diamond wave
	\|overlay_11::02314b9c		\|overlay_11::02314b9c
	\|0x0		\|0x0
Line 136:		Line 136:
	\|v15p03t1.wte		\|v15p03t1.wte
	\|overworld		\|overworld
	\|		\|Some crystal cave crystals
	\|overlay_11::02314d20		\|overlay_11::02314d20
	\|0x0		\|0x0
	\|		\|0x8000
	\|		\|
	\|		\|
Line 145:		Line 145:
	\|p03p01t1.wte		\|p03p01t1.wte
	\|overworld		\|overworld
	\|		\|fog/mist texture
	\|overlay_11::02314eec		\|overlay_11::02314eec
			overlay_11::022f33d8
	\|0x0		\|0x0
	\|		\|0x6000
	\|		\|
	\|		\|
Line 154:		Line 155:
	\|frameX.wte (where X is from 0 to 4)		\|frameX.wte (where X is from 0 to 4)
	\|both		\|both
	\|		\|dialog box frame
	\|0x020274e4		\|0x020274e4
	\|0x1F000		\|0x1F000
Line 163:		Line 164:
	\|t01p01t1.wte		\|t01p01t1.wte
	\|overworld		\|overworld
	\|		\|some clouds
	\|overlay_11::022f3368		\|overlay_11::022f3368 (loading weather 1)
	\|0x0		\|0x0
	\|		\|0x4000
	\|		\|
	\|		\|
Line 172:		Line 173:
	\|t01p01t2.wte		\|t01p01t2.wte
	\|overworld		\|overworld
	\|		\|some clouds
	\|overlay_11::022f3394		\|overlay_11::022f3394 (loading weather 1)
			\|0x4000
	\|0x4000		\|0x4000
	\|
	\|
	\|
	\|-
	~~\|p03p01t1.wte~~
	~~\|overworld~~
	\|
	~~\|overlay_11::022f33d8~~
	~~\|0x0~~
	\|
	\|		\|
	\|		\|
Line 190:		Line 182:
	\|d73p41t1.wte		\|d73p41t1.wte
	\|overworld		\|overworld
	\|		\|another kind of mist/fog (top of Shaymin mountain?)
	\|overlay_11::022f341c		\|overlay_11::022f341c (loading weather 3)
	\|0x0		\|0x0
	\|		\|0x6000
	\|		\|
	\|		\|
	\|}		\|}
			From those allocations, it seems that VRAM from 0x11000 to 0x1EFFF (included) are free to be used both in overworld and dungeon. (todo: check palette more precisely)

Marius851000: /* Memory */ minor spelling

2024-06-26T15:51:43Z

Memory: minor spelling

← Older revision		Revision as of 15:51, 26 June 2024
Line 11:		Line 11:


	The 3D engine is ~~totally~~ capable of rendering in 2D, simply by rendering rectangle in front of the virtual camera, which is what EoS always does. The way this game work is by first buffering the ~~things~~ to render to a buffer and then a function will submit those to render (probably during VBlank), which will then take effect on the next frame.
			The 3D engine is capable of rendering in 2D, simply by rendering rectangle in front of the virtual camera, which is what EoS always does. The way this game work is by first buffering the elements to render to a buffer and then a function will submit those to render (probably during VBlank), which will then take effect on the next frame.

	The 3D engine can only render on the main screen, which in EoS is the bottom screen. Some game (but not EoS) render on both screen by switching the main screen every frame, dividing by two the framerate from 60 to 30 FPS.		The 3D engine can only render on the main screen, which in EoS is the bottom screen. Some game (but not EoS) render on both screen by switching the main screen every frame, dividing by two the framerate from 60 to 30 FPS.
Line 20:		Line 21:


	The game store ~~it’s~~ 3D data in WTE files. It contain the texture and the palette, but not where the file will be stored in the RAM, which is specified in the game’s code. Here is table of the (known) allocation the game make. It is probably exhaustive.		The game store its 3D data in WTE files. It contain the texture and the palette, but not where the file will be stored in the RAM, which is specified in the game’s code. Here is table of the (known) allocation the game make. It is probably exhaustive.

	ProcessWTE is the function used to load them.		ProcessWTE is the function used to load them.

Marius851000: First version of Memory use table

2024-04-14T17:33:34Z

First version of Memory use table

Show changes

Marius851000: Initial page creation

2024-04-14T17:15:31Z

Initial page creation

New page

== 3D Rendering engine ==
The Nintendo DS dispose of hardware that can perform 3D rendering in addition to it’s dedicated 2D system. EoS mostly use the 2D system, but occasionally make use of the 3D engine for some effects. Those are:

* The dialogue box border and background
* Rendering of the quick status at the top of the bottom screen during a dungeon
* The various weather effect
* Boss transition wipe
* A few other effect during cutscenes
** (TODO: which one?)
* (TODO: check that I forgot none)

The 3D engine is totally capable of rendering in 2D, simply by rendering rectangle in front of the virtual camera, which is what EoS always does. The way this game work is by first buffering the things to render to a buffer and then a function will submit those to render (probably during VBlank), which will then take effect on the next frame.

The 3D engine can only render on the main screen, which in EoS is the bottom screen. Some game (but not EoS) render on both screen by switching the main screen every frame, dividing by two the framerate from 60 to 30 FPS.

=== Memory ===
The bank D is dedicated to store the textures used for the 3D render, and bank F is used to store the palettes. Bank D is 128KiB large, and bank F is 16KiB large. The game seems to only allocate texture on a multiple of 1KiB, and palette on a multiple of 0x100B, but there it is possible to perform allocation not aligned on those arbitrary values (but it still (maybe, untested) need to be 4-bytes aligned).

TODO: