OctaneRender® for Poser beta WIN - build 1.16a [OBSOLETE]

[Iefke]

Weird problem in Poser2014 Pro:
Have Octane rendering in the viewport.
Change the material node type from a material with texture images in it from ex. glossy to diffuse
This crashes Poser with an error on wxmsw291u_core_vc_custom.dll (2 times in a row, then Poser closes)

This happens with both versions 1.14a and 1.16a
It does not happen when the material nodes are changed without the render window open.
It does not happen with materials with just RGB values.
It is independent from the scene, any object, even the simplest primitive, with a texture provokes the crash.
This does not happen wit Poser2012 Pro (on the same machine).

This looks like your Poser Pro 2014 python installation is corrupted. wxmsw291u_core_vc_custom.dll is a PoserPython file. I suggest re-installing Poser Pro 2014.

Paul

After further investigation i found that Poser 2012 has the same problem with the versions 1.14 and 1.16

However i could nail the problem down to the video driver for the onboard Intel HD Graphics 4000 chip.
Earlier i installed the latest version (9.18.10.3071) from Intel which apparently is the source of this problem. I now reverted back to the old driver version which came with the motherboard or Windows 8 (i forgot which of the two), and now everything (version 1.16a5 btw) runs smoothly!

This Intel 4000 doesn't seem to match well with Octane.
However the strange fact remains that version 1.13 with Poser 2012 gave no problems.
I guess it must be a OpenGL thing ...

Anyway, thanks for your support Paul!

Yvo

[face_off]

It seems to me, images from the LiveDB are stored in memory and only as long as you don't close Poser. I scanned all my hard drives completely, but couldn't find the requested images. no luck with selecting from within the plugin either.

Uwe - I have investigated this - and it's due to special characters being in your Poser Preferences path. When there are no special characters in a path/filename then the filename is treated the same in Windows, python and Octane. However when there is a special character in the director or filename, then python will store the path/filename in Unicode format, Octane expects UTF-8 format, and Windows needs ASCII. So I am in the process of rectifying this - it will be in the next version.

Paul

[face_off]

I have refreshed the installer at the top of this thread. Pls download and install if needed (based on the notes below).

1.16a6
- Fixed an issue which caused Poser to crash on Win 8 when changing node types
- Fixed an issue where LiveDB materials were not being saved if there were special characters in your Windows username
- Added a "Ratio" combobox to the Viewport so you can scale down the rendering image on the screen

Paul

[KleanZlate]

Is there any news on when a patch will be out that makes rendering PP2014's SubD in Octane possible?

[face_off]

Is there any news on when a patch will be out that makes rendering PP2014's SubD in Octane possible?

At a guess, I would say this change would need to be done in conjunction with making the softbody deformations available to PoserPython. So it's probably quite a big change. Also, when it /is/ done, if you subd a mesh, it will take substantially longer to load into Octane (since there will be 4 times as making vertices and polygons for each level of subdivision). It will be roughly the same load times as Genesis (each subd 1 and 2). I will probably stop the plugin from rendering anything higher than subd 2, since it will be millions of polygons.

Pauil

[KleanZlate]

Is there any news on when a patch will be out that makes rendering PP2014's SubD in Octane possible?

At a guess, I would say this change would need to be done in conjunction with making the softbody deformations available to PoserPython. So it's probably quite a big change. Also, when it /is/ done, if you subd a mesh, it will take substantially longer to load into Octane (since there will be 4 times as making vertices and polygons for each level of subdivision). It will be roughly the same load times as Genesis (each subd 1 and 2). I will probably stop the plugin from rendering anything higher than subd 2, since it will be millions of polygons.

Pauil

Ok. Thanks for the updates!

[face_off]

That would be great. But the installer does overwrite a custom made OctaneDefaults.py

Zay - I have tested this on the lastest version of the installer (1.16a6) and it did not overwrite my OctaneDefaults.py file. So I /think/ this issue is fixed.

Paul

[Zay]

Zay - I have tested this on the lastest version of the installer (1.16a6) and it did not overwrite my OctaneDefaults.py file. So I /think/ this issue is fixed.

Paul

Yes, that seems to be fixed now. Also had a play with instancing. No errors so far. Great!

[Robynsveil]

I don't recall whether this has been discussed or addressed , but if -- with the plugin up and preview window active -- I select a camera (say: the posing camera) that is not parented to the Universe, I get an error message that i can't render from that camera. Fair enough... however, I don't intend to render from it, just pose my figure. Then, the Python dialogue box comes up with a bunch of traceback info. The message is a good one to have pop up, once... but it seems that perhaps you might want to include some error trapping code to manage what happens subsequently, maybe?
Just an idea... overall, an AMAZING and very, very addictive add-on to Poser, Paul! I am thoroughly impressed and rapt with it!

[face_off]

I get an error message that i can't render from that camera. Fair enough... however, I don't intend to render from it, just pose my figure. Then, the Python dialogue box comes up with a bunch of traceback info. The message is a good one to have pop up, once... but it seems that perhaps you might want to include some error trapping code to manage what happens subsequently, maybe?

I will fix the python exceptions. It's a good point about just needed to pose from the camera but not render from it. Let me see what can be done.

Paul