Quote from: d3m0n1q_733rz on February 27, 2012, 11:43:36 PM

Why can't you just init as a uint3 in the first place? Did you not change the python init file to handle the uint3 as of yet?

I did change the python init file, but just realized I accidentally set rateDivisor = 3 out of habit, and it's supposed to be 4 since you're supposed to treat uint3 as a uint4. It should work like that, but I'll finish testing tomorrow

You can't init as a uint3 in the first place because there is no definition for a true "uint3" in that sense, it's just a stripped down uint4 (last value is thrown out or used as a placeholder). I'm gonna work on it more tomorrow, but once I get it working this should give a 10% increase over uint2. It only uses ~920 ALUs so far

blandead

Posts

Merits