OTOY Forums

If I mousewheel scroll and change a setting in this way, the setting would have to have the focus first, right? In the present case, the render window had the focus. I clicked on the plugin window header to get it in front of the render window, then clicked imager, then clicked hotpixel_removal, then changed the setting by dragging the slider. I'm 99% certain I didn't touch the mousewheel.

I've had a render restart before when I changed exposure, and again, I'm pretty sure I didn't touch the mousewheel. Besides, shouldn't using the mousewheel be safe if imager has the focus? Or am I not understanding something correctly?

(I use the render progress setting religiously, btw, and I'm very grateful it exists.)

face_off wrote:

I've just had a render restart on me after 8 hours because I changed hotpixel_removal. I don't suppose that is the way nature intended it to be, lol. (Fortunately, I had a feeling in my gut and had saved the render before I touched anything.)

I am 99% certain that this is happening because you use the middle mousehwheel to scroll the tree, and if the tree does not have the focus, the mousewheel instead increments/decrements the currently selected tree item. I am thinking I may have to disable the mousewheel moving of sliders, since it makes it too easy to accidentally restart a render.

If doing an 8hr render - always use progressive save. That way you can use the neat right mouseclick function on the viewport to compare with the previous render too.

Paul

I agree the accidental restart of a render due to the scroll wheel happens a lot. But the scroll wheel is also quite useful for making small adjustments. The UI with the slider is simply not fast enough. Maybe a solution: If you have an accidental restart it is usually much later (most action with a slider results in a restart anyway). So if you would have a timeout on the scroll wheell of a few seconds. Wouldn't that prevent the accidental restarts?

I've had a render restart before when I changed exposure, and again, I'm pretty sure I didn't touch the mousewheel. Besides, shouldn't using the mousewheel be safe if imager has the focus? Or am I not understanding something correctly?

The plugin code is something like "If the changed tree item is imager or postproc, do not restart the render". So the only way it could restart is if another item was changed (a non-imager/postproc item). I've had Poser do some interesting things, like move a light, or change the animation frame number, without much warning - all of which will restart the render. So as you are doing, use Progressive Save, and use the Lock Changes button.

Maybe a solution: If you have an accidental restart it is usually much later (most action with a slider results in a restart anyway). So if you would have a timeout on the scroll wheell of a few seconds. Wouldn't that prevent the accidental restarts?

Wim, I'm not sure I exactly understand what you mean here. Do you what a timeout prior to having a mouse wheel move the slider, or after?

Paul

face_off wrote:

Maybe a solution: If you have an accidental restart it is usually much later (most action with a slider results in a restart anyway). So if you would have a timeout on the scroll wheell of a few seconds. Wouldn't that prevent the accidental restarts?

Wim, I'm not sure I exactly understand what you mean here. Do you what a timeout prior to having a mouse wheel move the slider, or after?

Paul

What I meant is that the scrollwheel is deactivated after a few seconds of not being used (when it is set to change the slider)

I've been having some odd problems with this version.

Sometimes when I start rendering, the viewport is black and nothing happens, no error message and no progress. Sometimes closing octane and opening it again works, usually I have to restart poser. It's always fine on the default startup scene, it's when I start loading different figures and moving things that it happens regardless of refreshing the scene.
I've also had problems with refreshing the scene when it is working, I.E. I'll change the body texture I'm using, refresh the scene and it will still render the previous texture I was using.

CorDox wrote:I've been having some odd problems with this version.

Sometimes when I start rendering, the viewport is black and nothing happens, no error message and no progress. Sometimes closing octane and opening it again works, usually I have to restart poser. It's always fine on the default startup scene, it's when I start loading different figures and moving things that it happens regardless of refreshing the scene.
I've also had problems with refreshing the scene when it is working, I.E. I'll change the body texture I'm using, refresh the scene and it will still render the previous texture I was using.

I'm having the exact same thing happening to me for a few versions now.Oddly enough, it didn't occur in this version yet.
It was never a biggie for me, so I never reported it back.
What always helped me was closing the viewport window, hitting the refresh button of the setup window, so that scene would be "updated" again and opening the viewport window afterwards again.

I've been having some odd problems with this version.

Sometimes when I start rendering, the viewport is black and nothing happens, no error message and no progress. Sometimes closing octane and opening it again works, usually I have to restart poser. It's always fine on the default startup scene, it's when I start loading different figures and moving things that it happens regardless of refreshing the scene.
I've also had problems with refreshing the scene when it is working, I.E. I'll change the body texture I'm using, refresh the scene and it will still render the previous texture I was using.

Have you tried re-importing the mesh group from the materials tab?

Erick wrote:

CorDox wrote:I've been having some odd problems with this version.

Sometimes when I start rendering, the viewport is black and nothing happens, no error message and no progress. Sometimes closing octane and opening it again works, usually I have to restart poser. It's always fine on the default startup scene, it's when I start loading different figures and moving things that it happens regardless of refreshing the scene.
I've also had problems with refreshing the scene when it is working, I.E. I'll change the body texture I'm using, refresh the scene and it will still render the previous texture I was using.

I'm having the exact same thing happening to me for a few versions now.Oddly enough, it didn't occur in this version yet.
It was never a biggie for me, so I never reported it back.
What always helped me was closing the viewport window, hitting the refresh button of the setup window, so that scene would be "updated" again and opening the viewport window afterwards again.

That works for me as well when the render shows its black screen

Esper8 wrote:Have you tried re-importing the mesh group from the materials tab?

Yes, that solves the texture updating for the most part.
Not the oddness with the black viewport and having to restart or do things in a specific order, in order to get to get it working again though. Wondering if it's going to impact animation since I planned to do one at some point. I think my previous version before this was 1.02s, didn't notice any problems then.

To clarify, just closing the viewport and doing a refresh doesn't always solve the black viewport, I sometimes have to close the setup window as well and restart it from the render menu, and in some cases that doesn't work and I have to restart Poser.

Not the oddness with the black viewport and having to restart or do things in a specific order, in order to get to get it working again though. Wondering if it's going to impact animation since I planned to do one at some point. I think my previous version before this was 1.02s, didn't notice any problems then.

To clarify, just closing the viewport and doing a refresh doesn't always solve the black viewport, I sometimes have to close the setup window as well and restart it from the render menu, and in some cases that doesn't work and I have to restart Poser.

What Nvidia driver version are you using? What are your hardware specs pls (it's worth putting them in your signature on this forum).

Paul