OctaneRender 2022.1 for Houdini beta build 2022.1.0.1 XB2

Sub forum for plugin releases

Moderator: juanjgon

User avatar
juanjgon
Octane Plugin Developer
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

ThomasHelzle wrote: in this and the previous build, I get the following error on each render I start in the IPR:
Hmm, I can't reproduce this problem in XB2. Are you sure that it happens if you create the scene from the scratch using the XB2 build? Can you please share an example scene with this issue?

Thanks,
-Juanjo
ThomasHelzle
Licensed Customer
Posts: 13
Joined: Fri May 28, 2010 4:10 pm
Location: Berlin
Contact:

I just tried and yes, it still happens with a newly created scene with XB2, find it here:
http://screendream.de/work/OctaneErrorMessages.zip
Basically I get an error for every texture in the scene.

Thanks and cheers,

Tom

Edit: The renderings are actually fine, it's just the error messages that make me curious if everything is as it should... ;-)
User avatar
juanjgon
Octane Plugin Developer
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

Post updated to include plugin builds for the new Houdini 19.5.303

Thanks,
-Juanjo
ThomasHelzle
Licensed Customer
Posts: 13
Joined: Fri May 28, 2010 4:10 pm
Location: Berlin
Contact:

Thanks for the superquick update to 19.5!

I'm still getting the same errors as before in 19.5 with the new builds of Octane with a newly created scene...

Any idea?

Cheers,

Tom
vurt
Licensed Customer
Posts: 61
Joined: Thu Dec 02, 2021 10:27 am

ThomasHelzle wrote:Thanks for the superquick update to 19.5!

I'm still getting the same errors as before in 19.5 with the new builds of Octane with a newly created scene...

Any idea?

Cheers,

Tom

hey, yeah, I'm getting the same errors in log

DaylightTexture void __cdecl OP_Parameters::evalStringT(class UT_String &,const class UT_StringRef &,int,double,int) const: Invalid parameter name A_IMAGE_CHOSEN_LAYER_NAME
DaylightTexture __int64 __cdecl OP_Parameters::evalIntT(const class UT_StringRef &,int,double,int) const: Invalid parameter name A_IES_PHOTOMETRY_MODE
DaylightTexture void __cdecl OP_Parameters::evalStringT(class UT_String &,const class UT_StringRef &,int,double,int) const: Invalid parameter name A_IMAGE_CHOSEN_LAYER_NAME
DaylightTexture __int64 __cdecl OP_Parameters::evalIntT(const class UT_StringRef &,int,double,int) const: Invalid parameter name A_IES_PHOTOMETRY_MODE
User avatar
juanjgon
Octane Plugin Developer
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

ThomasHelzle wrote:I'm still getting the same errors as before in 19.5 with the new builds of Octane with a newly created scene...
I've found the problem! It will be fixed in the next build.

Thanks for reporting it!
-Juanjo
ThomasHelzle
Licensed Customer
Posts: 13
Joined: Fri May 28, 2010 4:10 pm
Location: Berlin
Contact:

Awesome - thank you! :-)

Cheers,

Tom
luminouspowerhouse
Licensed Customer
Posts: 33
Joined: Thu Nov 20, 2014 3:20 am

Cant'find OCIO, dropdown menu says "no entries" please see screenshots
Win 19.5.303
Attachments
Screenshot_2.jpg
Screenshot_1.jpg
User avatar
juanjgon
Octane Plugin Developer
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

Select the "ocioDisplayName" param, even to choose the default value. This is the only way to populate the other menus.

-Juanjo
luminouspowerhouse
Licensed Customer
Posts: 33
Joined: Thu Nov 20, 2014 3:20 am

Juanjo, changing any parameters under IMAGER (in Octane RenderTarget), like ocioView, adding LUT, etc - doesn't do any changes in IPR, even with full scene reload.
does yours work as expected?
Post Reply

Return to “Releases”