Jump to content

Etherloth

Members
  • Content count

    22
  • Joined

  • Last visited

Everything posted by Etherloth

  1. Hi all! First post, sorry is not to contribute much but to ask for help, hopefully someone else with the same problem can read about this and find the solution here. I have a problem loading geometry in Houdini 16 running on W7x64, no matter what kind of file the behavior is always the same, to hang for a few seconds, then display the Cooking message for a (longer than it feels right) moment and then returning an error in the node. The dreaded message in the ! Error field of the node is: Unable to read file "C:/Users/userName/Documents/fileName.obj". This happens either via FILE > IMPORT > GEOMETRY and also popping the TAB menu, typing GEOMETRY and creating a new node, double clicking on it and trying to browse to the file via the floating file chooser input. I have already tried with many different files and file types, creating a simple cube OBJ and trying to import it, to make sure the file name does not have any spaces or numbers, I have even dropped the file in the $HOME folder (/Documents in my case) to ensure was not a path issue. I also have tried to check my houdini.env file to see if something weird was overwriting the program defaults (all is commented out, no actual environment variables there), even to add a PATH | path-to-the-houdini-bin-folder; to the system variables to no avail. The default.bgeo that Houdini uses as placeholder is loading without any issue, so not sure if this involve a path problem, my guess is more a geometry interpreter related issue of sorts. Additionally, Houdini gets all weird after the geometry is unsuccessfully loaded with constant freezes and even if I can get to select the node and eliminate it, the behavior of pressing space/alt to cam-navigate the 3D viewport results in a constant spinning around (!?). I have added an image displaying the error if its of any help, would be great to know how to get a workaround to this issue if someone can give a hand, thanks in advance! Eth.
  2. I noticed that some kind of files were actually importing/exporting properly and after checking on my Comodo Firewall program I got to realize that the ones that didn't had their respective executables blocked access to local host... not sure why Comodo did this, perhaps every time I tried to export/import there was a dialog popping in the background (as is usual in Comodo, it asks EVERYTIME a program wants to do anything meaningful in your system) and unlike in the normal cases when Comodo query has visual priority over the program that attempts to do something, with Houdini looks like these popups are left in the background, at least in my machine, therefore by default all these converters got blocked. TLDR: Make sure your file converters have clear access to your localhost. Now all OBJ and other formats are read/wrote perfectly. Thanks all the thread contributors for the help on this matter, hope this can help others in similar situation.
  3. polybevel bug?

    How to reproduce? On creating some random geo with the curve tool, selecting all points and applying it a polybevel I cannot reproduce the problem:
  4. Hi all I have a question about exporting geometry using .fbx - Basically I want to export certain model that has been created in Houdini and render it in Keyshot, while in Houdini the model looks smoothed as shown in the pic attached sc_from_houdini.png but when i import it in Keyshot it comes totally black opaque and unable to receive new materials. I can overcome this situation by entering dummy (zero) changes to the geometry in Keyshot, which renders it able to receive materials and be rendered properly. Now, the problem I find is that once this first issue is fixed, the result of the render is showing the raw polygons and not a smooth surface as it appeared in the Houdini renders, as we can see on sc_from_keyshot.png attached. Anyone have idea what this happens? Perhaps I am missing some step before exporting the geometry, or exporting it wrongly? Sorry is not the same exact camera, but is the exact same geometry, I also attach here the houdini .fbx exported file ) Thanks in advance ) s.fbx
  5. Touche my friend. Not only adding normals solves the problem with the black, non-material-assigning geometry, but also fixes the "pixelated" look of the geometry indeed what Keyshot looks like was doing is tracing vertex from point to point somehow, attached newly render example below. Thanks a lot @Atom !!
  6. Thanks @marty for all the answers and help ) Nope, MASTER is simply what I am using which AFAIL should be 100% fine, thanks for your answers as well @Atom - Still wondering what was that PATH related line in .env that you mentioned a few times, I have nothing about PATH in there and perhaps is worth a shot )
  7. Mh, but the existing PATH in Houdini already has a part that says: C:/PROGRA~1/SIDEEF~1/HOUDIN~1.20/bin Which is a clipped version of: C:\Program Files\Side Effects Software\Houdini 16.0.504.20\bin Shouldn't this be enough to point the program towards the correct stuff? Or does it have to have it twice no matter what like in an array? I tried to delete PATH totally from windows environment variables and tried again (unsuccessfully) and Houdini was returning me a %PATH% in the end of the PATH content from the info within the application. For the record, I also tried to delete my preferences folder and put on the PATH environment variable value the following: C:/PROGRA~1/SIDEEF~1/HOUDIN~1.20/bin C:\Program Files\Side Effects Software\Houdini 16.0.504.20\bin; "C:\Program Files\Side Effects Software\Houdini 16.0.504.20\bin" "C:\Program Files\Side Effects Software\Houdini 16.0.504.20\bin;" "C:\Program Files\Side Effects Software\Houdini 16.0.504.20\bin;&" but does not work at all as well Running out of ideas here.
  8. The value of the PATH environment variable I have set up in windows is a copy/paste of what you have suggested before, so: "C:\Program Files\Side Effects Software\Houdini 16.0.504.20\bin;&" And if I enter echo %PATH% in cmd it returns now the proper value set on the variable, so the one quoted above ^ Inside Houdini, though, the PATH still shows as C:/PROGRA~1/SIDEEF~1/HOUDIN~1.20/python27;C:/PROGRA~1/SIDEEF~1/HOUDIN~1.20/bin;C:/PROGRA~1/SIDEEF~1/HOUDIN~1.20/toolkit/bin;"C:\Program Files\Side Effects Software\Houdini 16.0.504.20\bin;&" Mh, any idea of why would it be adding all that stuff before the actual PATH that we have set? :/
  9. One more note, before I think I copied wrong the PATH inside About Houdini cos it was clipped by the window, the actual whole thing is (after the change in the environment variable): C:/PROGRA~1/SIDEEF~1/HOUDIN~1.20/python27;C:/PROGRA~1/SIDEEF~1/HOUDIN~1.20/bin;C:/PROGRA~1/SIDEEF~1/HOUDIN~1.20/toolkit/bin;"C:\Program Files\Side Effects Software\Houdini 16.0.504.20\bin;&"
  10. Ok so, I have tried to put: "C:\Program Files\Side Effects Software\Houdini 16.0.504.20\bin;&" in the PATH variable, but did not solve the issue (even restarted the computer just in case). If I enter in cmd echo PATH it returns PATH if I enter echo $PATH returns $PATH What should actually return the echo?
  11. In the About Houdini section, my PATH is set to: PATH C:/PROGRA~1/SIDEEF~1/HOUDIN~1.20/python27;C:/PROGRA~1/SIDEEF~1/HOUDIN~1.
  12. I did read about this on other forums and already have set my PATH in environment variable to point the /bin folder on Houdini, this is the PATH value on env. vars: C:\Program Files\Side Effects Software\Houdini 16.0.504.20\bin; Not entirely sure if there is anything I miss there, tried both with and without semicolon at the end and nothing... hence me asking @Atom about it. If i enter an echo PATH in cmd it returns me simply: PATH
  13. Yes, for example if I open Houdini, create a box and export it to the desktop in .bgeo or .poly form it works flawlessly, same thing if i create a new scene, a brand new geo node, dive into it and bring back in the .bgeo or .poly box via the file node, it all works fine - If I try to save that same box as an .obj or .dxf though, it looks like the program process something for a few seconds, then the dialog box disappears as if the process has been completed, but does not generate the .obj or .dxf file at all.
  14. Yes I have tried to test gwavefront with indications from another post but when I tried to do a geometry conversion from command line it complains about the license :| By simply typing gwavefront in the cli indeed does return the proper help text.
  15. Hey, thanks for the answer I already tried that in the beginning, not just in C: but also in Desktop, $HOME (Documents) etc. I do not think is a pathing issue, but more that Houdini cannot find or is unable to start the process to work with the OBJs.
  16. @Atom so could you pls tell me what is the exact line to add PATH in the .env? Just concerned I could have entered some typo of sorts. Thanks.
  17. Thanks for the interest @Atom my houdini.env is basically empty, has the comments only: # # Houdini Environment Settings # # The contents of this file are read into the environment # at startup. They will override any existing entries in # the environment. # # The syntax is one entry per line as follows: # VAR = VALUE # # Values may be quoted # VAR = "VALUE" # # Values may be empty # VAR = # # Example: # # HOUDINI_NO_SPLASH = 1 So nothing there, can you please paste here the $PATH you had to add in order to make it work? Thanks in advance. Eth.
  18. Ok so after an extensive research I have not found the solution, is a pity because I think Houdini offered amazing features, is just perhaps that my hardware combination unluckily is not very friendly with it, thanks @stickman and @Atom for trying. Eth.
  19. Problem is with all files ) showing here the one I use as example. simplesquare.obj
  20. What I meant above is that obviously I do not give my OBJs a .obj0 extension name, they are completely normal OBJ files that open perfectly in any other 3D package, I also created a totally simple square in OBJ and tried to import it with the same results. There must be something else because upon importing any geometry Houdini starts responding REALLY laggy and glitchy, mostly non responding. The way it works is that actually the geometry TRIES to load for a while (few mins) letting Houdini unresponsive, then when it seems to "give up" just adds the zero at the end of the file extension. If I try to take out that zero manually from the extension and reload the geometry, it returns me the same error without the zero at the end of the extension as shown in the attached screenie. I have also noticed that if I try to export any geometry to an FBX file and load it in Keyshot it appears all black, not sure if related.
  21. Shameless bump to see if someone can shed some light on the topic
  22. Yes I found that actually weird, obviously the .obj files I try to import do not have that zero at the end.
×