Milan Kolar
Milan Kolar
I remember discussing this at quite some length with a client at the time when this was implemented. The general issue at hand was, how to differentiate between the cases,...
After quite some time in production, I agree that it's probably more intuitive to allow the override anytime, but then the validation of frame range is completely useless
>If that plug-in is optional then it would validate by default unless the Artist would explicitly say "ignore this check for this instance" That's exactly the issue. You can only...
Just a note that we haven't forgotten about this at all, just considering if it can nastily influence anything in production.
Task linked: [OP-2667 Fusion: set framerange from menu button](https://app.clickup.com/t/6658547/OP-2667)
I think what @jakubjezek001 is trying to say is that you are rendering frame range without handles, 1001-1005 in the example, however it should be rendering with handles included for...
>Anyone any pointers on this? :) `%LOCALAPPDATA%/pypeclub/hosts/fusion` is totally reasonable. I'm, however, unable to comment on much of the rest as I'm really not versed in fusion in general.
To be honest I'd be happy to merge this, considering the testing going on in colourbleed. We just need to sort out the conflicts.
I vote for the option 2. There as actually a pseudo version of it in pype 2.x, but it was duplicating the feature of `patched_discover` I believe
Considering we're re-working the settings for v4, I would say this is stale now and can be closed. What do you think @iLLiCiTiT ?