Changes

[[Category:File formats]]

[[Category:File formats]]

The SHBIN (SHader BINary) file is used to contain compiled and linked shader programs. These can include vertex shaders (typically compiled from .vsh files) and geometry shaders (typically compiled from .gsh files, though .asm have been observed).

The SHBIN (SHader BINary) file is used to contain compiled and linked shader programs. These can include vertex shaders (typically compiled from .vsh files) and geometry shaders (typically compiled from .gsh files, though .asm have been observed). In commercial applications, SHBIN files can be found as standalone files with the extension .shbin, or contained within .bcsdr files. BCSDR files use CGFX as a container, but the underlying DVLB/DVLP/DVLE structure remains unchanged.

In commercial games/apps, SHBIN files can be found as standalone files with the extension .shbin, or contained within .bcsdr files. BCSDR files use CGFX as a container, but the underlying DVLB/DVLP/DVLE structure remains unchanged.

A SHBIN's structure starts with a header, then a DVLP, then DVLE(s).

A SHBIN's structure starts with a generic header (DVLB), then a single program header (DVLP), then DVLE(s). The program header specifies the generic parts of the shader, i.e. the shader program data, the operand descriptor data, and a filename symbol table. The contextual details (entry point, constant values, debug symbols, etc) are specified in an executable header (DVLE). There may be multiple DVLE headers, so in this sense multiple shaders sharing the same program code can be stored in a single SHBIN. Hence for the following note the distinction between "program" and "executable".

== DVLB Header ==

 

== Header ==

{| class="wikitable" border="1"

{| class="wikitable" border="1"

|  0x8

|  0x8

|  0x4

|  0x4

|  Program's main offset in binary blob (in words)

|  Executable's main offset in binary blob (in words)

|-

|-

|  0xC

|  0xC

|  0x4

|  0x4

|  Program's endmain offset in binary blob (in words)

|  Executable's program's endmain offset in binary blob (in words)

|-

|-

|  0x18

|  0x18

|}

|}

Label table entry :

=== Label Table Entry ===

{| class="wikitable" border="1"

{| class="wikitable" border="1"

|-

|-

|}

|}

Constant table entry header :

=== Constant Table Entry ===

 

Each executable's constants are stored as in constant uniform table. This information is used by ctrulib's SHDR framework to automatically send those values to the GPU when changing to a given program. An entry is constituted by a header and the constant data, the latter of which uses a format specific to the constant type.

{| class="wikitable" border="1"

{| class="wikitable" border="1"

|  0x0

|  0x0

|  0x1

|  0x1

|  Constant type

|  Constant type (0=bool, 1=ivec4, 2=vec4)

|-

|-

|  0x2

|  0x2

|}

|}

Corresponding constant entry formats:

 

Corresponding constant entry formats :

{| class="wikitable" border="1"

{| class="wikitable" border="1"

|}

|}

Output register table entry:

=== Output Table Entry ===

{| class="wikitable" border="1"

{| class="wikitable" border="1"

|-

|-

|}

|}

Uniform table entry :

=== Uniform Table Entry ===

{| class="wikitable" border="1"

{| class="wikitable" border="1"

|-

|-

|-

|-

|}

|}