OctaneRender 2023 for Poser [OBSOLETE]

[spartan00j]

Yeah I understand that. But I have plenty of space on my drive. And the destination never changed. I had to close the plug in and reopen it. So it can function properly again.

The

Code: Select all

Saved images from an animation are now saved with a filename in the format "[Poser scene filename]_[frame number].png/exr

FR implemented in the latest release could be causing this. If this happens again, can you check the Octane Log to see if there are any errors reported there please.

Paul

Hi Paul, I open up the plug in and got a blank screen. Had to close poser completely and reopened to fix it.
This is the error code.

Code: Select all

Enabled with code: K3 M1
failed to save image
failed to save image

[face_off]

Before I go into this - can you make sure you are on Nvidia driver 552.22 Studio and re-test the above?

Thanks

Paul

[spartan00j]

Before I go into this - can you make sure you are on Nvidia driver 552.22 Studio and re-test the above?

Thanks

Paul

Hey Paul, it sort of hard to retest since it happens random. But I was on a earlier version of the driver. And also it was the consumer version not the studio. But I sense update my driver. And I randomly got the same issue again. With a different code.

Code: Select all

Started logging on 19.07.24 20:15:16

OctaneRender Studio+ 2024.1 Beta 2 (14000007)

device 0: failed to bind device to thread, since it's already bound
device 0: failed to initialize context
device 0: failed to initialize render thread 0000000075D54950
device 0: failed to bind device to thread, since it's already bound
device 0: failed to initialize context
device 0: failed to initialize render thread 0000000020DBBDE0
device 0: failed to bind device to thread, since it's already bound
device 0: failed to initialize context
device 0: failed to initialize render thread 00000000B2B52650

[face_off]

Before I go into this - can you make sure you are on Nvidia driver 552.22 Studio and re-test the above?

Thanks

Paul

Hey Paul, it sort of hard to retest since it happens random. But I was on a earlier version of the driver. And also it was the consumer version not the studio. But I sense update my driver. And I randomly got the same issue again. With a different code.

Code: Select all

Started logging on 19.07.24 20:15:16

OctaneRender Studio+ 2024.1 Beta 2 (14000007)

device 0: failed to bind device to thread, since it's already bound
device 0: failed to initialize context
device 0: failed to initialize render thread 0000000075D54950
device 0: failed to bind device to thread, since it's already bound
device 0: failed to initialize context
device 0: failed to initialize render thread 0000000020DBBDE0
device 0: failed to bind device to thread, since it's already bound
device 0: failed to initialize context
device 0: failed to initialize render thread 00000000B2B52650

Can you please confirm exactly which Nvidia driver version you have installed, and if it is Game or Studio?

Thanks

Paul

[spartan00j]

Before I go into this - can you make sure you are on Nvidia driver 552.22 Studio and re-test the above?

Thanks

Paul

Hey Paul, it sort of hard to retest since it happens random. But I was on a earlier version of the driver. And also it was the consumer version not the studio. But I sense update my driver. And I randomly got the same issue again. With a different code.

Code: Select all

Started logging on 19.07.24 20:15:16

OctaneRender Studio+ 2024.1 Beta 2 (14000007)

device 0: failed to bind device to thread, since it's already bound
device 0: failed to initialize context
device 0: failed to initialize render thread 0000000075D54950
device 0: failed to bind device to thread, since it's already bound
device 0: failed to initialize context
device 0: failed to initialize render thread 0000000020DBBDE0
device 0: failed to bind device to thread, since it's already bound
device 0: failed to initialize context
device 0: failed to initialize render thread 00000000B2B52650

Can you please confirm exactly which Nvidia driver version you have installed, and if it is Game or Studio?

Thanks

Paul

I have 560.70 Studio installed

[face_off]

Can you test with the driver I specified above please?

Thanks

Paul

[spartan00j]

Can you test with the driver I specified above please?

Thanks

Paul

Hi Paul, it was a headache but I finally got the driver installed. There's an issue with that version of driver having multiple monitors connected while installing it gave me a black screen and I couldn't install until I disconnected the display ports and just left one HDMI connected. Weird!
But I got the same results with the driver version you specified. Here's the log.

Code: Select all

Started logging on 20.07.24 10:59:27

OctaneRender Studio+ 2024.1 Beta 2 (14000007)

Image loading: PNG: FreeImage_SaveU: failed to open output file
failed to save image
Image loading: PNG: FreeImage_SaveU: failed to open output file
failed to save image
Image loading: PNG: FreeImage_SaveU: failed to open output file
failed to save image

[face_off]

Thanks. What is the scene filename of your Poser .pz3 file? And what is the Save Format in the Animation tab. And does the Output Folder in the Animation tab exist please?

Paul

[spartan00j]

Thanks. What is the scene filename of your Poser .pz3 file? And what is the Save Format in the Animation tab. And does the Output Folder in the Animation tab exist please?

Paul

scene filename: Bone remodeling - OsStic Part 5-2.pz3
Save Format: G:\PBC-3633-OsStic Animation\02. Editing Folder\Footage-Frames\7-15-24\OsStic Part 5-2
And yes the output folder exists.
But I get this even when I'm not rendering to image files sometimes. It's random. It happened again this morning. Here's the error code. I'm not rendering to an image just trying to view the scene.

Code: Select all

Started logging on 26.07.24 02:25:12

OctaneRender Studio+ 2024.1 Beta 2 (14000007)

Enabled with code: K3 M1
failed to save image
failed to save image
failed to save image
failed to save image

[face_off]

scene filename: Bone remodeling - OsStic Part 5-2.pz3
Save Format: G:\PBC-3633-OsStic Animation\02. Editing Folder\Footage-Frames\7-15-24\OsStic Part 5-2
And yes the output folder exists.
But I get this even when I'm not rendering to image files sometimes. It's random. It happened again this morning. Here's the error code. I'm not rendering to an image just trying to view the scene.

Do you have Progressive Save enabled?

Paul