Search the Community
Showing results for tags 'Houdini13'.
Found 4 results
-
Hi, Anyone know what is happening to my Houdini? I just install the new 13 after I installed my new Window 7. It crashed often and it seems to not work properly. It happened even I install directly from SideFX.
-
Here is my final short film for Sheridan's 10 month Visual Effects course. Everything from pitch, storyboards, previsualization, shooting plates, editing and vfx is done entirely by myself. I had the support and feedback of a great group of teachers and classmates. Breakdown to come soon. All shots you see have VFX elements, how many can you spot? Programs Used: - Nuke 8.0v3 - Houdini 13 - Maya 2014 - PF Track - Mari 2.5v2 - Adobe Creative Suite Timeline Included: - September - October (Pitch) - October-November (storyboards) -November-December (previsualization) - January-February (production shoots for whole class) - February-March (editing) - March-June 20th (VFX) All visual elements were created entirely by myself Music: "Happy End" by Distemper **Feel Free to inquire regarding any questions or critiques as I am still fine tweaking some details over the next few weeks. ** https://vimeo.com/98883004
-
Hey guys, i didnt find anything in the forum so i'm gonna open up a new thread for future searchers on this topic (and not hijack my other thread about compilation issues....). Now that i managed to build my plugins, i would like to establish a convenient plugin testing workflow. What i would do in Maya is, after the build i would run a python script to: 1. Load empty scene 2. Unload the plugin and release the handle 3. Copy and overwrite the .dll (.mll) 4. Reload the plugin 5. Reraise test scene setup I can't seem to find a way to unload the plugin in Houdini (or load it in the interface). Is there a way to set it up like this, or do i need to restart Houdini every time ? PS: Is there a list somewhere that explains all the abbreviations like GU, OP etc. ? When i accidentaly read that GU means Geometry Utility, lightbulbs went on, and the HDK naming scheme immediately became a lot less obscure.... -
Hello everybody, i am currently in the process of trying to generate a Visual Studio project that successfully builds Houdini plugins and later on create a cmake file to regenerate it. I looked at all tutorials i could find but am now stuck on a strange issue. Problem: The compilation process inside VS simply stops during the object creation stage for SOP_Star.C at this point: ................ 1>..\..\source\SOP_Star.C(213): warning C4244: '=' : conversion from 'double' to 'float', possible loss of data 1>..\..\source\SOP_Star.C(229): warning C4244: '=' : conversion from 'fpreal' to 'float', possible loss of data ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== No errors of any kind, just lots of warnings (which is more or less normal, right!?). Setup: OS: Win7x64 Houdini: 13.0.260 built with VC11 Test Plugin: SOP_Star.C IDE: VS2013 with platform toolset set to VC110 (VS2012 which my H13 is built against) Command Line options: I was messing with this all day. Basically i just copied and/or corrected the settings i determined by running hcustom -c SOP_Star.C and hcustom -m SOP_Star.C into the Command Line options of Visual Studio. hcustom -e SOP_Star.C successfully builds the project. It also shows that it runs hcompile which then start the VS compiler with an additional cmd line option called -DUT_DSO_TAGINFO that hcustom -c doesnt show!? CL command line options: All options (grey field in Visual Studio/Properties/C/C++/CommandLine): /GS /GL /W3 /Gy /Zc:wchar_t /Zi /Gm- /O2 /sdl /Fd"x64\Release\vc110.pdb" /fp:precise /D "WIN32" /D "NDEBUG" /D "_WINDOWS" /D "_USRDLL" /D "SOP_STAR_EXPORTS" /D "_WINDLL" /D "_UNICODE" /D "UNICODE" /errorReport:prompt /WX- /Zc:forScope /Gd /Oi /MD /Fa"x64\Release\" /EHsc /nologo /Fo"x64\Release\" /Fp"x64\Release\sop_star.pch" Additional options (white field in Visual Studio/Properties/C/C++/CommandLine)....taken from hcustom -c: -nologo -TP -Zc:forScope -DVERSION="13.0.260" -DI386 -DWIN32 -DSWAP_BITFIELDS -D_WIN32_WINNT=0x0501 -DWINVER=0x0501 -DNOMINMAX -DSTRICT -DWIN32_LEAN_AND_MEAN -D_USE_MATH_DEFINES -D_CRT_SECURE_NO_DEPRECATE -D_CRT_NONSTDC_NO_DEPRECATE -D_SCL_SECURE_NO_WARNINGS -DBOOST_ALL_NO_LIB -DSESI_LITTLE_ENDIAN -DAMD64 -DSIZEOF_VOID_P=8 -DFBX_ENABLED=1 -DOPENCL_ENABLED=1 -DOPENVDB_ENABLED=1 -I . -I "D:/tools/SIDEEF~1/HOUDIN~1.260/toolkit/include" -I "C:/PROGRA~2/MICROS~3.0/VC/include" -I "C:/Program Files (x86)/Windows Kits/8.0/Include/um" -I "C:/Program Files (x86)/Windows Kits/8.0/Include/shared" -wd4355 -w14996 -O2 -DNDEBUG -MD -EHsc -GR -bigobj Anybody any ideas? Has anybody built plugins with VC11 from a Visual Studio Project successfully? Or does anybody even have a cmake file ready to generate VS2012 projects that successfully compile? Thanks in advance! Timm
