I hadn't thought of its exact function. I decided it will be a gas mask with a power source in the back. Thanks for the comment keeping functionality in mind will help me define it from here. I will post an update over the weekend!
It's not worth it even with all those fine functionalities, it's so damn slow you're better off using the functions already available in photoshop even if they're not as ergonomic. Oh and I've yet to see that speed increase in 2.0 (IT's A TRAP §)
returned it yesterday, btw you can disable touch functions, so I assume you can use the pen only if you wanted(I had the bamboo touch, no pen functions). and yes, terrible in dawn of war :)
it would be easy to script, if autodesk hadnt forgotten to publish the "get suboject selections" functions to maxscript. Via c++ you can access which vertices are selected, but in maxscript they forgot... one could publish that function with a plugin so.
Thanks guys, more specifically I miss the align uv functions, where you take a row of vertices and align it u or v perfectly straight. J.Haywood's seems to have that functionality, I'll try it out, thanks Kary :)
You could try the Henyey Greenstein phase function with low aniso value. It isn't exposed to the function library so search for it in the engine content. You would still need a thickness map though, I think you can't do anything decent without it.
I don't know of any consistent behavior on the CC 2015 front. Some computers in my office have no issue with it, some do. CS6 is the only thing that functions consistently across the machines. It's worth taking a shot, at the least. Rest assured that 2.0 functions flawlessly. :)
They've been slowly adding back in the functionality of the old caddy system to the new ones. I think they fixed the zero'ing out in 2011, the enter key and tabbing in 2012. Slowly but surely all of the functionality is coming back... its sad that it wasn't all there on day one.
look on here for the split function https://docs.python.org/2/library/string.html#string-functions string concatenation is done with + so once you've split it at whatever separator you decide to use you can simply do this... newstring = splitString[0] + random + splitString[1]
Thought I'd try my hand at the expired polycount challenge. Been working on the base. Straying from the concept quite a bit, but I'm trying to figure out how to make all the joints and stuff functional. Crits in terms of form/functionality/sizing or anything really is greatly appreciated. c^: