murphy
murphy
In my opinion, it should set the frame range to db record. It fails because it does not match, the fix should match it. I would not go too deep...
do I need to redo the test?
where is the global file format taken from? 
From my point of view, the wording is actually opposite. OP settings is set to TIFF Render Globals is set to TIFF Beauty AOV is set OpenExr Cryptomatte is set...
think so, . . 
run the command  but the publish ended with exactly the same error :(
> > [look with textures extracted and published successfully](https://github.com/pypeclub/OpenPype/pull/2971#pullrequestreview-1097251132) > > @m-u-r-p-h-y - Shouldn't that produce `.rstexbin` files with this PR instead of `.tx` files? > > Did you enable...
> I agree that we need to specify format, but we'll need to add in the future validators to deal with unsupported features enabled on existing render instance - for...
> Would that be ideal? To have that toggle on the instance? we have this currently  and it is not ideal definitely
The question is if we should not use the Draft plugin for assembling tiled renders by default, as it is not paid feature anymore.  Instead of maintaining OpenPypeTileAssembler ....