Skeithh
commented
2 hours ago through sheer suffering i have somehow managed to discern that tonight, the "eyes" were causing the issue. The UV sizes of the other parts were not 1:1 with the actual cube's size. These parts weren't causing problems yesterday, but they sure were now! Is there any chance that we can get some sort of error checker that can.. prevent this? Or at least warn you that something is off. I don't know how feasible this is but it would save my life and the lives of 20 other people or so
I've been going insane, wracking my brain what could be causing this. It seems entirely random what the problem item is each time around. One moment its that a UV location is a decimal, the next- god only knows because nothing is different from the last morning that I opened it. Sometimes, at random, some miniscule change I do to a model causes its texture size to inflate from 256x256 to 4096x4096, making the entire file unusable within the cpm editor.
Within blockbench, the file is at 256x256, it only inflates within the context of cpm. What is causing this? what madness has infected my software? There is not a single UV in the file attached that is located on a decimal point. I tried copying over the file piece by piece into a new file, and it appears to just be entirely broken now as each piece triggers the bug, despite everything except for the wings not having caused this problem last night.
Please. I beg of you. I need a solution to this because it keeps affecting Every. Single. One of my models. It's driving me insane.
model_affected.zip