Vrayprocedural In H9 - HDK : Houdini Development Kit - od|forum Jump to content

Vrayprocedural In H9


ivan

Recommended Posts

anybody figure out how to use 'em?

The HDK headers have tons of new stuff in 'em, so I know it's still active.

I got my old VRAY_Procedural to compile now, and I've installed it just like in H8.1,

but the object doesn't have "mantra procedurals" as a regular option.

It seems to be available in "obsolete houdini 8" which doesn't sound very promising....

Link to comment
Share on other sites

  ivan said:
anybody figure out how to use 'em?

The HDK headers have tons of new stuff in 'em, so I know it's still active.

I got my old VRAY_Procedural to compile now, and I've installed it just like in H8.1,

but the object doesn't have "mantra procedurals" as a regular option.

It seems to be available in "obsolete houdini 8" which doesn't sound very promising....

There are geometry SHOPs. So you probably need to make a SHOP.

This allows you to do things like point instance your procedural if it makes sense (things like delayed read archives do make sense).

Link to comment
Share on other sites

I kinda tried this. I put down a "mantra program procedural" shop and put demobox in the program field.

Then I attatched it to my object under the geometry tab, where it says "Procedural Shader"

no dice. squat nada. din't work.

it spit this at me:

sh: line 0: exec: demobox: not found

mantra: program[/obj/geo1] unable to load geometry

I tried different spellings/capitolizations....

it seems to be going in to the IFD:

ray_start object # {

ray_transform 1 0 0 0 0 1 0 0 0 0 1 0 0 0 0 1

ray_procedural -m -0.5 -0.5 -0.5 -M 0.5 0.5 0.5 program demobox

ray_geometry /obj/geo1/point1

ray_property object name "/obj/geo1"

ray_end # }

and if I do a mantra -V5, I can see the procedural is getting registered:

Registering procedural 'demobox'

  crunch said:
There are geometry SHOPs. So you probably need to make a SHOP.

This allows you to do things like point instance your procedural if it makes sense (things like delayed read archives do make sense).

Edited by ivan
Link to comment
Share on other sites

  ivan said:
I kinda tried this. I put down a "mantra program procedural" shop and put demobox in the program field.

Then I attatched it to my object under the geometry tab, where it says "Procedural Shader"

no dice. squat nada. din't work.

it spit this at me:

sh: line 0: exec: demobox: not found

mantra: program[/obj/geo1] unable to load geometry

I tried different spellings/capitolizations....

it seems to be going in to the IFD:

ray_start object # {

ray_transform 1 0 0 0 0 1 0 0 0 0 1 0 0 0 0 1

ray_procedural -m -0.5 -0.5 -0.5 -M 0.5 0.5 0.5 program demobox

ray_geometry /obj/geo1/point1

ray_property object name "/obj/geo1"

ray_end # }

and if I do a mantra -V5, I can see the procedural is getting registered:

Registering procedural 'demobox'

Close...

You've chosen the "program" procedural, not the "demobox" procedural. The program procedural is a different procedural which runs an external application and reads geometry from stdin (thus the failure to be able to run the "demobox" application).

You need to create a new SHOP for your procedural.

As a quick way to check, you can use the "generic geometry" SHOP and fill in the command line you want...

Link to comment
Share on other sites

ok... makes sense... now how would I write a geometry SHOP?

should be mostly just a UI... do I just make a .ds script and put it somewhere?

according to the help, there is no geometry context, just displace,fog,light,photon,shadow,surface,chop,cop,image3d,pop,and sop.

no examples. The "code" page on the Type Properties states "this operator is not implemented in code"...

  crunch said:
Close...

You've chosen the "program" procedural, not the "demobox" procedural. The program procedural is a different procedural which runs an external application and reads geometry from stdin (thus the failure to be able to run the "demobox" application).

You need to create a new SHOP for your procedural.

As a quick way to check, you can use the "generic geometry" SHOP and fill in the command line you want...

Link to comment
Share on other sites

  ivan said:
ok... makes sense... now how would I write a geometry SHOP?

should be mostly just a UI... do I just make a .ds script and put it somewhere?

according to the help, there is no geometry context, just displace,fog,light,photon,shadow,surface,chop,cop,image3d,pop,and sop.

no examples. The "code" page on the Type Properties states "this operator is not implemented in code"...

Good question.

In fact, it is possible to create a .ds file and put it somewhere... But I'd have to dig around for the files and it's quite problematic.

The easier way is to go to the Operator Type Manager (Windows Menu)

In the "filter" type "program" so that you can find the program procedural shader quickly.

Once you've found Shop/vm_geo_program, use the RMB over the entry and choose "Copy..."

This allows you to create a new procedural shader. You can edit the parameters to your heart's content.

Link to comment
Share on other sites

hokay, I have a new procedural, but it inherits what it puts into the IFD from the copied SHOP, i.e

I make a "demobox" SHOP by copying a metapoly SHOP and renaming it, etc... then attatch the demobox to an object, and the IFD file will put this in:

ray_start object # {

ray_transform 1 0 0 0 0 1 0 0 0 0 1 0 0 0 0 1

ray_procedural metapoly

ray_geometry /obj/geo1/point1

ray_property object name "/obj/geo1"

ray_end # }

even though my new shop doesn't have "metapoly" in it anywheres....

how do I control what the SHOP puts in to the IFD?

  crunch said:
Good question.

In fact, it is possible to create a .ds file and put it somewhere... But I'd have to dig around for the files and it's quite problematic.

The easier way is to go to the Operator Type Manager (Windows Menu)

In the "filter" type "program" so that you can find the program procedural shader quickly.

Once you've found Shop/vm_geo_program, use the RMB over the entry and choose "Copy..."

This allows you to create a new procedural shader. You can edit the parameters to your heart's content.

Edited by ivan
Link to comment
Share on other sites

  ivan said:
hokay, I have a new procedural, but it inherits what it puts into the IFD from the copied SHOP, i.e

I make a "demobox" SHOP by copying a metapoly SHOP and renaming it, etc... then attatch the demobox to an object, and the IFD file will put this in:

ray_start object # {

ray_transform 1 0 0 0 0 1 0 0 0 0 1 0 0 0 0 1

ray_procedural metapoly

ray_geometry /obj/geo1/point1

ray_property object name "/obj/geo1"

ray_end # }

even though my new shop doesn't have "metapoly" in it anywheres....

how do I control what the SHOP puts in to the IFD?

Check the "Shader name" in the type properties...

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...