Jonathan Mack

Benjamin Lemoine
the develloper suggested that maybe those are packed …
and wrote :
packed = 11387939
red = packed & 0x0000FF
green = (packed & 0x00FF00) / (1<<8)
blue = (packed & 0xFF0000) / (1<<16)
but i'm not sure i could do this in vex…

int packed = 11387939;
int red = packed & 255;
int green = (packed & 65280)/shl(1, 8);
int blue = (packed & 16711680)/shl(1,16);
@Cd = set(red,green,blue)/255.0;

int packed = 11387939;
int red = packed & 255;
int red = packed & 255;
int green = shrz(packed & 65280, 8);
int blue = shrz(packed & 16711680,16);
@Cd = set(red,green,blue)/255.0;

int packed = i@packedcolor;
int red = packed & 255;
int green = shrz(packed & 65280, 8);
int blue = shrz(packed & 16711680,16);
int alpha = shrz(packed & -16777216,24);
alpha = select(alpha<0, alpha+256, alpha);
@Cd = set(red,green,blue)/255.0;
@mask = alpha/255.0;

int @packedcolor;
float r,g,b;
int red,green,blue,alpha;
assign(r,g,b,@Cd*255.0);
red = (int)r;
green = (int)g;
blue = (int)b;
alpha = (int)rint(@mask*255.0);
green = shl(green, 8);
blue = shl(blue, 16);
alpha = shl(alpha, 24);
@packedcolor = red | green | blue | alpha;

malbrecht
> Why not leave the scale alone in houdini, it would make round tripping a lot cleaner

… well, scaling of other assets for sure is one reason, but most importantly, simulation usually requires “more or less natural” scales. The moment you want to sim cloth, destruction etc, your scale needs to be “sane”.
Then, measuring comes to mind. If you're not “eye-balling” your stuff but have to deliver correct-ish results (I used to do animations for documentation back in the days, before my Houdini times), you may have pre-established camera extrinsic and intrinsic, so that you need to “stay in focus” (pun intended). Not sure if something like that is “a thing” for game engines, not my area of expertise.

But in general, I wouldn't like to work in the wrong scaling. Ever. :-)


Marc