- Eddy version: 1.6.1
- Nuke version: 10.5v5
- Operating system: Centos 7
- GPU model: GTX 1080TI
- Graphics driver version:384.59
- Is the bug reproducible? yes
- Steps to reproduce the bug: use frame offset in VDB_Cache
The frame offset parameter behaves opposite to what is expected, that is a negative number will shift the cache later in time when.
E.g. -10 Will make the cache start 10 frames later rather earlier. In Nuke’s TimeOffset node the logic is that you are applying the specified number to the start frame, so a negative n umber will make an element start sooner.
Also, if possible, it would be great to be able to see the VDB_Cache node in the Dope Sheet.