OTOY Forums

Hi

Resizing textures via Textures tab freezes DS.

1. Started with an empty scene
2. Loaded a cube primitive
3. Applied a LiveDB material containing a diffuse map
4. Clicked to resize a diffuse texture to 1/2 (or any really).
5. DAZ freezes. Waited up to 5 min., nothing happens. Tried several different textures from LiveDB, always freezes.

BTW thanks for the update, it's been long anticipated Hope bug fixing doesn't take as long with this version as with the beta.

Jazbee wrote:Hi
Resizing textures via Textures tab freezes DS.

confirmed. overseen some debug thread locking code - 'am currently uploading the installer again; rather a hotfix so no new build nbr; just re-download in about an hour and it'll work...

Great, thanks!

Another small thing to report... I don't know if it's a bug really.

I have both Main Octane Pane and Nodegraph Editor docked as separate tabs, so that when I load a material I switch the tab instead of clicking "Nodegraph Editor" button in the main tab. Doing that materials don't update in NGE. Since I've always worked this way, at first I though there way something very wrong going on. I had to click "Nodegraph Editor" button in Materials tab and then everything worked fine. As I said, don't know if it qualifies as a bug, but this didn't happen in the older version.

Jazbee wrote:Great, thanks!

Another small thing to report... I don't know if it's a bug really.

I have both Main Octane Pane and Nodegraph Editor docked as separate tabs, so that when I load a material I switch the tab instead of clicking "Nodegraph Editor" button in the main tab. Doing that materials don't update in NGE. Since I've always worked this way, at first I though there way something very wrong going on. I had to click "Nodegraph Editor" button in Materials tab and then everything worked fine. As I said, don't know if it qualifies as a bug, but this didn't happen in the older version.

there are 5 ways to get an oc mat shown in the nge:
- double click either the oc mat itself in the left hand tree,
- or one of the linked daz surfaces in the right hand tree,
- press ENTER (= not numpad return), when i.e. cycling through oc mats using the cursor keys,
- using the nge picker tool in the viewport,
- apparently the open nge button.

might be possible that in the old version it did update to the currently mat-tab selected mat every time it went form hidden to shown; 'am going to test if this would still work since it sounds quite useful...

Ok, I've got another one

Octane Viewport freezes when you start it with a mesh without an assigned material.

1. Start new scene
2. Create a primitive (new material is not created automatically for primitives as it used to, maybe it's meant to be that way)
3. Open viewport. It's stuck in one position even if you create a new material for the primitive

*IF you create the missing material before opening the viewport, it works fine.

4. To unlock the viewport you need to create a new camera in DS. Adding a camera before opening the viewport doesn't produce this bug either.

Jazbee wrote:Ok, I've got another one
Octane Viewport freezes when you start it with a mesh without an assigned material.

1. Start new scene
2. Create a primitive (new material is not created automatically for primitives as it used to, maybe it's meant to be that way)
3. Open viewport. It's stuck in one position even if you create a new material for the primitive

*IF you create the missing material before opening the viewport, it works fine.

4. To unlock the viewport you need to create a new camera in DS. Adding a camera before opening the viewport doesn't produce this bug either.

ok, so this is for the todo list; had you cleared out a scene using ctrl-n/new or did this happen directly after starting ds?

In happens in both cases

Jazbee wrote:Ok, I've got another one

Octane Viewport freezes when you start it with a mesh without an assigned material.

1. Start new scene
2. Create a primitive (new material is not created automatically for primitives as it used to, maybe it's meant to be that way)
3. Open viewport. It's stuck in one position even if you create a new material for the primitive

*IF you create the missing material before opening the viewport, it works fine.

4. To unlock the viewport you need to create a new camera in DS. Adding a camera before opening the viewport doesn't produce this bug either.

Followed your steps to the "T" but unable to reproduce the issue. Before you jump on me like the last dude did, what hardware are you using.
I'm guessing that since I have 2 Video cards with the 3G card set as my primary render card and the 2G card set as display card, I'm not getting some of the weird video issues people are mentioning.

Tugpsx wrote:Followed your steps to the "T" but unable to reproduce the issue. Before you jump on me like the last dude did, what hardware are you using.
I'm guessing that since I have 2 Video cards with the 3G card set as my primary render card and the 2G card set as display card, I'm not getting some of the weird video issues people are mentioning.

i could reproduce it in 1 of 3 tries, only after having cleared the scene, created and deleted a camera, then adding primitive (no mat), but wasn't able to get the vp stuck (what apparently means it isn't connected to a camera).

btw i still have some multithreading in places where i most probably 'am going to dump it at some point - when particular problems persist; esp. since neither daz (completely not) nor octane (partly) are thread safe, it will be the only measure. it's not a big drawback, the overall time it needs to do things like scene updates is not to grow much, just the interface is going to stuck when i.e. large mat sets are converted. unfortunately there is no memory access to loaded daz maps, so even with the new octane api, which allows to write maps directly in-memory, the plugin still needs to load every map that a scene uses a 2nd time from disk...

i could reproduce it in 1 of 3 tries, only after having cleared the scene, created and deleted a camera, then adding primitive (no mat), but wasn't able to get the vp stuck (what apparently means it isn't connected to a camera).

Ah, you are correct, doing it this way does produce the issue.