19 Jun
2023
19 Jun
'23
9:13 p.m.
On Mon Jun 19 21:03:09 2023 +0000, Francisco Casas wrote:
Correction, the profile ps_2_1 doesn't exist. I confused it with ps_2_x, which the native compiler doesn't seem to support, unless we pass ps_4_0_level_9_1 or ps_4_0_level_9_3, but those don't support sv_position either, so shader model >= 3, would do. I had to make a change to the test too, because ps_3_0 doesn't add 0.5 to sv_position, like ps_4_0 and ps_5_0.
Right. It's not actually called 2.1. The actual profile is two different profiles, ps_2_a and ps_2_b, which both compile to a version token of 2.1 in the bytecode. I don't know what the difference between a and b is.