diff options
| author | Adrian Kummerlaender | 2018-12-16 23:46:32 +0100 |
|---|---|---|
| committer | Adrian Kummerlaender | 2018-12-16 23:46:32 +0100 |
| commit | dc69fab1565659241eb6f2f3576076872e86c45e (patch) | |
| tree | 43fc7857250637261b45e6d17ba025b4f60b719c /src/buffer/vertex | |
| parent | ce334547f0f0560386ca8b97f354d83da68019a5 (diff) | |
| download | compustream-dc69fab1565659241eb6f2f3576076872e86c45e.tar compustream-dc69fab1565659241eb6f2f3576076872e86c45e.tar.gz compustream-dc69fab1565659241eb6f2f3576076872e86c45e.tar.bz2 compustream-dc69fab1565659241eb6f2f3576076872e86c45e.tar.lz compustream-dc69fab1565659241eb6f2f3576076872e86c45e.tar.xz compustream-dc69fab1565659241eb6f2f3576076872e86c45e.tar.zst compustream-dc69fab1565659241eb6f2f3576076872e86c45e.zip | |
Filter weird origin vertex
The same thing occurs in computicle. I suspect some initialization /
compute shader invokation problem. On the other hand: Why would that
happen for the origin vertex and not e.g. the first or last vertex
in memory? To be investigated further.
Diffstat (limited to 'src/buffer/vertex')
0 files changed, 0 insertions, 0 deletions