You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by jturnley November 11, 2024
I set up my workflows to use a 2x2 uniform tile layout with each tile slightly larger than 1/4 the size of the final image to improve output quality (i.e. so the model has a better chance of seeing enough of a face to not turn the output into a Lovecraftian horror). When it gets to the 4th tile, rather than being uniform in size, it picks a small section in the bottom right corner and renders that instead. Usually this doesn't cause a problem, because seam fix goes back and fixes it, but occasionally decides something down in that corner is a face or the like because the area is too small for the model to get enough context, and messes up the whole workflow.
Does anyone know, is this a bug, or is there a way around this issue?
The text was updated successfully, but these errors were encountered:
Hello. I was wondering if anyone found a fix for this. I still get this problem where USDU starts rendering a small portion from the edge of the image when the final tile is finished.
Discussed in #116
For reference, my standard image gen size is 512x768, upscaling to 1.5x with 600x800 tiles.
Originally posted by jturnley November 11, 2024
I set up my workflows to use a 2x2 uniform tile layout with each tile slightly larger than 1/4 the size of the final image to improve output quality (i.e. so the model has a better chance of seeing enough of a face to not turn the output into a Lovecraftian horror). When it gets to the 4th tile, rather than being uniform in size, it picks a small section in the bottom right corner and renders that instead. Usually this doesn't cause a problem, because seam fix goes back and fixes it, but occasionally decides something down in that corner is a face or the like because the area is too small for the model to get enough context, and messes up the whole workflow.
Does anyone know, is this a bug, or is there a way around this issue?
The text was updated successfully, but these errors were encountered: