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

[face_off]

I have exported the scene to OctaneRender 1.26, but the problem was there 1:1 as in the plugin. But off and on the importance sampling according to a rotation helps to smooth the image.
But I think it should still work even without such actions.

I think this is an issue with Octane 1.25, and Otoy have most probably fixed it in 1.27. I have a 1.27 build of the plugin ready, however there is a small issue with the scale sliders introduced with 1.27, so I will wait for 1.28 before releasing the next version of the plugin.

So in summary, this will hopefully be resolved in the next release of the plugin (which will be 1.28).

Paul

[wimvdb]

I have several occasions where I had to reset the cuda device because the videocard did not respond.
This started happening with 1.25.17.

The first few renders work fine but when I then switch to another camera and start to render it stops shortly afterwards (around 50, 100 or 500 samples as far as I remember). Resetting the device and all renders fine. Memory usage, texture use are all nowhere the limit.

[face_off]

I have several occasions where I had to reset the cuda device because the videocard did not respond.
This started happening with 1.25.17.

Hi Wim

Is this with you old hardware, or new?
Are there any cuda errors in the log? (From the "cuda" button in the devices tab)?
It may have been something introduced with the 1.25 render engine, or perhaps somethings has changed with your hardware. It would be worth trying to underclock your video card a touch to see if that helps.

Paul

[wimvdb]

I have several occasions where I had to reset the cuda device because the videocard did not respond.
This started happening with 1.25.17.

Hi Wim

Is this with you old hardware, or new?
Are there any cuda errors in the log? (From the "cuda" button in the devices tab)?
It may have been something introduced with the 1.25 render engine, or perhaps somethings has changed with your hardware. It would be worth trying to underclock your video card a touch to see if that helps.

Paul

It is still with the old hardware. New hardware arrives this week
It has been working fine for the past year and I never overclocked it
When I checked the log it was empty - but not sure if I had done a reset. I wil check next time.
I am running GPU-Z now to see if anything strange is going on

Another weird thing.
It looks like in the scene I am loading, the wrong card settings are chosen. I have the GTX580 and the GTX680 in there. Only the 680 is actived for GPU for CUDA. When I load this scene I get the too many textures loaded message. But when I do a Image file statistics you can see that it takes the wrong limits: 64/32 which should be 144/68.
Now if I let it continue the viewport reports 144/68 again and render OK. So it looks like the plugin checks the wrong card for limits

[face_off]

It has been working fine for the past year and I never overclocked it
When I checked the log it was empty - but not sure if I had done a reset. I wil check next time.
I am running GPU-Z now to see if anything strange is going on

My best guess is that either a small hardware issue has arisen - or Octane 1.25 has issues. A 1.27 or later build may resolve it. I would try underclocking the card just in case...

It looks like in the scene I am loading, the wrong card settings are chosen. I have the GTX580 and the GTX680 in there. Only the 680 is actived for GPU for CUDA. When I load this scene I get the too many textures loaded message. But when I do a Image file statistics you can see that it takes the wrong limits: 64/32 which should be 144/68.
Now if I let it continue the viewport reports 144/68 again and render OK. So it looks like the plugin checks the wrong card for limits

I think the Image File Statistics is taking the texturemap limits from the Configuration (where you have a 500 or 600 series card) - changing the setting there may address your issue.

Paul

[wimvdb]

It has been working fine for the past year and I never overclocked it
When I checked the log it was empty - but not sure if I had done a reset. I wil check next time.
I am running GPU-Z now to see if anything strange is going on

My best guess is that either a small hardware issue has arisen - or Octane 1.25 has issues. A 1.27 or later build may resolve it. I would try underclocking the card just in case...

It looks like in the scene I am loading, the wrong card settings are chosen. I have the GTX580 and the GTX680 in there. Only the 680 is actived for GPU for CUDA. When I load this scene I get the too many textures loaded message. But when I do a Image file statistics you can see that it takes the wrong limits: 64/32 which should be 144/68.
Now if I let it continue the viewport reports 144/68 again and render OK. So it looks like the plugin checks the wrong card for limits

I think the Image File Statistics is taking the texturemap limits from the Configuration (where you have a 500 or 600 series card) - changing the setting there may address your issue.

Paul

Yes, that was i - I changed the poser temp location and it was reset to default
I had not changed it for a long time

[ch0pper]

I have a new feature request is at all possible Paul

I've enclosed the mockup of what I would like to see if possible which I'm sure is possible

imager [camera]

On the main settings

just by saturation

Is it possible to have a colour balance

To change our RBG values?

To the picture exactly as it does with saturation?

As it's a perfect way to get your picture right 100% of the time

In my view is of course

[face_off]

Chopper - is what you are after "whit balance"? And if so - would adding a white balance picker to the Viewport resolve your issue? That's the way it works on Standalone (so you can try it there to see if it addresses your requirement).

Paul

[ch0pper]

well that sort sorts 50 % of what looking for
can this be put into poser ? white balance picker to the Viewport ?

in the next build?

[face_off]

well that sort sorts 50 % of what looking for
can this be put into poser ? white balance picker to the Viewport ?

in the next build?

Probably. It is scheduled for mid-next week.

Paul