Jump to content


  • Content count

  • Donations

    0.00 CAD 
  • Joined

  • Last visited

  • Days Won


kiryha last won the day on July 20

kiryha had the most liked content!

Community Reputation

54 Excellent

1 Follower

About kiryha

  • Rank
  • Birthday 05/06/1977

Contact Methods

  • Website URL

Personal Information

  • Name
    Kiryha Krysko
  • Location
  • Interests
    Houdini, Photography, Cookery

Recent Profile Visitors

2,162 profile views
  1. From Command Line Tools running exe file is working!
  2. In the command line (C:\Windows\System32\cmd.exe) started from the folder with geoisosurface.C (E:\PROJECTS\HDK\samples\geoisosurface): hcustom -s geoisosurface.C I have a Visual Studio 2017 installed and MSVCDir environment variable set to C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023
  3. Thanks, Alex! I have a Houdini bin in the PATH Windows environment variable. Also, I tried to run set PATH="C:\Program Files\Side Effects Software\Houdini 18.0.460\bin;%PATH%" before executing geoisosurface.exe, but it did not help as well. Ok, not a big deal since the executable is working from the Houdini bin.
  4. Hello, devs, I have compiled geoisosurface.C but running geoisosurface.exe raise an error: Entry Point Not Found. The procedure entry point gzdirect could not be located in the dynamic link library C:\Program Files\Side Effects Software\Houdini 18.0.460\bin\libxml2.dll If I place geoisosurface.exe into the Houdini bin folder it is working and produce me sphere.bgeo. If I copy libxml2.dll to the folder with exe file the error is: The procedure entry point gzdirect could not be located in the dynamic link library D:/path_to_geoisosurface/libxml2.dll I am pretty sure that exe file should work outside Houdini bin dir, but have no idea how to fix this. Alex @Stalkerx777, anything comes into mind?
  5. Pragmatic VEX: Volume 1 [4K] [H18]

    Hello Yunus, this course looks outstanding, thanks for sharing! How did you combine the Scene View with Network View (when you manage the creation of nodes on top of the camera view)?
  6. Add tools to shelf from external file

    Probably you will need to run Houdini via Python wrapper, where you can set up necessary environment variables, the path to shelf etc.
  7. VEX for artists

    I have a Houdini GitHub repo where (in addition to the code section, which is the Houdini pipeline for my personal projects) I store all my R&D notes related to the pipeline developing and programming organized as one wiki. The valuable part of this wiki is VEX for Artists tutorial, where I record everything I was able to understand about VEX in form of tutorials, so it might be useful not only for me but for anybody else, who is going the same route of learning programming from scratch. It was built by a guy with an artistic background and no technical education and skills, so it might be suitable for the same type of peoples. Easy and clean, a lot of simplification, a lot of explanation of basics. This VEX tutorial was just updated with a new section: Solving problems with VEX. Here, using the basic blocks studied earlier we will create something meaningful for the production. The first example we look into is the creation of a hanging wire between 2 points. For those who tried or even afraid to begin to learn VEX but fail and stop because it was too hard. Enjoy!
  8. simple vex function

  9. Shared drive in the cloud

    Hello, magicians, I am looking for online storage to share the Houdini pipeline (Python2.7, PySide2, sqlite3) and projects between remote artists. In the ideal case, anybody with login/password provided should be able to connect this storage as a network drive, launch Python scripts, access all files and folders. My OS is Windows but it would be nice if it will work under Linux and Mac as well.
  10. Ah, got it. Interesting question, usually it works the opposite way: you define your global variables via environment variables.
  11. What do you mean by "global variables"?
  12. Run Python script after Houdini starts

    subprocess.Popen([HOUDINI, ['C:/temp/script.py'], 'argument_one']) That gives me what I need. The only thing I don't know how to run a function from script.py after import...
  13. I am launching Houdini with subprocess: HOUDINI = 'C:/Houdini 18.0.287/bin/houdinifx.exe' subprocess.Popen(HOUDINI) How can I import a Python and run a necessary function after Houdini is launched (import open_asset; open_asset.open())? In Maya I can send MEL command to be executed after Maya starts (and import script with this command): subprocess.Popen('C:/Maya 2019/bin/maya.exe', '-command', "python('execfile(\"path_to_the_script\"')") How can I do something like this in Houdini? The 123.py is not a solution, because I don`t need to run a script each time, only in certain cases, and the scripts are different each time. I need this to open an asset file from Shotgun, for example.
  14. By the "fields" I meant the half-frame for TV broadcasting. I recall I struggle to get fields out of Maya render when I was working on TV in the past millennium. I did not know they are still alive.
  15. Looks nice! I see the fields... did not expect anybody uses fields these days