OctaneRender 2 for Poser (Windows/OSX) [OBSOLETE]

[samhal]

1. You can Open a new empty scene.
2. Create an Infinite light.
3. Open Octane plugin (this will convert the light to Daylight)
4. Close Octane plugin.
5 .Go in Edit/General Preferences and check "Launch to prefered scene", and click the button Set Preferred Scene.

Now every time you Open a new scene/document the Daylight will be there.
You can even optimized it.
Before you click the button "Set preferred Scene", you can under the Daylight parameters lock the zRotating. Set it to zero and double click the parameter to edit it. Set Value and Limits to zero and check Force Limits and click OK. As you don't need zRotation it's better to make sure it doesn't move or you can get really in trouble if you use all 3 axis'. You only need xRotation and yRotation. You can also set Scale to 15 or 20 procent to better view the light in teh scene.
Then hit the button Set Preferred Scene and all these new settings are in every new scene/document.

GREAT tips! Thanks!

[Zay]

Or save the Daylight to the library.

[wimvdb]

24_06_14 - 01.jpg

Now how obvious was that... LOL... you'd think after half an hour I'd know how to work the internet eh!

An error though using this new Poser and Standalone version.

Got the same problem
For me it happens if import a shader from disk (like redspec or my own sss shaders)
Looking at the standalone thread there seems to be a problem with "in-memory" images, which might just be the case here with the import at "keep exising textures"

[face_off]

Deane - if you are looking for the correct Octane Standalone version to match the current Poser plugin version - check the first post on this thread - it is listed there.

An error though using this new Poser and Standalone version.

Yes it a problem where if you do not have an texturemap plugged into an Image, Alphaimage or Floatimage node, AND you are running a 600 series card or later, rendering fails with a cuda 719 error. So I have removed the above release link from the first post in this forum. If you still want to try it - the 64 bit version can be downloaded from http://render.otoy.com/customerdownload ... _Win64.exe.

Otoy will release a patch for this ASAP and I will then post a working plugin version.

Paul

[face_off]

I have refreshed the installers at the top of this thread with:

2.1.0.19
- Compiled against the revised Octane 2.01
- Fixed issue where Render Region was not being clear when refreshing the scene
- Fixed issue when unticking "Mouse Wheel Moves Slider" was not disabling mouse wheel slider changes (and the default for this option is now OFF)
- Fixed issue where "Paste to all materials named ???" was not re-selecting the highlighted material

Paul

[wimvdb]

2.0.1.19 fixed the cuda error 719 bug
Thanks for the quick update on the pluging

[wimvdb]

It looks like there is still a 719 error when you go over 68 grayscale maps.
I am not sure though since he grayscale map counter is at the wrong place and does not seem to give the actual figure
The 719 error occurs when I add one and goes away when I remove it
Still 1.1GB free in VRAM according to the viewport report

[wimvdb]

It is not number of grayscale maps which causes the cuda 719 error.
There must be some other factor causing it. As soon as I go over 4.8MB it starts to happen (using a dual Titan configuration)

Anyone know of any other limitation besides VRAM?

[Krew]

It is not number of grayscale maps which causes the cuda 719 error.
There must be some other factor causing it. As soon as I go over 4.8MB it starts to happen (using a dual Titan configuration)

Anyone know of any other limitation besides VRAM?

I have a dual Titan configuration also, so I thought I would do a test for you and load up 4.8GB worth of stuff and see what happened. Before I got to that point though, I noticed something. In my Octane Render Viewport, the memory allocation reports as follows for the scene I have loaded up:

Mem: 2941/6144
Free Memory: 1876

So, if I'm using 2941MB out of 6144MB of VRAM, and I have 1876MB free, it looks like the plugin is only addressing 4817MB of memory(?), even though its showing 6144MB of total VRAM (2941 + 1876 = 4817). Interesting. Since that number (4.8GB) compares to the point at which you're having problems, it looks like that might be the issue (?)

Edited to add: A couple of days ago I went WAY over 68 greyscale maps and I didn't get a 719 error, I just got the standard dialog about exceeding the texture limit. So at least from my experience I can confirm that exceeding the greyscale limit isn't causing the error. Hope that helps.

[Krew]

I have a dual Titan configuration also, so I thought I would do a test for you and load up 4.8GB worth of stuff and see what happened. Before I got to that point though, I noticed something. In my Octane Render Viewport, the memory allocation reports as follows for the scene I have loaded up:

Mem: 2941/6144
Free Memory: 1876

So, if I'm using 2941MB out of 6144MB of VRAM, and I have 1876MB free, it looks like the plugin is only addressing 4817MB of memory(?), even though its showing 6144MB of total VRAM (2941 + 1876 = 4817). Interesting. Since that number (4.8GB) compares to the point at which you're having problems, it looks like that might be the issue (?)

Edited to add: A couple of days ago I went WAY over 68 greyscale maps and I didn't get a 719 error, I just got the standard dialog about exceeding the texture limit. So at least from my experience I can confirm that exceeding the greyscale limit isn't causing the error. Hope that helps.

Okay, I realize now that I was mistaken because I forgot to take into account that my system is using VRAM for other purposes while I'm using the Octane Plugin (should have remembered that!). So, you can probably disregard my post