I told you that requiring us to change all of our workflow with sprites to fit into 16,32,64 and 128 isn't very pratical..
Imagine if i had to rework and resize all sprites i make and clients send me just to fit those sizes?The first suggestion he said here totally will handle my issue with sprites size.
Thanks! Wakawakamush :)
I haven't had many complaints about this before, but I'll definitely take it into consideration for the next update. Many thanks!
The current system relies on square images for simplicity because each pixel needs to align across the orthogonal views to generate a voxel. If the pixel positions don't match, the app can't determine where to place the geometry in 3D space.
Just to get a bit more context—what image dimensions do you usually work with?
I need to think through this carefully and do some testing. I imagine an extreme non-square aspect ratio (like 1:10) might cause issues. Similarly, if the side images have different dimensions from each other, it will be hard for the system to build the model accurately.
Do you also need to be able to use images with different dimensions for each side?
I'll test this out and let you know what I find!
Thanks again :)
To keep things simple, keep the predetermined sizes for the grid (users don't really care about this), but add an option to align the images uploaded? Then also do that filling in the space with empty pixels internal change I mentioned and the app should accept them just fine.
So, that way you keep everything the same (internally) and the user just has to tweak the images positions to have the right results when creating the mesh from multiple images?
