OpticalFlowTOP stuck when 32 bit texture input

2025.30060 Experimental — didn’t test on previous versions

Having a 32bit float texture input to the opticalflowTOP causes zero output.
Interestingly, connecting a “fresh” optical flow to an 8 bit texture, and then connecting to a 32 bit texture the error doesn’t happen, output is as expected. Connecting an already bugged optflow to an 8 bit texture doesn’t unstuck it however.

Hi @function.store,

thanks for sending this in, it’s confirmed and we are having a look.

cheers
Markus

1 Like