OctaneRender™ Standalone 2.11.1

[BroAugustine]

Marcus,

I just wanted to reiterate about the crashes when exiting Lua and report another bug that might be related. The scripts run and do what they are supposed to do. It's just if you ever try to close or end the script, Octane crashes.

Here is another Lua bug which might have do do with the crashes seeing as how the scripts aren't being parsed the same between versions. In Octane v2.05 all the shortcut keys show up for the scripts I use. When I run v2.11.1, three of the scripts are missing the shortcut keys. This is even after running the 'Reload Scripts' menu item. I did note however that if I move the shortcut key directive such as

Code: Select all

-- @shortcut ctrl + w

to the first line in each of the three scripts, then the shortcuts reappeared except for Octane Render Walkthrough.lua which only worked after I added a blank line after the first line.

[grimm]

I understand that you guys haven't had a chance to look at this yet, but I thought I would add in my experience on the possibility that this might help. I received my GTX980 and have it installed. I was able to install the 343.22 version of the Nvidia driver and both my GTX460 and the 980 can be seen in the Nvidia Xsettings tool. I have made sure that I have CUDA installed (version 6.5) and X is working (on the 460). When I load up Octane 2.11.1 and go to the card preference, it can see that I'm running CUDA 6.5 but it doesn't see either the 460 or the 980.

I'm just trying to figure out if it's a problem with Octane or if my setup is still having problems. Thanks,

Jason

[momade]

bug obj export
2.11.1

maybe a scale problem?
have you tested to increase your rey-epsilon by powers of ten to lets say 0.001? or double check your imp/exp obj-scale. it could be that your model gets imported waaaaaaay to big...

br.
mo

[roeland]

Marcus,

I just wanted to reiterate about the crashes when exiting Lua and report another bug that might be related. The scripts run and do what they are supposed to do. It's just if you ever try to close or end the script, Octane crashes.

Here is another Lua bug which might have do do with the crashes seeing as how the scripts aren't being parsed the same between versions. In Octane v2.05 all the shortcut keys show up for the scripts I use. When I run v2.11.1, three of the scripts are missing the shortcut keys. This is even after running the 'Reload Scripts' menu item. I did note however that if I move the shortcut key directive such as

Code: Select all

-- @shortcut ctrl + w

to the first line in each of the three scripts, then the shortcuts reappeared except for Octane Render Walkthrough.lua which only worked after I added a blank line after the first line.

shortcutKeys.png

We could reproduce and fix the crashing issue.

The missing hotkey is another issue. We had to change a few things in the header parsing code, and the current version will stop parsing the header at the first line which doesn't start with "--", including blank lines. We can make it skip over blank lines again in the next release.

--
Roeland

[coilbook]

with coherent mode enabled first frame freezes at the end during animation render with the following. it works fine with coherent disabled
slave .... (5) lost 1.0 samples
slave .... (5) lost 2.0 samples
slave ..... (3) lost 2.0 samples
slave ..... (5) lost 1.0 samples
so forth

[Karba]

with coherent mode enabled first frame freezes at the end during animation render with the following. it works fine with coherent disabled
slave .... (5) lost 1.0 samples
slave .... (5) lost 2.0 samples
slave ..... (3) lost 2.0 samples
slave ..... (5) lost 1.0 samples
so forth

We are waiting for the scene.

[BorisGoreta]

So why exactly did you get rid of black level input in color correction node ? Now many of my materials in my projects ( real client work ) don't look as they should any more. Your explanation was that only small amount of materials in LiveDB uses this, nobody who uses Octane plugin uses LiveDB so this is not the way to conclude things. And nobody does serious work in Octane Standalone because it is very limited compared to 3D packages and their respective Octane plugins. So I am not happy that my renders don't look as they shold because you removed this feature.

I also don't understand "there is not enough pins" explanation. Is this limitation of Octane Standalone GUI or the render engine ? If it is the first could you still leave this open for Octane plugins. How come diffuse material has 10 input pins and colorcorrector node only 6 ? Is this dependant on the input type ?

[jan kudelasek]

with coherent mode enabled first frame freezes at the end during animation render with the following. it works fine with coherent disabled
slave .... (5) lost 1.0 samples
slave .... (5) lost 2.0 samples
slave ..... (3) lost 2.0 samples
slave ..... (5) lost 1.0 samples
so forth

We are waiting for the scene.

hi I have similar problem. Frame freezes at the end after several frames. same with coherent disabled. It came with 2.10. I use to multiple gpu slave and 3ds max plugin.

[Karba]

So why exactly did you get rid of black level input in color correction node ? Now many of my materials in my projects ( real client work ) don't look as they should any more. Your explanation was that only small amount of materials in LiveDB uses this, nobody who uses Octane plugin uses LiveDB so this is not the way to conclude things. And nobody does serious work in Octane Standalone because it is very limited compared to 3D packages and their respective Octane plugins. So I am not happy that my renders don't look as they shold because you removed this feature.

I also don't understand "there is not enough pins" explanation. Is this limitation of Octane Standalone GUI or the render engine ? If it is the first could you still leave this open for Octane plugins. How come diffuse material has 10 input pins and colorcorrector node only 6 ? Is this dependant on the input type ?

This is a general engine limitation, not standalone one.
We had to choose between removing some pins and speed drop.
You can try to play with gamma, it should bring your renders back.

[BorisGoreta]

Ah, ok then, I am all for speed too, this is top priority.