2.2.0.51807 bugs

Haven’t checked these against 2.1.x, just stuff I jotted down while testing at the airport going to SIGGraph.

  1. InputChannel[ID] doesn’t debug correctly when precision is not default. Something about the int to float conversion?

  2. At least with a PRT Loader (haven’t checked other objects), Normals (at least the display, didn’t debug the actual values) don’t work with XForm. I was trying to convert a PRT from Y-up to Z-up. :slight_smile:

  3. Error when saving float Age and Lifespan.

Wishlist item: Modifier key alternative for Active Type to add tools to inputs, not outputs. For those of us that tend to build from output to input. Just an idea.

Got it, Integer values should not be passed through the same formatted print as floats. Will fix.
EDIT: Fixed internally.

Can we have steps to reproduce please?

What are you saving? When I save a PFlow, Age and Lifespan save as expected.

It won’t be trivial (I would not expect it for 2.2), but I will log it as a Wish List item.

Thanks for the feedback!

PRT Loader with normals, set to display normals, added a XForm, rotated the gizmo. As soon as I rotate it, the particles disappear. EDIT: Don’t need to rotate it. As soon as the XForm evaluates the particles disappear, even if the transform is identity.

I was using a MagmaFlow to convert the integer Age and Lifespan from an existing PRT sequence into normalized float values. I’ll see if I can get the error again.
EDIT: OK, I have no idea what I was doing, as I can’t set the Age channel to float at all.

Reproduced with any modifier (e.g. Bend). The values appear ok though (according to PDV).

In the latest builds, Age and Lifespan are both Floats natively. If you load a PRT sequence where the Age or Lifespan were saved as Integers, they will load as Floats automagically. In my Magma (v2.2.0), setting the Output channel to Age provides only float32[1] as option. So there is no need to convert the Age and Lifespan input channels to floats in that version anymore, they always are floats, and you cannot use Integers even if you wanted to.
Are you seeing something different?

D’oh! I had rolled back to 2.1.x anyway, that’s why I didn’t see the error (or the float channels). I’ll put 2.2 back and see if it happens.