Also if it can save out images as slow as it wants there wouldn't be studdering (or as taxing on the hardware, it would just take some time for each frame to save out before moving onto the next one). As if it were taking time for each frame to save out and THEN move onto the next frame instead of trying to do them all at…
Hi all, Trying out Marmoset for the first time and running the 30day trial of 106. I knocked up a very quick rock in zbrush as a test piece to bake and got my maps from xNormal. Using the xNormal 3d viewer everything is fine, however in marmoset I was getting seams so I figured flipped channel or something was to blame. No…
i have some few issues here, 1) in the first image, the hair transparency map is working with alpha to coverage turned on. however, i'm getting a halo around it where an outline shows through and is clearer seen when the transparent smaller planes are on top of the main hair surface. Just to prove it is not a problem with…
I have a intel core 2 Duo processor P7450 (2.13 GHz, 1066 MHz FSB), 4 Gb memory, 500 Gb HDD, Nvidia Geforce GT240M. Maybe the problem is that the maps are too big and slow down and bug the render? The maps are 4k each exeptfor the alabard texture, normal and glow(the spec/gloss map of the alabard if 2k doesn't work right)…
Everything was going great until Marmoset 1.10 tore my rig and animation to pieces. I spent 2 days following this tutorial to rig my creature in Maya http://www.digitaltutors.com/tutorial/1371-Rigging-Quadrupeds-in-Maya He uses some kind of "flexi" rig system that relies on nurbs deformation and even a bit of n-hair I…