H12.5 and customized Surface model
3239 3 2- jimc
- Member
- 295 posts
- Joined: 10月 2008
- Offline
I just installed 12.5.316.22, and opened a hip file previously edited with 12.1.X. I have a material that I customized, a Mantra Surface Material, but it renders plain white and the material node has the red lines on the icon indicating an error. If I go into the network I see the error is on the surfaceModel node, and there are 6-7 nodes inside that that are flagged in error too. Looking at these nodes I can tell that some of them seem to have incorrect output types, and they were not the ones that I customized. Any idea what happened? Is there some way to fix it, or will I need to rebuild the shader from scratch?
- jimc
- Member
- 295 posts
- Joined: 10月 2008
- Offline
- RudiNieuwenhuis
- Member
- 193 posts
- Joined: 4月 2009
- Offline
Well, if you didn't change anything in the surfaceModel itself it's easy to just make it match the current definition. (right click)
I think you could even make a python script for this that does this for all the materials in your shop, something like:
myNode = hou.node('/shop')
for i in myNode.children():
print i
i('surfaceModel').matchCurrentDefinition()
But this generates errors because i'm sure i'm not referencing the surfaceModel correctly.
I could use some help on this.
I think you could even make a python script for this that does this for all the materials in your shop, something like:
myNode = hou.node('/shop')
for i in myNode.children():
print i
i('surfaceModel').matchCurrentDefinition()
But this generates errors because i'm sure i'm not referencing the surfaceModel correctly.
I could use some help on this.
- moondeer
- Member
- 14 posts
- Joined: 9月 2011
- Offline
my shaders also broke.
in my case, for surfaceModel, refr_enable and refr_model
error: “input data type does not match”
also, i am not offered the choice to update or match current def.
that is a contextually added bit, and it looks like this node doesn't apply.
so,
my peers they just do not bother to open a scene created in older hou.versions. they always use the matching application version.
i dropped a new surfaceModel and moved connections over to the new guy.
this broke the opengl bits.
i suspect i must now update the parameter interface to accomodate the new surfacemodel.
ugh. lol.
:shock:
in my case, for surfaceModel, refr_enable and refr_model
error: “input data type does not match”
also, i am not offered the choice to update or match current def.
that is a contextually added bit, and it looks like this node doesn't apply.
so,
my peers they just do not bother to open a scene created in older hou.versions. they always use the matching application version.
i dropped a new surfaceModel and moved connections over to the new guy.
this broke the opengl bits.
i suspect i must now update the parameter interface to accomodate the new surfacemodel.
ugh. lol.
:shock:
-
- Quick Links