Hi SreckoM
I tried cleaning up the normals as you suggested, but I'm still getting issues on the rear, as per the last image I sent
Apologies for sending such a high noise value - I've been altering things, then chucking the noise right up to see the changes. Also, I have been importing and removing geo within the file and haven't kept the scaling the same throughout, so some noise values weren't high enough for larger objects
What shader were you using for your last image?
Solidworks to Houdini - Converting Geometry etc.
32838 29 4- stu_dini
- Member
- 9 posts
- Joined: June 2014
- Offline
- SreckoM
- Member
- 379 posts
- Joined: Dec. 2006
- Offline
I was using metal_Anthracite, did some changes on it though. Also note that I used Envlight with HDR and deleted other lights in scene and used PBR as render engine.
Most important thing is to cusp normals with Vertex sop and it should work.
You do not even need to clean normals before that I think.
But as I said geo is really messy and I would not be surprised if there are some artifacts after that too. I did renders from few angles and it looks good.
Most important thing is to cusp normals with Vertex sop and it should work.
You do not even need to clean normals before that I think.
But as I said geo is really messy and I would not be surprised if there are some artifacts after that too. I did renders from few angles and it looks good.
- stu_dini
- Member
- 9 posts
- Joined: June 2014
- Offline
Hi guys,
Just thought I'd post an update.
Not much has changed tbh… for me, the best workflow has been via MOI then creating custom VOPS shaders. Out of the box shaders do something funky with the normals (seems to be the normals anyway)
But anyhow, I have the iron in Houdini looking good enough. The shaders aren't showing the tessellation now. The are some objects not quite smooth enough, but that would be a simple case of re-exporting on a case by case basis at a slightly higher res.
Would obviously be better if Houdini supported this kind of work a bit more, hopefully in the future…
I'll keep updating here as and when I find stuff. Many thanks for your helps so far!
Stu
Just thought I'd post an update.
Not much has changed tbh… for me, the best workflow has been via MOI then creating custom VOPS shaders. Out of the box shaders do something funky with the normals (seems to be the normals anyway)
But anyhow, I have the iron in Houdini looking good enough. The shaders aren't showing the tessellation now. The are some objects not quite smooth enough, but that would be a simple case of re-exporting on a case by case basis at a slightly higher res.
Would obviously be better if Houdini supported this kind of work a bit more, hopefully in the future…
I'll keep updating here as and when I find stuff. Many thanks for your helps so far!
Stu
- Horseguy44
- Member
- 6 posts
- Joined: June 2014
- Offline
Looks great Stu but I have to ask, considering pretty renders can be done with other less powerful/less difficult packages, why Houdini? Are there plans to take this iron or other products and animate? Add steam/smoke etc?
This does give me great hopes that my own ambitions for Houdini, as a product design tool (this is a hint to the developers…new/existing market waiting to be accommodated…) will work out!
Thanks for the update.
-GW
This does give me great hopes that my own ambitions for Houdini, as a product design tool (this is a hint to the developers…new/existing market waiting to be accommodated…) will work out!
Thanks for the update.
-GW
- stu_dini
- Member
- 9 posts
- Joined: June 2014
- Offline
- Gyroscope
- Member
- 75 posts
- Joined: Feb. 2011
- Offline
Sorry, late update from me. While it doesn't appear to be a bug, more a workflow issue, I found one solution and SESI offered another.
I found, the overlapping UVs to be an issue, which once sorted out it was good enough to go.
SESI's suggestion was computing normals and adding a Divide SOP using the Bricker Polygons toggle checked. My specific case called for a 0.2 size.
I found, the overlapping UVs to be an issue, which once sorted out it was good enough to go.
SESI's suggestion was computing normals and adding a Divide SOP using the Bricker Polygons toggle checked. My specific case called for a 0.2 size.
- stu_dini
- Member
- 9 posts
- Joined: June 2014
- Offline
- Anonymous
- Member
- 678 posts
- Joined: July 2005
- Offline
Hi to all,
I run into the same problem. Getting STEP-files from my customers, converting it with Polytrans to FBX and importing these files into Houdini 13.
I've tried anything I've read but nothing works for me. Any ideas? I have to deliver final picts monday - uff. I have a texture for the bump map but without any UVs that fits to my model there is no chance. All normals are OK!
Thanks for help
Detlef
I run into the same problem. Getting STEP-files from my customers, converting it with Polytrans to FBX and importing these files into Houdini 13.
I've tried anything I've read but nothing works for me. Any ideas? I have to deliver final picts monday - uff. I have a texture for the bump map but without any UVs that fits to my model there is no chance. All normals are OK!
Thanks for help
Detlef
- jimc
- Member
- 295 posts
- Joined: Oct. 2008
- Offline
- imensah
- Member
- 35 posts
- Joined:
- Offline
T splines would have been a good solution to solve the geometry conversion but autodesk snagged the patents pretty quick http://www.tsplines.com/ [tsplines.com]
-
- Quick Links