problem artifacts

Newtek Lightwave 3D (exporter developed by holocube, Integrated Plugin developed by juanjgon)

Moderator: juanjgon

Post Reply
gigi
Licensed Customer
Posts: 40
Joined: Thu Mar 07, 2013 11:11 am

Hello, does anyone know tell me what is the problem? geometry looks clean.
Attachments
LW.jpg
Pc laptop | Corei7 at 2.8GHz | 16GB | GeForce GTX 980M 8 GB | 240 GB SSD | 500 GB 7200 Rpm| Windows 8.1 pro 64 |
User avatar
juanjgon
Octane Plugin Developer
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

Weird issue. Have you tried to tweet the ray epsilon parameter in the kernel node? Perhaps it is a scale problem.

-Juanjo
gigi
Licensed Customer
Posts: 40
Joined: Thu Mar 07, 2013 11:11 am

hau reason, is a problem of scale. The model has been scaled because the original is too big for my scene! how can I fix it? It 'a problem of model?
Pc laptop | Corei7 at 2.8GHz | 16GB | GeForce GTX 980M 8 GB | 240 GB SSD | 500 GB 7200 Rpm| Windows 8.1 pro 64 |
User avatar
juanjgon
Octane Plugin Developer
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

Can't the ray epsilon parameter in the kernel node fix the problem? ... try to render the image with 0.001 or 0.01 as ray epsilon, to see what happens.

-Juanjo
gigi
Licensed Customer
Posts: 40
Joined: Thu Mar 07, 2013 11:11 am

I do not think, as you can see in the modeler, the vessel is 8.6 meters high. while in the layout it is scaled in order to have a correct size.
Attachments
2.jpg
1.jpg
Pc laptop | Corei7 at 2.8GHz | 16GB | GeForce GTX 980M 8 GB | 240 GB SSD | 500 GB 7200 Rpm| Windows 8.1 pro 64 |
User avatar
juanjgon
Octane Plugin Developer
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

Weird, the object scale should not be a problem. Can you please try with a ray epsilon of 0.000001 (you are going to see 0.0, but it works).

Anyway, if you want to send me the scene I could test it here: [email protected]

-Juanjo
gigi
Licensed Customer
Posts: 40
Joined: Thu Mar 07, 2013 11:11 am

the problem still exists. I send you the scene. thanks for your time.
Pc laptop | Corei7 at 2.8GHz | 16GB | GeForce GTX 980M 8 GB | 240 GB SSD | 500 GB 7200 Rpm| Windows 8.1 pro 64 |
User avatar
juanjgon
Octane Plugin Developer
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

The problem in this scene is that the objects have a vertex normal map that is broken, perhaps because you have modified the geometry in the modeler (rotation operations and so on). If you disable the vertex normal maps in the materials and adjust the smoothing angle, all should work fine.

Remember to reload the scene in the IPR after change this parameters to see the changes.

-Juanjo
Attachments
image000693.jpg
gigi
Licensed Customer
Posts: 40
Joined: Thu Mar 07, 2013 11:11 am

Thanks again Juanjo!!!!
Pc laptop | Corei7 at 2.8GHz | 16GB | GeForce GTX 980M 8 GB | 240 GB SSD | 500 GB 7200 Rpm| Windows 8.1 pro 64 |
User avatar
LightwaveGuru
Licensed Customer
Posts: 487
Joined: Wed Jun 25, 2014 9:34 am
Location: Germany
Contact:

juanjgon wrote:The problem in this scene is that the objects have a vertex normal map that is broken, perhaps because you have modified the geometry in the modeler (rotation operations and so on). If you disable the vertex normal maps in the materials and adjust the smoothing angle, all should work fine.

Remember to reload the scene in the IPR after change this parameters to see the changes.

-Juanjo
hi :)

everytime if you see artefacts like that is the reason that the new octane/lw users drop the normal map in the classic surface editor or use a wrong normal map in the node editor...put this tipp in the manual if you want...its better (as you must have a look in every scene if a new user do that) ....than you can say...RTFM :)

snip lwguru
http://www.neotek.laboratories.de or http://www.youtube.com/c/Lightwaveguru or http://www.facebook.com/safarifx 4x Titan X 12 GB watercooled / 6x 2080 ti air cooled / 2x 980 ti watercooled
Post Reply

Return to “Lightwave 3D”