doue1925 2017-06-27 22:20
浏览 113
已采纳

为什么golang gomobile基本示例为vec4属性设置3浮点大小?

Golang gomobile basic example [1] uses VertexAttribPointer to set 3 x FLOATS per vertex.

However the vertex shader attribute type is vec4. Shouldn't it be vec3?

Why?

Within render loop:

glctx.VertexAttribPointer(position, coordsPerVertex, gl.FLOAT, false, 0, 0)

Triangle data:

var triangleData = f32.Bytes(binary.LittleEndian,
    0.0, 0.4, 0.0, // top left
    0.0, 0.0, 0.0, // bottom left
    0.4, 0.0, 0.0, // bottom right
)

Constant declaration:

const (
    coordsPerVertex = 3
    vertexCount     = 3
)

In vertex shader:

attribute vec4 position;

[1] gomobile basic example: https://github.com/golang/mobile/blob/master/example/basic/main.go

  • 写回答

1条回答 默认 最新

  • doujinge9648 2017-06-28 20:21
    关注

    Vertex attributes are conceptually always 4 component vectors. There is no requirement that the number of components you use in the shader and the one you set up for the attribute pointer have to match. If your array has more components than your shader consumes, the additional components are just ignored. If your array supplies less components, the attribute is filled to a vector of the form (0,0,0,1) (which makes sense for homogeneous position vectors as well as RGBA colors).

    In the usual case, you want w=1 for every input position anyway, there is no need to store that in an array. But you usually need the full 4D form when applying the transformation matrices (or even when directly forwarding the value as gl_Position). So your shader could conceptually do

    in vec3 pos;
    gl_Position=vec4(pos,1);
    

    but that would be equivalent of just writing

    in vec4 pos;
    gl_Position=pos;
    
    本回答被题主选为最佳回答 , 对您是否有帮助呢?
    评论

报告相同问题?

悬赏问题

  • ¥15 如何实验stm32主通道和互补通道独立输出
  • ¥30 这是哪个作者做的宝宝起名网站
  • ¥60 版本过低apk如何修改可以兼容新的安卓系统
  • ¥25 由IPR导致的DRIVER_POWER_STATE_FAILURE蓝屏
  • ¥50 有数据,怎么建立模型求影响全要素生产率的因素
  • ¥50 有数据,怎么用matlab求全要素生产率
  • ¥15 TI的insta-spin例程
  • ¥15 完成下列问题完成下列问题
  • ¥15 C#算法问题, 不知道怎么处理这个数据的转换
  • ¥15 YoloV5 第三方库的版本对照问题