AL_SET_SHADER_INT_VECTOR(3)
π al_set_shader_int_vector(3) π
okay bestie, this page comes from the Library Functions Manual, and itβs all about al_set_shader_int_vector from the Allegro 5 API. pull up a chair, weβre doing shader uniforms today π
β¨
πΈ NAME πΈ
al_set_shader_int_vector β Allegro 5 API. literally the function for setting an integer vector array uniform, no cap π«Ά
β¨ SYNOPSIS β¨
#include <allegro5/allegro.h>
bool al_set_shader_int_vector(const char *name,
int num_components, const int *i, int num_elems)
π DESCRIPTION π
okay so this function sets an integer vector array uniform of the current target bitmapβs shader. The num_components parameter can take one of the values 1, 2, 3 or 4. If it is 1 then an array of num_elems integer elements is added. Otherwise each added array element is assumed to be a vector with 2, 3 or 4 components in it. slay π
for example, if you have a GLSL uniform declared as uniform ivec3 flowers[4] or an HLSL uniform declared as uniform int3 flowers[4], then youβd use this function from your code like so:
int flowers[4][3] =
{
{1, 2, 3},
{4, 5, 6},
{7, 8, 9},
{2, 5, 7}
};
al_set_shader_int_vector("flowers", 3, (int*)flowers, 4);
returns true on success. Otherwise returns false, e.g. if the uniform by that name does not exist in the shader. not me checking the return value every single time πβ¨
π SINCE π
5.1.0 β sheβs been here, okay? iconic behavior π
π¦ SEE ALSO π¦
cute little sign-off: from the Allegro reference manual, page al_set_shader_int_vector(3) β source is the Allegro reference manual, page is al_set_shader_int_vector(3), and the footer did not give me a date, so no invented date bestie, just vibes and a little kiss ππ
π¦ where this page comes from
- arch rolling: allegro 5.2.11.3-2 Β· Zlib AND BSD-3-Clause AND OFL-1.1 AND LicenseRef-Custom
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms