| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We were incorrectly computing the buffer offset when using the
instances. The buffer offset is always equal to:
start_instance * stride + (instance_num / instance_divisor) *
stride
We were completely ignoring the start instance quite
often producing instances that completely wrong, e.g. if
start instance = 5, instance divisor = 2, then on the first
iteration it should be:
5 * stride, not (5/2) * stride as we'd have currently, and if
start instance = 1, instance divisor = 3, then on the first
iteration it should be:
1 * stride, not 0 as we'd have.
This fixes it and adjusts all the code to the changes.
Signed-off-by: Zack Rusin <[email protected]>
|
| |
|
| |
|
|
|
|
|
| |
Currently, only 32-bit indices are supported, but some use cases
translate needs support for all types.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently translate asserts on unsupported output formats, making
it impossible to use for some purposes, such as testing whether it
actually works on all formats it supports.
Removing the assert was met with opposition, so this change allows
clients to ask whether an output format is supported, and they are thus
able to avoid attempting to use it.
Since this is just an addition to the API, no adverse effect is
possible, and it makes the testsuite work again.
|
| |
|
|
|
|
| |
It's all screaming for integer support -- fake it with float for now.
|
| |
|
|
|
|
|
| |
Modify the translate module to respect instance divisors and accept
instance id as a parameter to calculate input vertex offset.
|
|
|
|
| |
Sizes of translate keys must also match.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
It's quite a big struct & we examine it a lot (too much). Reduce
the impact of this by just looking at the active part where possible.
|
| |
|
| |
|
|
|
|
|
| |
Will eventually do this for all instances where we are converting vertices
from one format to another.
|
|
|