Jump to content

Search the Community

Showing results for tags 'Compiling'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Lounge/General chat
    • Education
    • Jobs
    • Marketplace
  • Houdini
    • General Houdini Questions
    • Effects
    • Modeling
    • Animation & Rigging
    • Lighting & Rendering + Solaris!
    • Compositing
    • Games
    • Tools (HDA's etc.)
  • Coders Corner
    • HDK : Houdini Development Kit
    • Scripting
    • Shaders
  • Art and Challenges
    • Finished Work
    • Work in Progress
    • VFX Challenge
    • Effects Challenge Archive
  • Systems and Other Applications
    • Other 3d Packages
    • Operating Systems
    • Hardware
    • Pipeline
  • od|force
    • Feedback, Suggestions, Bugs

Product Groups

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Skype


Name


Location


Interests

Found 3 results

  1. Hello everybody! If we want to create geometry using VEX we can pipe a null node into an Attribute Wrangle and in the latest we can use functions such as addpoint() to birth geometry. One requirement is that we have to set it to run over Detail (only once). The problem comes when I want to do this using a .vfl file and compile into VEX and use a VEX node that points to the compiled file. Geometry won't be created. It is strange because I know VEX just work on points, not on Detail so I have two questions: 1. Why do we have to run the Attribute Wrangler in mode "run over Detail (only once)"? Why not points? 2. Is there a way to use a pragma flag or something to tell the vcc compiler that this code must run over Detail and only once? Thanks for your help in advance. Ramon.
  2. I'm trying to compile the Field3D plugin on windows in order to transfer smoke from Houdini to Fume. This is the command that I'm currently running from the field3d directory where f3dtools.C file is located: hcustom f3dtools.C -i c:/ie/ark/programs/houdini/houdini13.0/dso -L "C:/Program Files (x86)/Microsoft SDKs/Windows/v7.0A/Lib/x64/" -L "C:/Program Files (x86)/Microsoft SDKs/Windows/v7.0A/Lib/" When compiled with no change to the code, the compiler complains about error C2664: 'void GU_Detail::sortPrimitiveList(GU_AxisType)' : cannot convert parameter 1 from 'fpreal32 *' to 'GU_AxisType' If I comment out this line, then the compiler gives a classic fatal error LNK1120: 25 unresolved externals. It seems like almost all of these errors are LNK2019: unresolved external symbol in the f3dtools object file, followed by a string beginning with: "__declspec(dllimport) public: class std::basic_string . . . . . ." Is there a precompiled version of this plugin somewhere? I'm surprised it's not just included by default, without it there's no way to get smoke out of Houdini which is a big barrier to adoption. Thanks for any help you can provide!
  3. Hey guys, I set MSVCDir to the following two locations, but it does not work. Where is the correct location? Thanks C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\Tools C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE
×
×
  • Create New...