Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

Sculpty Seems

Ryoku Itoku
Registered User
Join date: 19 Jan 2006
Posts: 59
07-10-2007 17:38
well I'm a maya user and I've got the exporter and everything works fine on that end, nothing has changed in both my modeling practices and how i've exported my Sculpt maps however

an update or two ago I tried uploading some sculpt maps and I noticed that there was a huge seem in my models. I uploaded one and the seem actualy escilated into a fullblown WT*.

along where the seem was in the preview is now a row of pinched verticies. a temp fix for this was to turn the sculpt prim type to a torus though the pinching didnt go away but on the object in question it wasnt entierly a big deal though anything i make now has a big seem in it and I cant figure out how to get rid of it!

http://andrew.armyofnone-online.com/problem.jpg
Thili Playfair
Registered User
Join date: 18 Aug 2004
Posts: 2,417
07-11-2007 02:55
Found a workaround on this -.- but i havnt touched it for awhile so i forgot what it was ~.~ bleh, i had the same seam issue the pic shows, tried flipping the texture 90 degree's might been how i fixed it.

To be honest im not to impressed with sculpts yet, nice to make small objects, useless for big (10x10x10 is to small for them) , rather they work on the bugs then having new stuff, to much got showed into debug and hidden away instead of having it as option , bloom/reflective shineyness are some.
Ryoku Itoku
Registered User
Join date: 19 Jan 2006
Posts: 59
07-11-2007 15:54
unfortunetly no ammount of flipping will fix this. i tried flipping not only the UVs but the texture in photoshop for about an hour. I previewed in sculpty paint and in preview and still cant figure out whats going on.

the really funny part is I've also tested this on sculpt maps which previously worked (and currently ARE working, uploaded and look fine) but in preview i have a nasty seem which wont go away.

this affects my ability to upload stuff. I'm considering posting it on jira as a blocking bug because this ruins the feature.