Bifrost : Velocity vertex color set bug.

Bifrost : Velocity vertex color set bug.

Anonymous
Not applicable
1,350 Views
2 Replies
Message 1 of 3

Bifrost : Velocity vertex color set bug.

Anonymous
Not applicable

I have a pretty big issue here. I am using bifrost for the creation of Rivers in a AAA game. The vertex color set that gets applied to the mesh is being used as a flow map. However the is a large problem with this. There is a bug where if all 3 channels (RGB) go into the negitives they all become the same and don't display real XYZ velocities.  Here is a simple test done on water flowing in all directions over a sphere. The colors have been sampled to show their actual values.

Blackchannel.jpgOtherchannel.jpg

 

As you can see any area where all channels pass into the negative makes all channels equal. Any area with just one color positive has varying trust worthy velocity values. This makes the entire vertex color set useless. 

 

This was tested in both 2015 and 2016 ex2.

0 Likes
1,351 Views
2 Replies
Replies (2)
Message 2 of 3

mspeer
Consultant
Consultant

Hi!

 

There seems to be a problem with storing values in the color attribute of the Paint Vertex Color Tool. Do a double click on the color field to open the full color Chooser, then set manual or sample your values. If you choose values for all 3 RGB channels lower than 0 they show up correct in the Color Tool, but if you close the Color Chooser and reopen it all channels got the input from the highest value.

For example: -2 , -4 , -6 will be stored as -2 , -2 , -2. If you choose a Color Chooser from an other color attribute, like the color of a shader these values will be stored correct, so this bug seems to be specific to the Paint Vertex Color Tool ( Tested with Maya 2017, no SP). The colors generated by Bifrost are OK, but the Paint Vertex Color Tool can't store them.

0 Likes
Message 3 of 3

Anonymous
Not applicable

I see. I needed to write a script to compress them in to 0-1 space anyway and it turns out the values sampled in script are correct.

0 Likes