OctaneRender for DAZ Studio 3.02 [OBSOLETE]

[Hydra]

I still can't click '...' in the NGE;

I get an error "DAZStudio.exe caused GUARD_PAGE in module "C:\Program Files\DAZ 3D\DAZStudio4\MSVCR100.dll" at 0033:0000000064A4C24D, memmove()+749 byte(s)", then Daz crashes.

I briefly see a blank menu.

[face_off]

I get an error "DAZStudio.exe caused GUARD_PAGE in module "C:\Program Files\DAZ 3D\DAZStudio4\MSVCR100.dll" at 0033:0000000064A4C24D, memmove()+749 byte(s)", then Daz crashes.

Can you pls let me know if any of these work for you:

1) Rename C:\Users\[username]\OctaneRender\Data\OctaneRender_settings.oczdb to C:\Users\[username]\OctaneRender\Data\OctaneRender_settings.oczdb_old
2) Rename C:\Users\[username]\OctaneRender\Cache to C:\Users\[username]\OctaneRender\Cache_old
3) DAZStudio->Edit->Preferences->Restore Factory Defaults

Paul

[Spectralis]

I'm having a problem with 3.0.20.22 on a scene that worked fine in 3.0.20.20. In the latest build when I render a still the viewport correctly renders to 16:9 (1.788:1) but when I try to render animation the viewport defaults to 1:1 size. So all the rendered animated frames are the incorrect size. Camera, environment and render setting in the animation render pane are all set correctly.

[face_off]

I'm having a problem with 3.0.20.22 on a scene that worked fine in 3.0.20.20. In the latest build when I render a still the viewport correctly renders to 16:9 (1.788:1) but when I try to render animation the viewport defaults to 1:1 size. So all the rendered animated frames are the incorrect size. Camera, environment and render setting in the animation render pane are all set correctly.

This is fixed in the next release.

Paul

[Spectralis]

Ok, that's good to know. I first thought that it might be a problem with the scene.

In the meantime is there any way to go back to the 3.0.20.20 version? It had expired which was why I installed the latest release.

[Hydra]

Paul, none of those things worked. It still crashes.

[face_off]

Paul, none of those things worked. It still crashes.

I have added some additional error check in the next release, which will hopefully either resolve, or help identify the problem.

Paul

[Spectralis]

I'm having a problem with UV transform and Octane materials in the latest plugin release.

TEST: load plane, load Octane parquet material, UV transform is set to non-specific but is really 3D not 2D. Need to change UV transform to 2D in NGE. I think there's a problem when loading materials with the UV transform setting in the .22 release. I've written more about it here:

viewtopic.php?f=44&t=54489

[Spectralis]

Instancing doesn't seem to work correctly in this build either. I load a desk, chair, computer and an office cubicle. The desk, chair and computer are parented to the cubicle. I then create nine instances and arrange them in an office space. The cubicles and all parented objects appear in the plugin viewport but are not positioned correctly. No matter how I try to move the cubicles they do not correspond to their position in the DAZ viewport. A forced reload doesn't correct this problem.

I'm not sure why the plugin viewport isn't updating the instances position but it should correspond to the DAZ viewport.

[face_off]

Instancing doesn't seem to work correctly in this build either. I load a desk, chair, computer and an office cubicle. The desk, chair and computer are parented to the cubicle. I then create nine instances and arrange them in an office space. The cubicles and all parented objects appear in the plugin viewport but are not positioned correctly. No matter how I try to move the cubicles they do not correspond to their position in the DAZ viewport. A forced reload doesn't correct this problem.

I'm not sure why the plugin viewport isn't updating the instances position but it should correspond to the DAZ viewport.

The has been reported previously, and it appears that instancing has never worked, and is listed as "Unsupported" in the manual (https://docs.otoy.com/?manual=manuals/p ... imitations). I have looked at it, but there is no simple solution, so it's still on the list of things to fix.