(Bug: Polaris) Submit to deadline defaults to input 1-1 for some reason

[lamepennies]

Dupe Check

• [X] I have searched Juno's bugs and there are no duplicates

Serivce this pertains to.

Polaris

URL in Hubble.

https://ath.junovfx.com/viewer/janice/

Browser

Chrome Based

Describe the bug

When I submit to deadline, I have to change it to global range.

To reproduce

In the juno write node, hit submit to deadline

Expected behavior

No response

Screenshots

Regression

No, this bug or issue has existed throughout my experience using Orion

Recent working Orion date

No response

Does this block you from using Orion daily?

No

[skeleturtle]

@lamepennies I noticed this too and will look into it tomorrow evening. Should be a quick fix.

[skeleturtle]

@lamepennies

Something odd seems to be happening here with ATH, that I can't 100% pinpoint and it may actually be something with Nuke 15.

1. Write node juno local render button runs standard nuke render execute call. On ATH this is resulting in the input being set 1-1 even though it is not.
2. Submit to deadline I using the node.firstFrame() and node.lastFrame() calls These provide the first and last frame in range of the given node. In most instances on ATH I am getting the expected 1-59 on my sot test case. however sometimes when going through x_denoise its 1-100.
3. I launched SQM which is also nuke 15, and I don't seem to have either issue happening. both local render and submit to deadlines input looks to return the expected frame range. With and without x_denoise in the network. EDIT** Correction, I do notice a difference on SQM when using x_denoise in some instances.

I would like to keep this open, and run some more tests on projects outside of ATH and potentially nuke 14 as well since I appear to be getting inconsistent results.

[lamepennies]

If I run a precomp, it displays fine. Weird, right?

[ddesmond]

What about updating to nuke 15.1?