OctaneRender® for Poser (Windows) - build 1.20.2 [OBSOLETE]

[wimvdb]

First of all - make sure that you have at least one of your videocards set to low or medium priority. If left at high, it will effectively kill the UI performance
With regards to large scenes (like stonemason's) - there are two factors in play here: The amount of textures and the actual video memory those textures need. No matter how many cards you have, it will take use the lower value of those cards as a limit. So if one card has 2GB with 64 texture slots and one card has 4GB with 144 texture slots, both cards will use the lower values (2GB and 64 textures slots). This is because both cards need to have all of these in VRAM

So upgrading your setup to Titan cards definitely will increase the scene size you can load since it is Nvidia's most capable cards with lots more memory and - I think - more texture slots as the 690
And of course it will be faster as well

[blueeagle327]

Thanks you so much for your explanation, I will tell you as soon as I get my new cards how it render. By the way I know everyone ask for this, but could be great a tutorial (beginner and advance) for octane. And if for poser plug ing. The better

Thanks again

Pablo

[face_off]

Hi Pablo

Is the plugin actually reporting that you are low on memory? The memory stats are on the button status bar of the OctaneRender Viewport window. Mouseover the statusbar for additional info.

Also, make sure you use your on-board graphics as the Windows dispaly adapter if possible. If not, turn the render priority to low in the Devices tab.

If you are running out of memory, there is a python script included with the plugin which will reduce the texturemap sizes, so you can same some VRAM that way.

Paul

[blueeagle327]

Thanks Paul, Already have my render priority in low. I will render tomorrow an scene with the python script to compress the texture maps, and I will tell you what happened, but I will pray for my new Titans came sooner

Thanks

Pablo

[RGUS]

Can youi please, please de-highlight nodes in the material list window when you change the values in the node type window, whether keyed in values or mouse wheel scroll values.
Example... I change lots of 'gamma' values back to 1.00, by keying in the value... then use the mouse wheel to scroll to the next material only to find the scrolling changes the value I just keyed in for say 'X:'... I know... maybe my workflow is not to great.

[face_off]

Can youi please, please de-highlight nodes in the material list window when you change the values in the node type window, whether keyed in values or mouse wheel scroll values.
Example... I change lots of 'gamma' values back to 1.00, by keying in the value... then use the mouse wheel to scroll to the next material only to find the scrolling changes the value I just keyed in for say 'X:'... I know... maybe my workflow is not to great.

Yes, I agree - the mousewheel to change the slider gets confused with scrolling the tree. A lot of time and much discussion was had about this during beta testing. In summary - the system at the moment is about as far advanced as the Poser wx.python can support - so the real decision is whether to remove mousewheel movement of the sliders or not. Maybe this could be an option in the Configuration? A build against Octane 1.22 is being tested at the moment - and there are two issues stopping it's release - but hopefully it will be available this week or next.

Paul

[ThetaGraphics]

I get this error whenever I try to render TarbosaurusDR ( http://www.daz3d.com/tarbosaurusdr )

"Eye left has a mismatch between vertices and textures and it will not be loaded into the Octane Scene."

I've tried turning off the visibility of both eyes, so that they hopefully wouldn't load in, but I still get the same message.

I've also tried exporting the entire model as an obj and loaded it back in, only to get the same message (except with the obj file's name).

Is there a solution to this?

(I am using version 1.20.2.7 of the plugin)

[face_off]

I get this error whenever I try to render TarbosaurusDR ( http://www.daz3d.com/tarbosaurusdr )

"Eye left has a mismatch between vertices and textures and it will not be loaded into the Octane Scene."

I've tried turning off the visibility of both eyes, so that they hopefully wouldn't load in, but I still get the same message.

I've also tried exporting the entire model as an obj and loaded it back in, only to get the same message (except with the obj file's name).

Is there a solution to this?

(I am using version 1.20.2.7 of the plugin)

The eye may have only be partially uv mapped. With Poser, when geometry is partially uv mapped it is not possible to determine which uv's belong to which vertices. If you export to 3ds max format and import back in that might fix it. Ultimately the person modelling this figure should uv map all the vertices.

Paul

[ThetaGraphics]

Thanks. Well, I managed to get the dino to at least exist in the scene by exporting the obj from Hexagon without uv maps. No textures, but fortunately my current project didn't need them. (Would be nice for the future, but oh well.) However, it brings to light another issue I have been having, and before you say that it is simply a modeling issue, I have been having this problem in almost all of my renders, regardless of the model.

Basically, I'm getting shadow artifacts all over the models. Sometimes they seem to follow polygon lines, and sometimes they don't. (I think that depends on what the smoothing is set to, but they appear regardless of whether smoothing is on or off.) It tends to appear more on lower poly models, though I have seen them appear on V4 as well. (It didn't used to)

[face_off]

Basically, I'm getting shadow artifacts all over the models. Sometimes they seem to follow polygon lines, and sometimes they don't. (I think that depends on what the smoothing is set to, but they appear regardless of whether smoothing is on or off.) It tends to appear more on lower poly models, though I have seen them appear on V4 as well. (It didn't used to)

I suspect your default rendertarget settings have a "rayepsilon" that is too high. I suggest using 0.00001 for Poser figures. Pls see http://render.otoy.com/manuals/Poser/?page_id=210.

Also - on the dino image above, it looks like the normals are corrupted. Use the deep_channel_kernel (with Interpolated normals) to assess if this is the case. If you disable smoothing for the dino skin material, then the normals are ignored.

Paul