Bug? - ORIB frame preview & animation playback not working

[linvanchene]

While doing a quick animation test of a x translated plane texture

I noticed that after all frames of the animation had finished rendering

- the preview frames in the OctaneRender Image browser (ORIB) all showed a red X with the error message "File not found" when hovering over the frame

-> The preview thumbnail image of the rendered frame is not showing (anymore).

- the animation does not play back when clicking on the "play button" in the ORIB

- the selected frames number in the OcDS animation tab and the frames number in ORIB do not match

example: 10 frames rendered but 30 frames as thumbnail preview in ORIB with red x and message "File not found"

- nevertheless the 10 frames are showing up in the target save folder that was indicated in the OcDS animation tab

- - -

Attached test scene as .duf in .zip

Tested with
Daz Studio Pro BETA - version 4.9.1.30
OctaneRender_for_DazStudio_3_0_6_16_Win64
- - -

[face_off]

Yes, you are right. You can see the file prefix in the browser window is wrong. I will see if this can be fixed in the next release.

Paul

[linvanchene]

You can see the file prefix in the browser window is wrong.

It seems when saving / loading scenes prefix and first / last frame information is also altered after scene reload

Default values when starting new scene:

- default Prefix: frame_
- default first / last frame: 0 / 30

- - -

Test values changed before saving scene:

- Prefix changed to: mahagony animated_

- first / last frame: 1 / 13

- - -

Values after closing and restarting DS and scene load:

- Prefix changed to: SCENENAME_

- first / last frame: 0 / 30

- - -

-> The name of the prefix is automatically changed to the name of the loaded scene even when a custom name was set for the prefix.

-> first / last frame reset back to the default 0 / 30 values after scene load

- The error handling values of 15 seconds were also reset to 10 seconds.

- Other values like, constant time selected, file type etc. seemed to stick with the saved values after scene reload.

test texture movement v1006.zip

.duf version of test scene in .zip

(21.07 KiB) Downloaded 169 times

- - -

[face_off]

Thank you. The code in this area appears to be incomplete - so it's not obvious what the intent is - but you are right it is not functioning correctly whatever the intent. I will need to take a closer look in the next few days.

Paul

[linvanchene]

Thank you. The code in this area appears to be incomplete - so it's not obvious what the intent is - but you are right it is not functioning correctly whatever the intent. I will need to take a closer look in the next few days.

Paul

Thank you for looking into this.

In the meantime a partial workaround for the OctaneRender_for_DazStudio_3_0_6_17_Win64 PREVIEW posted here:

viewtopic.php?f=44&t=52846#p268795

- - -

The preview thumbnails do show up

IF the DAZ Studio Scene name and the OcDS Name Prefix match

- - -

[face_off]

I will post a new release in a few hours, which I hope will fully resolve this issue. Can you pls re-test with this new release and let me know if there are any remaining issues.

Thanks

Paul

[linvanchene]

I will post a new release in a few hours, which I hope will fully resolve this issue. Can you pls re-test with this new release and let me know if there are any remaining issues.

Thanks

Paul

The previous tests I did posted in this thread was with the PREVIEW version of OctaneRender_for_DazStudio_3_0_6_17_Win64.exe

viewtopic.php?f=44&t=52846#p268795

I retested with the RELEASE version of OctaneRender_for_DazStudio_3_0_6_17_Win64.exe posted in the release thread

viewtopic.php?f=44&t=51808#p258727

- - -


1) if the prefix and the scene name match -> preview images do now also not show up in the ORIB ( this workaround was still working in the 3_0_6_17 PREVIEW version)

2) if prefix and scene name do not match -> no preview images show up

3) if a special prefix name is indicated it does not seem to be saved and reverts to the scene name when loading the scene again

4) if a first / last frame number is indicated it does not seem to be saved and reverts to the default 0 / 30 when loading the scene again


- - -

Could it be that there was some kind of mix up with the versions since the preview and the release of 3_0_6_17 have the same installer name?

I double checked and made sure to save the RELEASE version into a separate folder called OctaneRender_for_DazStudio_3_0_6_17_Win64 RELEASE before installing.

- - -

[face_off]

Thanks. This was due to the .duf retaining the old jpg save format. I have fixed this in the next release (uploading now).

Paul

[linvanchene]

Thank you for the continuous work on rooting those smaller issues out.

Retested with OctaneRender for DAZ Studio 3.0.6.18 (64 bit)

1) if the prefix and the scene name match -> preview images do now also not show up in the ORIB ( this workaround was still working in the 3_0_6_17 PREVIEW version)

2) if prefix and scene name do not match -> no preview images show up

-> solved with 3.0.6.18 -> preview frame images now show up at end of rendering.

3) if a special prefix name is indicated it does not seem to be saved and reverts to the scene name when loading the scene again

4) if a first / last frame number is indicated it does not seem to be saved and reverts to the default 0 / 30 when loading the scene again

Those issues remain.

Maybe they can be addressed when the save / resume render functionality is introduced?
If that will be possible in the OcDS plugin?

[face_off]

3) if a special prefix name is indicated it does not seem to be saved and reverts to the scene name when loading the scene again

I could not reproduce this error.

4) if a first / last frame number is indicated it does not seem to be saved and reverts to the default 0 / 30 when loading the scene again

As far as I can tell from the code - that is the intended functionality. The first/last frame numbers do not appear to be saved in the .duf file - and are derived from the DAStudio timeline.

Maybe they can be addressed when the save / resume render functionality is introduced?
If that will be possible in the OcDS plugin?

I don't know. My best guess is that the partial render will be saved together with the source scene as an ORBX. So you could load the ORBX into Octane Standalone and continue rendering. Or perhaps there will be a new dialog window for plugins which list all the partial renders and you can load and continue them. But that's just a guess.

Paul