Netvudu Posted November 23, 2012 Share Posted November 23, 2012 Just so that you know it, you are my new heroes guys....(specially if you make it work properly ) Quote Link to comment Share on other sites More sharing options...
zarti Posted November 23, 2012 Share Posted November 23, 2012 hey rom , this seems an awesome start ! sincerely .. thanks . since AD products do not oscillate on the same frequency as my brain and logic does , i really hope to see this idea take a solid form . so thanks in advance to anyone involved even in trying for it .. =) { yep , seems a bit 'strange' to see LW's layout of parameters inside Houdini , but as i said ; this might be a good candidate / reference for 'the_ubershader_material' ( i think ) Houdini needs } -- on Houdini 11.0.658 and 12.1.33 it does not working.on call asset and on load geometry gives a mistakes : )) hi skazkaPiter , accidentally im trying lwo.otl in the same H12.1.33 ( WIN_7x64 ) and im having no problems . .cheers Quote Link to comment Share on other sites More sharing options...
rom Posted November 27, 2012 Author Share Posted November 27, 2012 (edited) Here is a more stable version Turns out it was failing mostly due to vmap names not being compatible with houdini's attribute names currently the node parms for surface layers are only set up for the color channel, so it will also throw exceptions when trying to set layers in other channels. Although it should be able to load large files, it is not currently optimized for them. The initial intention for this was not to just load old lwo files, It was more to use Lightwave Modeler to quickly create elements that could then be subjected to houdini's procedural treatment, providing the best of both paradigms. For now it is probably also wise to 'cache' as a native houdini .bgeo as the lwo is not reloading, when the scene reloads. Lwo.otl Edited November 27, 2012 by rom 1 Quote Link to comment Share on other sites More sharing options...
dulo Posted November 27, 2012 Share Posted November 27, 2012 Thanks a lot for sharing !! I have written quite a lot of python houdini<->lightwave tools in the last 3 years so maybe I can help you too !! I am trying to move our heavily lightwave based studio more in the direction of houdini for ages .. maybe I can give it a try again :-) Quote Link to comment Share on other sites More sharing options...
SaleVonGeist Posted January 30, 2014 Share Posted January 30, 2014 Hi all, Just a quick question, has anyone had any luck running this lovely tool in latest H13 builds? I attached screen grab of error it displays. Any info would be great, thanks in advance! Cheers, Sasa Quote Link to comment Share on other sites More sharing options...
dulo Posted January 31, 2014 Share Posted January 31, 2014 Just install dateutil in your python shell then it should work. Quote Link to comment Share on other sites More sharing options...
SaleVonGeist Posted January 31, 2014 Share Posted January 31, 2014 Thanks for quick reply Martin, much appreciated! Any pointers on how to do that (just a simple user here), so I don't mess something up? If it's of any help I'm on windows 7 64bit...thanks in advance. Quote Link to comment Share on other sites More sharing options...
dulo Posted January 31, 2014 Share Posted January 31, 2014 well you would need a package manager like pip or the simples way is to install the free version of pycharm ( python ide ) point it to the python interpreter of houdini and use its packet manager frontend to install dateutil or any package you like. Quote Link to comment Share on other sites More sharing options...
dulo Posted January 31, 2014 Share Posted January 31, 2014 I attached a screenshot with 5 simple steps to install packages with pycharm .. I hope that helps and by the way, pycharm is THE BEST python ide for windows and linux .. Quote Link to comment Share on other sites More sharing options...
SaleVonGeist Posted January 31, 2014 Share Posted January 31, 2014 Great info, thanks for the time and explanation Martin! Cheers, Sasa Quote Link to comment Share on other sites More sharing options...
eetu Posted March 26, 2014 Share Posted March 26, 2014 Thanks, one picture was worth a thousand words I'm not that knowledgeable about Python package management, would it be possible to install the dateutil package so that one would not need to reinstall it every time a new Houdini build is installed? (windows) Quote Link to comment Share on other sites More sharing options...
Netvudu Posted March 26, 2014 Share Posted March 26, 2014 (edited) Could anybody confirm if this tool is working properly and to what extent before I go through the process of trying to install it? Edited March 26, 2014 by Netvudu Quote Link to comment Share on other sites More sharing options...
eetu Posted March 27, 2014 Share Posted March 27, 2014 I quickly tried it in H13 yesterday.It does indeed work, although it did error out on some lwo files. I need to do some more testing to figure out what it is it doesn't like. It is a bit slow with the default settings, but toggling off the debug stuff makes it a lot faster. ( I changed all those defaults to "off", as well as the debug file path ) Quote Link to comment Share on other sites More sharing options...
rom Posted April 28, 2014 Author Share Posted April 28, 2014 I haven't touched this for some time. I know that it got slower and more buggy on adding some of more advanced surface reading capabilities. If you have the debug switched on, it should produce a log of the results. If you guys could, on files that the node fails, upload the log and and the lwo file, I can have a look at is wrong. 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.