MartinusMagneson's picture

Magneson (@MartinusMagneson)

MartinusMagneson's picture

Setting the date for the comparison seems to fix it. It might be that discarding the date component also discards the daylight savings correction. You might want to file a bug report.

This workaround should fix the issue:

MartinusMagneson's picture

Weird, I can reproduce it here as well. Might be a daylight savings issue?

MartinusMagneson's picture

No stress! It is a bit of a different thought process. The coordinate system makes a lot more sense both mathematically and when you do 3d manipulations/work in 3d environments. Coming from pixel space and 0 - 1 / Width - Height space to that can be a bit of a shift though! I have ripped out a fair few hairs when transitioning to this kind of workflow myself. As it is standard for most applications in 3d space I guess it's just a matter of getting to grips with it.

(Also left you an answer there ;) )

MartinusMagneson's picture

Try removing the start of day input and leave it at 0.

MartinusMagneson's picture

Much easier to use the "Get Layer Bounds" node! :)

Pages