OTOY Forums

face_off wrote:

I managed to create it using the basic wear top.

Steps to recreate the issue.
1. Load G2F.
2. Select G2F.
3. Go to Shaping Tab.
4. Change Breasts Cleavage (Chest->Real World) to 1. This will help to show the issue more prominently.
5. Load the basic wear Top.
6. Open the Octane Viewport. Following screen should show. As you can see the top is kinda shrink wrapped around her breasts.

Hi Rajib, my preference would be to put this issue on hold until, since it seems low priority, and there are some more pressing issues I would like to address. I'll add it to the long-term list though.

Paul

Hi Paul,

Not an issue. This can be done later. I will be reporting few more issues that I have consistently faced but probably after I test with your next release (2.24.2.5). Even those can be added to the long-term list as I can work around them for now.

Best regards,
Rajib

Thanks for all your work face of, it's nice to see the forum lit up like christmas tree again

Have you looked into the "Render SubD level" setting in Paramers/Mesh Resolution? Currently OCDS ignores it, and just renders at the viewport subD. With figures like the new G3, which is supposed to be rendered at level 2 or 3, having that option would be nice, as subD'ing the figure in the viewport gets a bit heavy on performance at times.

New material conversion works really well

Have you looked into the "Render SubD level" setting in Paramers/Mesh Resolution? Currently OCDS ignores it, and just renders at the viewport subD. With figures like the new G3, which is supposed to be rendered at level 2 or 3, having that option would be nice, as subD'ing the figure in the viewport gets a bit heavy on performance at times.

In theory if you tick "Use Base Geometries", there could also be an Octane subd level slider in the Actor->Parameters->General->OctaneRender panel, however it is not a trivial change - so it will need to wait until the migration of the plugin to Octane 3 with done.

I also said that I would push through support for Render Layers prior to Octane 3, however it has been much more complex to implement than expected, so it too will need to wait.

Paul

I have refreshed the installer at the top of this thread with:

2.24.2.5
- Fixed Alembic Export dialog end frame number reporting the wrong frame
- Fixed issue where opening the Viewport on a scene with no geometry put the Viewport into an uncertain state
- Added preliminary support for Render Layers. Enable Render Layers in the "Rendersettings" tab, and assign individual render layer ID's to props/actors in the OctaneRender Parameters

I am hoping that this will be the last plugin release prior to the Octane 3 version. However if there are any important issues that need addressing with this release, pls let me know.

Thanks

Paul

face_off wrote:

Have you looked into the "Render SubD level" setting in Paramers/Mesh Resolution? Currently OCDS ignores it, and just renders at the viewport subD. With figures like the new G3, which is supposed to be rendered at level 2 or 3, having that option would be nice, as subD'ing the figure in the viewport gets a bit heavy on performance at times.

In theory if you tick "Use Base Geometries", there could also be an Octane subd level slider in the Actor->Parameters->General->OctaneRender panel, however it is not a trivial change - so it will need to wait until the migration of the plugin to Octane 3 with done.
Paul

Fair enough, on the user side it's hard to have an idea of what's just changing a few numbers around, and what's a huge rewrite

I'm a bit late to the party it seems. I didn't expect things to move so quickly. I need to hurry up and get some testing in tonight. Exciting times!

face_off wrote:I have refreshed the installer at the top of this thread with:

2.24.2.5
- Fixed Alembic Export dialog end frame number reporting the wrong frame
- Fixed issue where opening the Viewport on a scene with no geometry put the Viewport into an uncertain state
- Added preliminary support for Render Layers. Enable Render Layers in the "Rendersettings" tab, and assign individual render layer ID's to props/actors in the OctaneRender Parameters

I am hoping that this will be the last plugin release prior to the Octane 3 version. However if there are any important issues that need addressing with this release, pls let me know.

Thanks

Paul

Thank you for the new update, Paul!
My material preview is still not updating in real-time in the NGE, am I the only one having that problem or is it something that's still on the list of things to fix?

face_off wrote:I am hoping that this will be the last plugin release prior to the Octane 3 version. However if there are any important issues that need addressing with this release, pls let me know.

Paul,

Haven't had a chance to test the latest (and I'm at work ATM), so I'm not sure if this has been fixed at this point ...

In any case, if you could address this one, I'd be appreciative:

viewtopic.php?f=44&t=47686&p=254293#p254293

Thanks!

Haven't had a chance to test the latest (and I'm at work ATM), so I'm not sure if this has been fixed at this point ...

In any case, if you could address this one, I'd be appreciative:

viewtopic.php?f=44&t=47686&p=254293#p254293

I could not reproduce this issue on the latest release (2.24.2.5).

Paul

face_off wrote:

When saving a scene and loading it again

- the HDR environment preset that was active when saving the scene is not selected
- the texture used in the HDR environment preset is missing after manually reloading the preset

I can reproduce this on DAZStudio 4.9, but not 4.8. I am guessing it is related to the DAStudio 4.9 bug where the old scene is not being deleted when you load a new scene. Would someone with the private beta build of 4.9 (where this issue has been fixed) be able to test this pls?

Thanks

Paul

Retested with the latest public build:
Daz Studio Pro BETA - version 4.9.0.54! (Release Candidate)
and
OctaneRender for DAZ Studio 2.24.2.5 (64 bit)

- the HDR environment preset that was active when saving the scene is not selected

This seems to be solved with the latest build combination. The last used environment when the scene was saved now seems to be loaded.

BUT

- the texture used in the HDR environment preset is missing after manually reloading the preset

It seems in general images used in the RGB image slot of HDR environment presets are not saved.

-Issue 1a) : the image used in the HDR environment preset is missing when a scene with an HDR environment is loaded

- Issue 1b) :textures used in HDR environment presets that are saved to "My Presets" are also missing when loading



Workflow to replicate:

In the OcDS Environment tab
select default HDR environment preset
- change RGB color to RGB image
- in the texture load option browse to C:\Program Files\DAZ 3D\DAZStudio4 Public Build\shaders\iray\resources
- select DTHDR-RuinsB-500.hdr
- set Gamma to 1
- set Translation X to 0.5


- click on the "Copy" button
- enter name "Ruins v1003"
- set checkmark at "Save into "My Presets"" and accept
In DAZ Studio

- clear the scene by selecting /file/new

In the OcDS Environment tab
- load "Ruins v1003" from the "My Presets" section
The image is missing in the loaded preset.

Side Note:
I am not sure if it is intentional that one cannot edit any parameters of saved "My Presets" after loading them.
Maybe if "My Presets" would be editable directly after loading then the changed values would be automatically saved with the presets.
This may result in accidental changes to the values of the saved presets.

In order to edit "My Presets" again it seems one has to copy them and add a new name.
Then the values become editable again.