[jvanmetre]

JD-

I've noticed in a couple of instances where the material editor dialog box
freezes up after creating a new material...for example, when I create a new material and try to edit the BSDF layer, the layer is non-responsive...when I try to then close the material editor dialog box by checking the X in upper right corner...it's also non-responsive. To get it to close, I have to go to the main Maxwell menu and click on "material editor" for it to close...a bit strange.

Thanks

Jim

[JDHill]

Hi Jim,

I've also seen this two different times, but was not able to isolate it. If I've been paying attention, it seems to only have happened after I saved - let me know if that rings a bell. My best guess is that for some reason, Windows messages are not getting pumped correctly, though I do not yet know what it takes to get things into that state. The first time I thought something was locked up, so I shut it down. The second time, I tried to fiddle around with things, and some combination of show/hide by the menu/toolbar commands, along with switching materials seemed to get things moving again, though I am not sure exactly what sequence I may have performed.

Let me know if you can find any good pattern - I'd like to be able to duplicate it and figure out what's happening.

JD

[polynurb]

that happened to me as well, a few times.
Not too bad, I just selected a few different materials, and then back to the one I was editing, and I could switch between layers again.
I think one issue causing it is when a preview thumbnail is still being generated in the background... so maybe switching between materials only allowed the preview to finish.

[JDHill]

The multi-threaded preview thing may be a factor, though I don't think I was using that when I saw this. Doing modeless dialog boxes, while trying to post messages to them from other threads can get to be a little hairy. As far as I know, I'm doing that stuff in the way that you're supposed to, but there is definitely lots of room for error - I'm sure it doesn't help either that the main time we're trying to do that is when there is a cpu-intensive MXCL running in the background.

[polynurb]

- I'm sure it doesn't help either that the main time we're trying to do that is when there is a cpu-intensive MXCL running in the background.

you mean, making a preview while rendering in the background..
that doesn't work too well, unless i take away one core via taskmanager.

it is a bit brutal and i don't know if it is crash safe to take away and reassign cpu cores while rendering , i tend not to do it unless i have to; - but it never crahed or created errors till now.