Mon, Sep 9, 7:21 AM CDT

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Sep 09 6:38 am)



Subject: Probem with some shaders in poser5


compiler ( ) posted Sat, 04 September 2004 at 6:22 PM · edited Fri, 30 August 2024 at 7:06 AM

file_126885.jpg

I use Toon shaders a lot, and some meshes don't like them. To get a reasonably normal figure withPoser, I have to decrease the linewidth to 0, which spoils a good part of the interest in the toon node. Anyone has an idea of why it is doing this, and what can be done about it ? Thanks in advance for your suggestions.


xantor ( ) posted Sat, 04 September 2004 at 6:34 PM

It looks like the object polygons are having lines added to them, I don`t know how to fix it, but I am sure that there is a way. This happens with my free robot too :(


OddDitty ( ) posted Sat, 04 September 2004 at 7:23 PM

Looking at the toon shader I think I see why. I need to play with some things, but I should have a pretty decent chunk on this shader in about a week -- long time, I know, but I'm swamped. in part, though, look at material groupings...


xantor ( ) posted Sat, 04 September 2004 at 9:10 PM

I don`t think that the material groupings is the problem, it is a problem with the actual object file.


compiler ( ) posted Sun, 05 September 2004 at 4:10 AM

xantor, I'm a total sub zero for modeling. When you say "lines added to the obj",do you mean several lines joining the same vertices, or lines of text added in the obj file ? In the second event, a run through UVmapper would fix it, but I tried it and it did not work. Can you think of a way to correct this in a modeler ? OddDitty : thanks for looking into it. I don't mind the delay : I've been hitting my head on this problem for 2 months now...


xantor ( ) posted Sun, 05 September 2004 at 6:31 AM

it looks like the actual wireframe lines is what I meant. Someone had a solution for this a year or so ago but I can`t remember it. Welding the vertices might work.


compiler ( ) posted Sun, 05 September 2004 at 6:34 AM

i tried to use the "weld vertices" command in UV mapper Pro, and to import the obj with "weld vertices" option on, to no avail...


mateo_sancarlos ( ) posted Sun, 05 September 2004 at 8:24 PM

It would be easy enough to see if there are dozens of spurious groups or materials using the group editor, since the lines usually appear at group/material boundaries.


xantor ( ) posted Sun, 05 September 2004 at 8:38 PM

Can you do a close up picture of the wrong effect? Maybe just the head of the figure, because it looks to me like the mesh lines that are showing and a bigger picture would show one way or another what is wrong.


xantor ( ) posted Sun, 05 September 2004 at 9:13 PM

Could you try exporting the whole figure as an object and reimporting it and adding the toon shader? I tried it with my free robot and it is definitely the mesh lines that are showing, but when I exported it as a wavefront object and reimported it, the problem seemed to be fixed.


compiler ( ) posted Mon, 06 September 2004 at 5:30 AM

I'm at work, I'll post a close up later on. I have tried the import/export technique, with or without the "weld vertices" option, but it didn't work.


compiler ( ) posted Mon, 06 September 2004 at 2:38 PM · edited Mon, 06 September 2004 at 2:39 PM

file_126886.jpg

Now this is really getting weird ! From close-up, even with line width at 1, there is hardly a problem, only a few artefacts. If I take the camera back a little evrything gets screwed up (for all the material groups BTW)...

I'm totally clueless here. Any help will be much appreciated ! Edited : for all of the material groups BUT the chest...

Message edited on: 09/06/2004 14:39


xantor ( ) posted Mon, 06 September 2004 at 7:36 PM

When I exported the object and reimported it I had make polygon normals consistent checked, maybe that is what fixed the problem for me.


compiler ( ) posted Tue, 07 September 2004 at 2:53 PM

Nope, I just tried it and it made matters even worse...


compiler ( ) posted Tue, 07 September 2004 at 3:07 PM · edited Tue, 07 September 2004 at 3:11 PM

OK, finally found a solution.
Since it was obviously polygon based, I passed the obj through "Hi-res" a subdivision program available at DAZ, and it solved the problem.
The downside is that it brought the polycount from 8 000 polys to 30 000 polys... Edit : of course, any ideas based on cheap software to improve on this solution are more than welcome !

Message edited on: 09/07/2004 15:11


SenshiTaurus ( ) posted Tue, 07 September 2004 at 3:37 PM

I dunno why, but my toon shaders work fine...i'm sure compiler knows due to the test pictures showing all the anime lights in action with Cresent's toon shaders that i did...Well, i dunno why, but my low poly works just fine...


compiler ( ) posted Tue, 07 September 2004 at 4:16 PM

Crescent's shaders work because they have a lineWidth at 0. Now I'll see if increasing the LineWidth really is worth the pain. If not, I'll change this in my shaders. Thanks to all of you who have helped me figure this out.


SenshiTaurus ( ) posted Tue, 07 September 2004 at 4:17 PM

What's the diff of using the line width and what cresent did?


compiler ( ) posted Tue, 07 September 2004 at 4:52 PM

I tried both and it seems not to make a difference. As far as I can tell, the toon shader was meant to work on its own, the linewidth being useful in this case. For Crescent's shaders and others derived, the line is replaced by the edge_blend node, overriding the linewidth parameter. I'll replace my shaders in the freestuff.


xantor ( ) posted Wed, 08 September 2004 at 2:44 AM

By the way, this isn`t a poser 5 only problem. illustrator in 3dsmax and the lightwave built in cartoon shaders both have this effect happening with certain objects.


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.