Render to mplay problem

Sub forum for bug reports

Moderator: juanjgon

Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.


All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Stefan
Licensed Customer
Posts: 23
Joined: Thu Dec 17, 2015 2:01 pm

Hi Juanjo,
thanks for checking and the tip about unchecking "render to mplay" makes my hopes fly high again.
I am working on Win7.
User avatar
juanjgon
Octane Plugin Developer
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

What houdini version are you using? I want to send to you a test build with more log messages to see if I can find where is the problem.

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

I think that I have found the problem.

Please check your Houdini configuration folder ($HOME/houdini15). If the at some point in the past your MPlay application have crashed, sometimes it could leave in this folder a file named something like ".flipbook_lock.computer_name". Remove it and the MPlay should work again without problems.

-Juanjo
Attachments
image-000983.jpg
Stefan
Licensed Customer
Posts: 23
Joined: Thu Dec 17, 2015 2:01 pm

Thank you for investigating our problem!
Yes, I have that *flipbook*- file in that folder, so probably the issue is solved.
I cannot test it right now though, as I have an IPR in progress these days.
-regards Stefan
Stefan
Licensed Customer
Posts: 23
Joined: Thu Dec 17, 2015 2:01 pm

I came around to testing again today.
And deleting that file did the trick for me!

problem solved - thanks again!
User avatar
juanjgon
Octane Plugin Developer
Posts: 8867
Joined: Tue Jan 19, 2010 12:01 pm
Location: Spain

Stassius wrote:And another one. "Save parameter as permanent defaults" is not working. Say in render target node or in Octane rop node. And when i try to save preset, it shows visualisation menu. Is it even possible to use presets? It would be handy.
I am testing the "save parameters as permanent defaults" feature here with the Octane 3 plugin and it seems to work fine. Does anyone else have this problem?

-Juanjo
Stassius
Licensed Customer
Posts: 22
Joined: Tue Dec 22, 2015 8:18 pm

Right now permanent defaults works, yes. I thought you fixed the issue already.
Post Reply

Return to “Bug Reports”