OTOY Forums

You can set the limit in OctaneDefaults.py (in Program Files/SmithMicro/Poser Pro 2014/Runtime/Python/addons/OctaneRender for Poser)
It is default set at 4M polygons. You can make it a lot larger if you have enough CPU memory. I have set it at 25 million and can load anything now. That includes Forest Superior with a number of figures

Change at line 17 MAX_NUMBER_OF_SCENE_POLYGONS = 4000000 to a higher number

Oh cool . But, so how do I know what value to set. I have 16gig Ram on win7 professional System.
So, found it. With 16gig of RAM, I can go up to 16 000 000 Polygons, right?

Oh cool . But, so how do I know what value to set. I have 16gig Ram on win7 professional System.
So, found it. With 16gig of RAM, I can go up to 16 000 000 Polygons, right?

You can set the max polygons to anything up to 19 million with the current version of Octane.

Paul

I am having issues with Octane subdivs, where the UVs get scrambled after I refresh the scene. I also noticed Poser figures get visible seams between body parts after subdivided in Octane, like it wasn't welded together. In most cases this becomes more visible when I use body scaling or more extreme morphs, for the seams create holes on the models. Sometimes it's not open holes, but surface normal discontinuities at the seam between body parts, like it's not welded.

Is it just me?

I am having issues with Octane subdivs, where the UVs get scrambled after I refresh the scene. I also noticed Poser figures get visible seams between body parts after subdivided in Octane, like it wasn't welded together. In most cases this becomes more visible when I use body scaling or more extreme morphs, for the seams create holes on the models. Sometimes it's not open holes, but surface normal discontinuities at the seam between body parts, like it's not welded.

Which version of the plugin are you using pls?

face_off wrote:Which version of the plugin are you using pls?

I was using 2.21.0.40, and today I have just updated to 2.21.1.41 (current). Was that something specific to a version?

I was using 2.21.0.40, and today I have just updated to 2.21.1.41 (current). Was that something specific to a version?

There was an Octane subd problem in Octane API 2.21.0, which was fixed with 2.21.1. Has 2.21.1.41 fixed the problem for you?

Paul

face_off wrote:There was an Octane subd problem in Octane API 2.21.0, which was fixed with 2.21.1. Has 2.21.1.41 fixed the problem for you?
Paul

I don't know, I've stopped using Octane subdivs since I knew it would cause trouble. Today I have subdivided an outfit and nothing blew up, so I guess it's a good sign.

What about the visible seams and holes between figure body parts? That was without subdivs. I have stopped using body scaling or more extreme morphs/poses because I know that would ruin my renders. Has that been reported before?

Ken1171 wrote:

face_off wrote:There was an Octane subd problem in Octane API 2.21.0, which was fixed with 2.21.1. Has 2.21.1.41 fixed the problem for you?
Paul

I don't know, I've stopped using Octane subdivs since I knew it would cause trouble. Today I have subdivided an outfit and nothing blew up, so I guess it's a good sign.

What about the visible seams and holes between figure body parts? That was without subdivs. I have stopped using body scaling or more extreme morphs/poses because I know that would ruin my renders. Has that been reported before?

If you use Octane smoothing (plugin setup screen, smoothing angle set to non-zero) there is sometimes a seam problem, could very well have to do with scaling the figure. Usually setting the figure to unimesh fixes that problem. You can also go back to Poser smoothing where that problem does not occur.

What about the visible seams and holes between figure body parts? That was without subdivs. I have stopped using body scaling or more extreme morphs/poses because I know that would ruin my renders. Has that been reported before?

If you are getting this on the latest version, can you pls either post some screen shots, or even better, send me a scene showing the problem.

Thanks

Paul