Sadly your portfolio doesn't contain any solid piece for the moment. I scrolled down and in 2 sec I left. It's sad but true at the same time. You sould start new project and put more effort into it to impress.
50% sale this weekend!! Buy a rifle before Xmas and you get the new Communist invasion repelling package! Also we have the new Zombie apocalypse combo for children*! *contains small parts, not suitable under the age of 5!.
HighPoly is on the 1st image i posted about this container. Although it isn't super high poly keeping things basic for now, working up.... still used it to project normal maps onto low poly version via XNormal.
Yeah, I'd really like to be able to do high poly renders in 3-5 seconds, this looks interesting too, http://studiouani.com/ure/home.htm (heads up, might contain malware, I'd like someone to scan it and check)
I really like this! Only thing I notice is that a few areas could probably be mirrored to make the map more efficient. The contains lead bit if nothing else. Its a really small point though, so excellent job.
Hey Polycount, I have a strange request. I am modeling an AR-15 for my portfolio, and I need screen caps of people saying how terrible my portfolio is and how it does not contain any guns. Can you people oblige, or is that too weird? Thanks in advance.
If the normals are getting smoothed when loading in Toolbag, that means the .FBX file doesn't contain normal data. So you'll need to check your export settings to make sure the custom normals are saved. From Andrew's screenshot about, I would try the Split per-vertex Normals option
OK, it seems like Substance Designer is smart enough to auto replace any file path matching existing Alias. So while the SD properties panel show the full file path, the .sbs file will contain the alias in path, thus allowing other machines to setup their custom library location...
And here's the unwrap as it stands, the remaining space on the UV grid is reserved for the eyes and hair/leaf planes. I've tried to contain any distortion to the back (she'd mainly be seen front-on) and the chest will be covered in leaves like the concept so I'm not too worried about that. Any comments at all would be…
And that error shows the insetchamferstacksimple.ms file? The MAXScript-only file is self-contained and doesn't use mcg. Are you using the MAXScript-only version? The MCG one breaks the borders and then uses fixed-value weld which may not work with some unit setups in which case chamfer won't do anything.