AWS Thinkbox Discussion Forums

3ds Max Draft Stitcher bad overlap

If you set the overlap to > 0 it doesn’t actually overlap properly it just offsets by X pixels.

I’ll poke Grant and Bobo to get their thoughts.

Thanks!
Ryan

Hey Gavin,

Do you have a scene or some steps to reproduce I do not seem to be able to.

Grant

Hi Gavin,
Post shipping Deadline v6.1 version, we released some updated SMTD scripts which fixed a number of issues, which this sounds like one of them. On the BOX Deadline software v6.1 download link, there is a zip file containing some patched maxscript files for SMTD. The usual overwrite the files on the repo, make sure you restart all copies of 3dsMax running, etc - applies here.
As a side note, if you still have this issue once using the newer version of the SMTD scripts, could you please try deleting any saved Jigsaw regions in your Max scene/camera and re-creating them? There might still be one very obscure edge case between the un-patched & patched versions and upgrading between them, causes a possible issue with pre-existing Jigsaw regions. I’d love to know if this is the case for you. I think it will be very hard to solve and the easiest thing is just to delete any regions and start creating them again, but still, I’d like to know for peace of mind :slight_smile:
Cheers,
Mike

I don’t have time to test it out now, and I’ll probably forget by the time I can come back to it but I am using the 6.2 SMTD so shouldn’t that be up to date?

Also attached are the two jobs I used (delete when done please).

Hey Gavin,
So I haven’t been able to find anything wrong with that scene yet, do you have an steps that I could follow to get a minimalist example of this bug.

Grant

Hey Gavin,

So we found out what was going on with this, the regions that were being made aren’t being cropped properly and are thus being placed improperly. Ryan is going to look into Lightning to see why they aren’t being cropped.

Grant

And a little more detail for this. It is happening because of how we are saving through vray’s frame buffer, which is not cropping the images. We are looking into ways of fixing this but are not sure of what it is possible to do at the moment. For work arounds, setting the pixel padding to 0, or saving without using vray’s frame buffer will both work (probably not optimal for either).

Grant

Hmmm, glad you found the source. However just a note I don’t think I was using the Vray VFB when it occured so I think it’s broader than just vray. I agree with your indictment of the padding setting though.

Privacy | Site terms | Cookie preferences