```
+**Effect of Saturation on Vectorised Swizzle**
+
+```
+one thing that occurred to me: we need fmv.swizzle and maybe mvfixed[u].swizzle too (integers where 0.0 maps to 0 and 1.0 maps to the max signed/unsigned integer -- used for fixed-point swizzle such as pixel data -- we need signed ints for efficient bump map support for some programs). the 0.0 and 1.0 constants should map to 0, 1 for mv.swizzle, 0.0, 1.0 for fmv.swizzle, 0, UINT_MAX for mvfixedu.swizzle, and 0, INT_MAX for mvfixed.swizzle.
+
+i like the idea of a SKIP option!
+
+Jacob
+```
+
# RM Mode Concept:
MVRM-2P-1S1D: