ID 572644 - The ScanlineRender2 node does not output Motion Vectors if the shutter_steps knob is set to 0

Problem summary:
The ScanlineRender2 node does not output Motion Vectors if the shutter_steps knob is set to 0
 
Customer reported version:
Nuke 15.0v4
 
Customer reported platform:
Ubuntu
 
Steps to reproduce:
1) Launch Nuke and create a GeoCube node in the Node Graph.
2) Create a ScanlineRender2 node, and a Camera4 node.
3) Adjust the Camera's position so the GeoCube is visible when Viewing the ScanlineRender2 node.
4) Open the GeoCube's Transform Properties tab and add two keyframes to animate one or more knobs, such as Translate X.
5) View the ScanlineRender2, and change the Viewer's current Layer from rgba to forward.
6) In the ScanlineRender2 node's Properties, set the shutter_steps knob to 0, and observe how the Motion Vectors are no longer output:

 
Expected behavior:
The ScanlineRender2 node should be able to output Motion Vectors regardless of the shutter_steps knob value.
 
Actual behavior:
When a ScanlineRender2 node's motion_vectors_type knob is set to Distance or Velocity, the Motion Vectors will not be returned if the shutter_steps knob has been set to 0.
 
Workaround:
No known workaround at this time
 
Reproduced by Support in:
Nuke 15.0v4 - Windows 11, macOS 13 Ventura
Nuke 15.0v1 - Windows 11
Nuke 14.1v4 - Windows 11
Nuke 14.1v1 - Windows 11, macOS 13 Ventura
 
Earliest version tested:
Nuke 14.1v1 - This feature (ScanlineRender2 node's shutter_steps knob) did not exist before this version.