Twilight Render User Forum

Having an issue with the Deep Editor. If I try and convert a material to deep editor using the "tools" button in material editor window SU freezes. Nothing responds and the only way out is to force quit SU. I can access the Deep Editor if I go through the extensions menu in the SU toolbar. The Deep Editor window will open , I can select the material and convert it. This has me puzzled....
This behavior only occurs on my MacBook Pro , OS is Yosemite 10.10.5 . I don't have this problem on my iMac running Mavericks.

I'm using TW v2 pro and have the most recent version loaded. Any advice would be helpful. I've attached a screenshot with notations to hopefully make things clear.

Does it happen no matter what the material is?

Chris, Did some experimenting over lunch. Think I can supply a little more detailed information now.

First discovery , I only get the freeze up when working on my auxiliary monitor . It freezes up on the monitor at the apartment and at work.
If I turn off the monitor and work on the laptop screen instead of freezing up SU just crashes. On the laptop screen if I click on "convert to deep" in the material editor window, I get the dialogue box "do you want to convert material" , click yes and the deep material window opens and within seconds SU will crash.

Native SU materials without an added imported bump map or specular map convert to deep editor o.k.. Native SU material that gets a bump map from TW auto template folder crash. If I import a bump map to use with a native SU material it crashes. Example would be importing a noise map to use with a wall color.

Tried a bunch of texture images , bump maps and specular maps from different sources , they all crashed when trying to convert to deep. Tried different combinations, texture only, texture and bump etc. everything I tried was crashing. Seems to be associated with having an imported imaged loaded into the material editor ? Will do some more experiments tonight and post any new findings.

Bye the way, I'm working in SU 2015 Pro

Huh, that's interesting. Good investigating.

Given a material in the same situation, a standard SU material with template with a bump map, does it crash when you do the conversion inside the deep editor, or only from the template editor?

Chris, Posting another screen shot. Here's the steps I did, cube was painted with an SU "crayon color", opened TW material template window, selected "carpet" template , loaded a carpet bump map , I think the map was downloaded from this site. Clicked on "tools" in material edit window, then clicked "convert to deep". Yes - No dialog box opens , clicked "yes". Deep Edit window opened but before I can do anything SU crashes.....

Ok. What if you do that same thing (apply the template, apply the bump map) but do the conversion in the Deep Editor instead of the Template Editor?

Chris, Another screenshot. I applied the material template and bump map in the material template window. Opened deep editor by going through extensions > twilight render v2 > deep material editor . Converted to deep and loaded they specular map no problem. Ran a quick render, everything works fine. After converting to deep by going through the extensions path I have no problem opening deep editor in material edit window by selecting the material than clicking the open deep editor button there . The extensions path has been my work around.
I haven't tried converting a second material after having converted one . I'll give it a try a little later and let you know what happens.

Chris , Spent some time with this last night. Tried multiple objects in the same model with a various mix of textures , native SU textures , Su textures with added bump maps , imported textures etc. Everything would crash SU if tried to convert to Deep Editor in the Material Template window. Converting using the path , SU > Extensions > Twilight Render V2 > Deep Editor worked every time. After making the conversions this way I could successfully call back the deep edit window by selecting the material in Material Template window and clicking the Open Deep Edit button.

Ok. Great work! We will take a look at that use case and hopefully we will be able to find what's going on. OSX has some strange behavior on occasion but since this is pretty consistent hopefully we can find the problem.

Thanks!

Chris, Thanks and good luck.