OTOY Forums

juanjgon wrote:

imensah wrote:Is disabling the scene export option and cloud rendering option temporary or not?
Why can't we render on the cloud with the same render size limitations? Does not make sense.

Because currently once the scene is the cloud you can change the render resolution, or you can load the scene in Standalone and change the render resolution. These things are out of the plugin control, so at least in this first releases, to be safe about the violation of the Houdini Indie license, the scene export and cloud functions are disabled.

As far I know, other render plugins have the same limitations about scene exporting in the Indie version.

-Juanjo

It seems like this is happening across a few renderers. As far as exporting goes, does this also apply to exporting out individual things like meshes and materials or is it full scene based? I could see them not wanting full scene export, but it'd be nice if the simpler things came through.

juanjgon wrote:At least here this problem seems to be fixed now.

Yes, thanks, it seemed to be fixed about 12h ago or longer.
Everything fine now with the shop (here), thanks

Hi juanjgon,

I want do dive into Houdini 15.5 Indie and have a few questions:

1. For OS X it says 10.10 - is it minimum so it will also work with 10.11 ?
2. What means scene export disabled - ORBX not possible? why? The Houdini Indie normal export alembic + fbx will work?
3. Why is ORC disabled for Indie?
4. Why Houdini plugin has no icons (only text buttons) for the OR settings like the other plugins (would be look better and quicker use I think) ? (because Houdini is mostly code based input and different from only design driven 3D apps)
5. Is there still the complicated way to install via env file and no easy install dmg like other plugin - double click installer and done? (because Houdini is mostly code based input and different from only design driven 3D apps)
6. Are luminous polys work native so automatic emission polys add light to the scene like the other plugins?
7. Are particles like clouds, fire, explosions as volumes work (via OR sphere item I have read) so they are displayed same as in mantra?
8. Are render passes supported?
9. Will the Photoshop extension also work with Houdini for automatic PS layer setup from passes?

C-You wrote:Hi juanjgon,

I want do dive into Houdini 15.5 Indie and have a few questions:

1. For OS X it says 10.10 - is it minimum so it will also work with 10.11 ?
2. What means scene export disabled - ORBX not possible? why? The Houdini Indie normal export alembic + fbx will work?
3. Why is ORC disabled for Indie?
4. Why Houdini plugin has no icons (only text buttons) for the OR settings like the other plugins (would be look better and quicker use I think) ? (because Houdini is mostly code based input and different from only design driven 3D apps)
5. Is there still the complicated way to install via env file and no easy install dmg like other plugin - double click installer and done? (because Houdini is mostly code based input and different from only design driven 3D apps)
6. Are luminous polys work native so automatic emission polys add light to the scene like the other plugins?
7. Are particles like clouds, fire, explosions as volumes work (via OR sphere item I have read) so they are displayed same as in mantra?
8. Are render passes supported?
9. Will the Photoshop extension also work with Houdini for automatic PS layer setup from passes?

Hi!

1. Yes, the plugin should work in 10.11 without problems. The only limitation in OSX is that the OpenGL IPR window is not available yet. The IPR in OSX works in MPlay.
2. The ORBX export is disabled in Indie due to the Indie license restrictions. An ORBX animated file can be rendered at any resolution in Standalone or in the Cloud. All the external renders for Indie have the same limitation about exporting full scenes that can be rendered outside Houdini.
3. The same. In the cloud you could change the render resolution, violating the Indie license.
4. The plugin has icons in the shelf. https://docs.otoy.com/Houdini/?page_id=691
5. Nope, you need to add the plugin paths to the houdini.env file. From my point of view it is not safe edit this file from a installer. It can has other plugin installations that can be broken.
6. You can enable any object as light emitter using the object spare parameters. https://docs.otoy.com/Houdini/?page_id=1358
7. Yes, the plugin supports the direct rendering of the Houdini volume primitives.
8. Yes, with the same workflow used in Standalone or in the other plugins.
9. Yes.

Thanks!
-Juanjo

Hi juanjgon

I'm interested to use Houdini in my workflow and would like a trial of the Plugin Version 3. Where can I download it?

Thanks
Cyrill

I want to release the plugin demo version this week. I'll post the links here once ready.

Thanks,
-Juanjo

The links to the Octane 3 plugin demo version have been added to the first post.
Thanks for your patience.

-Juanjo

Hi juanjgon,

I have purchased Houdini 15.5 Indie and the OR v3 Plugin now and I am new to Houdini.
Only have the Houdini plugin installed - no standalone (but have license from a v3 combo)
and for the other host I also have only installed (via installer - perfect) the plugin and its
good - face_off said. And I ask you before about the Indie and OS X 10.11 - and so it should
work, because in the 15.5 Indie now octane is available - right?

So what I have ask before why there is no standard installer like in my other plugin? You said
its the only way for Houdini to get everything done with an edited env file.

But I have to say I know why I was afraid of this method. Because everything is explained only
for WIN and nothing for OS X - I am way to stupid and total lost in the forest. I have to work with
this great thing ASAP, but now everything is broken, because no documentation or video
shows the install procedure. No matter what I have tried - there is no octane things in Houdini.

Please help very quick and make a really step by step help (video would be awesome) for
us OS X user. I really don´t know where to put the plugin files and what path into the env.
In WIN there goes everything in mydocs - but in OS X there is nothing inside the user documents
folders. I found the env file in the hidden library/preferences/houdini/15.5/houdini.env

In the manual only written to put plugin files somewhere, but in the video tutorial from BW:
https://vimeo.com/154676990
he puts the plugin files into the mydocs at WIN - should I put everything inside the hidden library/preferences/houdini/15.5?
What path has to be written in the env - the houdini app (in OS X app folder)? or the plugin folder location?

I am total confused and frustrated now and hope you can help - I have purchased and want use it.
Please show very detailed with correct OS X path from the main hard disk starting - one single wrong
letter could break the whole thing.

And one more question please - when will the IPR be available for OS X? Will MPlay for octane be interactive
or opens it every time again if I change some materials and have to refresh again and again?

Sorry, but the installation instructions in the docs are written for Windows, Linux and OSX.
https://docs.otoy.com/Houdini/?page_id=39

Anyway, the steps to install the plugin in OSX are really easy:

- Download the plugin OSX .zip file. It has several plugin versions inside.
- If you are working with H15.5, you should extract the "Octane_3.00.20.0_Houdini_15.5.480_OSX" folder to any place in your HD. For example to your computer /Applications directory.
- As you have found, in your user home folder, the houdini.env file is located in "library/preferences/houdini/15.5/houdini.env"
- Edit this file, adding the HOUDINI_PATH variable pointing to the plugin folder. If you have extracted the plugin folder in your /Applications directory it should be: Done. Now, after start Houdini, in the menu bar you should see an Octane menu, and in the shelf menu you should be able to find and add the Octane shelf icons.

-Juanjo

C-You wrote: And one more question please - when will the IPR be available for OS X? Will MPlay for octane be interactive
or opens it every time again if I change some materials and have to refresh again and again?

The IPR working inside the MPlay has the same interactivity that working in the custom OpenGL window. It can be only a bit slower, but it works fine so far.

-Juanjo