- Mar 05, 2025
-
-
Nikolay Sivov authored
Signed-off-by:
Nikolay Sivov <nsivov@codeweavers.com>
-
Nikolay Sivov authored
Signed-off-by:
Nikolay Sivov <nsivov@codeweavers.com>
-
Nikolay Sivov authored
Signed-off-by:
Nikolay Sivov <nsivov@codeweavers.com>
-
- Mar 03, 2025
-
-
navi authored
While fxc allows full expressions inside the angle brackets, we don't parse that yet as it'd be quite a mess to properly do so with yacc, and I'm not aware of any game doing so in their shaders.
-
navi authored
-
Nikolay Sivov authored
To reproduce: float4 v; SamplerState s { BorderColor = 0.1 + v*0.2; }; Expression should use more than one literal constant, as a scalar in operation that involves a vector. Signed-off-by:
Nikolay Sivov <nsivov@codeweavers.com>
-
Giovanni Mascellani authored
So that they do not get truncated if they're too long.
-
Elizabeth Figura authored
-
Elizabeth Figura authored
-
Elizabeth Figura authored
-
Elizabeth Figura authored
-
Elizabeth Figura authored
-
Francisco Casas authored
The only purpose it has at this point is wrapping integer DIV in casts, which can be moved to lower_division().
-
Francisco Casas authored
Instead, allow half, bool, int, and uint, expressions that map to the same float op to reach sm1_generate_vsir_instr_expr().
-
navi authored
-
- Mar 02, 2025
-
-
Henri Verbeet authored
-
- Feb 26, 2025
-
-
Giovanni Mascellani authored
That extension (and the corresponding feature) must be enabled when the Initializer operand is used for workgroup variables.
-
- Feb 24, 2025
-
-
Nikolay Sivov authored
Signed-off-by:
Nikolay Sivov <nsivov@codeweavers.com>
-
Nikolay Sivov authored
Signed-off-by:
Nikolay Sivov <nsivov@codeweavers.com>
-
Henri Verbeet authored
Instead of "%f". vkd3d_string_buffer_print_f32() will use sufficient precision to represent the stored value exactly, and will use '.' as decimal separator regardless of the current locale.
-
Elizabeth Figura authored
-
Elizabeth Figura authored
-
Elizabeth Figura authored
-
Elizabeth Figura authored
-
Elizabeth Figura authored
The helper is used in one place.
-
Conor McCarthy authored
Besides simply being more compact, this allows the test to cover more shader types, perhaps most notably DXIL.
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
Which incidentally matches the I/O signatures from the DXBC container.
-
Henri Verbeet authored
-
Henri Verbeet authored
vkd3d-shader/dxbc: Output messages for invalid semantic name references in shader_parse_signature().
-
Henri Verbeet authored
Leaving it as 0 mostly ends up doing the right thing in practice, but isn't quite right.
-
- Feb 20, 2025
-
-
Giovanni Mascellani authored
If the root signature wasn't explicitly specified. This fixes a failure in The Touryst.
-
Giovanni Mascellani authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
-
Henri Verbeet authored
The DXIL parser doesn't need them.
-
Henri Verbeet authored
We currently generate our own I/O signatures inside the DXIL parser, but use the element counts from the DXBC container signatures to allocate the input_params/output_params/patch_constant_params arrays. That happens to work for well-behaved inputs, but it's asking for trouble.
-
Henri Verbeet authored
vkd3d-shader/dxbc: Update the vkd3d_shader_parse_input_signature() documentation for dxbc-dxil shaders.
-