vkd3d-shader/spirv: Do not write the point size if shaderTessellationAndGeometryPointSize is disabled.
Merge request reports
Activity
It makes a lot of intuitive sense to me, in general, to treat features and extensions the same way. I don't think any better designs occur to me.
Of course, we already started down a different path with shaderStorageImageReadWithoutFormat in 3dbd2cec. I still am not sure that was the best option, but perhaps we should just be consistent...
It makes a lot of intuitive sense to me, in general, to treat features and extensions the same way. I don't think any better designs occur to me.
Of course, we already started down a different path with shaderStorageImageReadWithoutFormat in 3dbd2cec. I still am not sure that was the best option, but perhaps we should just be consistent...
That, but also whether it's really worth it to change the default value of this between releases. Those aren't entirely independent choices, of course; using the extension mechanism makes it a bit awkward to keep this enabled by default like it was in previous versions.
added 107 commits
-
4b04fb7a...68c232cf - 105 commits from branch
wine:master
- 7f928a35 - vkd3d-shader/spirv: Introduce an option to control whether point size is written.
- 2848d7b6 - vkd3d: Do not write the point size for SPIR-V shaders.
-
4b04fb7a...68c232cf - 105 commits from branch