Wishgranter wrote:
Hi Castlenock
and when you use FIXED TEXEL size and set the OPTIMAL TEXEL VALUE in UNWRAP tool ( recalculate UVs ) its get in same issue ?
Please, let me know. If not could you upload the whole dataset so i can process it here for you ?
Wishgranter,
You’re the best! Yes, when I used fixed and set optimal to the best value, unwrapped and tried to texture I got the same error.
I’m still not-where-I-normally-am and make a physical move next week so am starting to prepare for that - getting the dataset up would be difficult, but not impossible (I’ll ask the local university I was on contract with to use their pipe, my upload pipe is laughable). I’ve started a high reconstruction with 2 GPUs (and a proper power supply) that bugged out after hour 20 and think it salvaged about 20% of that render… If I get another high-recon off of the initial alignment by tmrw morning CST I can try texturing from that, and if it doesn’t work I’ll chase you up for potentially looking at the data set. (That’s such a gracious gesture and I hope not to take you up on it).
Even though it’s an RC error and my image, RC, and other data sets weren’t on the drives, I’m sure my ‘SDD and HDD Backup Drive Apocalypse, 2017’ fiasco is at the root of the issue. Are there any suggestions on making sure RC is completely re-installed and that there is no residual references to the installation of the program anywhere in a Windows 10 OS? While the content was on a stable drive, RC’s installation drive was on one of the failed drives.