Sometimes you can do a search for "-1.#QNAN" or "-1.#IND" (without the quotes of course) and just replace with 0.0. It won't bring back stuff, but if you're file is so bad that it crashes on load it can get it back to a point where it'll load back up.
AltusZMH> Think about how the scratches ended up there. Give them a reason and a story. You can't have one continuous scratch going across 270 degree angles unless someone sat down took a sharp object and carefully added them with great detail :)
Hey Rebb, Any chance we can get a clamp feature? The script writes color values outside of the 0.0-1.0 range. This is giving me some serious headache. Trying to use it together with xNormal and it's SBM format for Maya. But I get artifacts due to this. Thanks
EDIT: Missed topic, of course it as a incredible tragedy for everyone and I hope any afflicted the best, impossible to imagine such suffering from any angle. :( There has been a lot great points made regarding it's cause and effect and I don't want to discredit anyone's emotional or mental response by concluding that…
Beware the fans on MSI laptops seem to die early deaths. I have a MSI, the GT62VR Dominator-087 15.6" i7-6700HQ GTX 1070. It's a great box, but three years old now and the fans are dead. Have to use external cooling. Otherwise a decent 3d laptop.
Hey Kodde you said "Those values are defined in 0.0-1.0 space, which maps to 0-255 in photoshop". Those equations returns a single value.But photoshop understand in terms of RGB,hex,HSB. So how would you find a color with just a single value.
Are you using maya ascii? You should since sometimes things like this can be saved. If you are, load in up in a text editor and do a search for "-1.#QNAN" or "-1.#IND" and if you find and replace the each with "0.0". That's not always the problem but it's pretty common in scenes that crash on loading.
I'm going to assume $250 or $270, but they could always put a Sony tax on it and sell it for 300, simply because it would sell out regardless, and probably go for $600 on eBay. Seriously. that said I'm totally getting one day 1, but I really, REALLY hope it's not $300.
I think if you decide to do a hi poly for normal map then jack up the polys on your low poly....1000 tris seems a lil low....u could def go as high as around 10 000 if u wanna do a next gen type character
ok i have the latest drivers , and have mudbox 1.0.7 , at 180 000 polys its perfect no chugginess etc, if i subdivide again then the program goes nutbatshit , anyway heres the screenshot with the memory used : i dont get it :( i will reinstall mud to see if it fixes anything....