Fixed in Vuo version:
- macOS 10.13
How severely does this bug affect you?:
Steps causing the bug to occur:
This is not "exactly" a bug, but something that limits the usefulness of the new vuo.image.equi.fisheye node. First, thanks for adding this and I've tested it and it performs identically to my shader versions, which is to be expected. However ... the order of rotations is an issue. "Normally" one would want to tilt (latitude), then pan (longitude, about the poles) and then roll. When I suggested the order before perhaps there was some misunderstanding or misdirection on my part, because the order as implemented is the opposite, probably because the order in a shader should be the opposite to which one normally things because it involves a reverse mapping from output vector to input. But, ideally one would be able to choose the order, but I'm not sure how this might be implemented. This applies to the order of rotations of 3D vectors in other nodes as well.