lazza79 Posted March 10, 2017 Share Posted March 10, 2017 (edited) Hi Guys, I am getting an annoying warning on H16 if I have an "explodedview" node in my scene. Nothing strange or causing me problems but it's really annoying. May this be because I imported an OTL done with H15.5 that had an explodedview node inside? Can anybody help? Thank you, Cheers! Lazza79 Edited March 17, 2017 by lazza79 Quote Link to comment Share on other sites More sharing options...
LaidlawFX Posted March 13, 2017 Share Posted March 13, 2017 Yes, the 90% of time you see that dialog is because you switch versions of houdini and new or old parameters exist. Once you save it and keep on working in that version it will go away. Alternative the other 10% is when an hda is no longer linked to the scene file and it becomes embedded. 1 Quote Link to comment Share on other sites More sharing options...
lazza79 Posted March 14, 2017 Author Share Posted March 14, 2017 The strange thing is that if I open a new scene without using any HDA I still get that error. How can I "reset" this? Thank you very much for your help! Lazza79 Quote Link to comment Share on other sites More sharing options...
LaidlawFX Posted March 14, 2017 Share Posted March 14, 2017 That should not be possible, as the hda would have to load in order for it to do that type of check. Is that hda in another hda? or is it getting created in a preset workflow? Also this will keep happening if you switch back and forth between major versions with a scene file due to the fact that parameter only exist in one version. Quote Link to comment Share on other sites More sharing options...
lazza79 Posted March 14, 2017 Author Share Posted March 14, 2017 So you say that if I remove all my hda from Houdini, the error will likely go away? Sorry, I am still learning... Quote Link to comment Share on other sites More sharing options...
LaidlawFX Posted March 14, 2017 Share Posted March 14, 2017 If you want to do a test, you can bypass your $HOME\houdini15.5 by calling it $HOME\houdini15.5_BAK, to check where your $HOME is go to the textport pane and do echo $HOME. If you have set your $HOUDINI_PATH you can bypass that too. After relaunching houdini, if the issue goes away then it's something in your custom directories and other tool sets, and then you can slowly engage each directory to see what is wrong. I'm guessing the first one to test would be $HOME\houdini15.5\otls_BAK. If it is still calling that issues after you have bypassed those directories and when you open a new scene, then you should probably reinstall Houdini :/ Also get the latest production, or daily build of houdini as it may be related to that specific version. Quote Link to comment Share on other sites More sharing options...
lazza79 Posted March 14, 2017 Author Share Posted March 14, 2017 (edited) That's strange. I uninstalled H16, reinstalled and loaded the non-commercial version and I still have that problem. I moved all the folders inside $HOME (houdini 14-15-15.5-16) to a subfolder and I still have that. I just open an empty scene, put down a sphere (polygon mesh) scatter points, voronoi, exploded view. Save, open again, ERROR. This is sooo strange. EDIT: I just tried to install H16 on a different clean PC. The problem is 100% reproducible. I am now trying to install a daily build to see if the problem is there as well. Edited March 14, 2017 by lazza79 Quote Link to comment Share on other sites More sharing options...
LaidlawFX Posted March 14, 2017 Share Posted March 14, 2017 What build number of houdini 16 were you installing? The 16.#.### Also what OS? It's possible it is a bug. You can tell sesi about support (at) sidefx.com. Test it on a lter daily build to see if they fixed it yet though. Quote Link to comment Share on other sites More sharing options...
lazza79 Posted March 14, 2017 Author Share Posted March 14, 2017 I just submitted the bug to SideFX. Other friends saw this. Thank you very much for your help! 1 Quote Link to comment Share on other sites More sharing options...
lazza79 Posted March 17, 2017 Author Share Posted March 17, 2017 Bug was solved on daily 548: The Connectivity SOP now has a parameter to choose whether to create a local variable or not. Quote Link to comment Share on other sites More sharing options...
.jpg.018a3ccc7a43f4bbdbeb8201c39f4f99.thumb.jpg.aa578da6fe2b7f5c8b26d654da58dd3f.jpg)
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.