Skip to main content
Game Development

Return to Answer

added 127 characters in body
Source Link
Fibbs
Fibbs
  • 524
  • 2
  • 11

Typically, I've managed to find the answer almost immediately after asking the question.

§8.5.1 TEXTURE IMAGE SPECIFICATION, p201Sized Types Table

...

Implementations are required to support at least one allocation of internal component resolution for each type (unsigned int, float, etc.) for each base internal format.

This seems to say that yesThis seems to say that yes the format is deprecated. It appears the format is not deprecated but is now optional and may not be available on all OpenGL 4.5 implementations. The reason is that only one type (int, float, etc) needs to be supported for each resolution (8, 16, 24, 32, etc).

Typically, I've managed to find the answer almost immediately after asking the question.

§8.5.1 TEXTURE IMAGE SPECIFICATION, p201Sized Types Table

...

Implementations are required to support at least one allocation of internal component resolution for each type (unsigned int, float, etc.) for each base internal format.

This seems to say that yes the format is deprecated. The reason is that only one type (int, float, etc) needs to be supported for each resolution (8, 16, 24, 32, etc).

Typically, I've managed to find the answer almost immediately after asking the question.

§8.5.1 TEXTURE IMAGE SPECIFICATION, p201Sized Types Table

...

Implementations are required to support at least one allocation of internal component resolution for each type (unsigned int, float, etc.) for each base internal format.

This seems to say that yes the format is deprecated. It appears the format is not deprecated but is now optional and may not be available on all OpenGL 4.5 implementations. The reason is that only one type (int, float, etc) needs to be supported for each resolution (8, 16, 24, 32, etc).

Source Link
Fibbs
Fibbs
  • 524
  • 2
  • 11

Typically, I've managed to find the answer almost immediately after asking the question.

§8.5.1 TEXTURE IMAGE SPECIFICATION, p201Sized Types Table

...

Implementations are required to support at least one allocation of internal component resolution for each type (unsigned int, float, etc.) for each base internal format.

This seems to say that yes the format is deprecated. The reason is that only one type (int, float, etc) needs to be supported for each resolution (8, 16, 24, 32, etc).