animknight Posted June 21, 2013 Share Posted June 21, 2013 Hey Guys I have a locked Digital asset which has a shader(digital asset) inside as an editable node. I deleted some parameters in the shader and updated it. But When I open my locked digital asset which has this shader and make some changes to this asset and save operator type and match current definition. It throws this error Problems while synchronizing child node skipping unrecognized parameter "useBlah" This is the parameter which I deleted in the shader. I'm not sure what's causing this? What am I doing wrong ? Any help much appreciated. Cheers -J Quote Link to comment Share on other sites More sharing options...
edward Posted June 22, 2013 Share Posted June 22, 2013 Try just resaving your locked HDA node (unlock first). The warning should go away. Quote Link to comment Share on other sites More sharing options...
animknight Posted June 24, 2013 Author Share Posted June 24, 2013 (edited) Thanks Edward. But I don't understand why it happens ? Does the digital asset stores even the parametric information of other digital assets which are present inside even though they are not embedded in this otl ? Does it happen if we use versioning for digital assets ? It happens only if I match current definition on the top level asset ? It's really annoying if I have nested digital assets using this shader. I have to open and save all the nested assets which uses this shader to lock the top level asset. Is there a better way to handle this ? Cheers -J Edited June 24, 2013 by jagadeesh Quote Link to comment Share on other sites More sharing options...
animknight Posted June 25, 2013 Author Share Posted June 25, 2013 Any thoughts ? Quote Link to comment Share on other sites More sharing options...
edward Posted June 26, 2013 Share Posted June 26, 2013 So did it fix it? When you have anything that uses a particular node (HDA or otherwise), the parameter value used for that node is stored. So when you delete the parameter on it, anything that used it will suddenly find that missing parameter and so it triggers a warning that information was lost. If you do *not* want this to happen, then you shouldn't remove the parameter, but just hide and stop using it. PS. I check forums very infrequently these days. Quote Link to comment Share on other sites More sharing options...
animknight Posted June 27, 2013 Author Share Posted June 27, 2013 I gotcha. Yes it did fix. I have to unlock the asset and save it and lock it back. But if this shader is being used in a number of assets, then I have to do this for all the assets. Is there by any other means I can ignore this warning ? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.