[ricardo]

Hi JD,

I think it was 1.5.1 it's the latest I have prior to Ugrading to 1.6.X, what just happened.

Cheers!

Ricardo

[JDHill]

Hi Ricardo,

There are quite alot of changes (around 9 months worth) to the various plugin components when moving directly from 1.5.1 to 1.6.8, so it's not completely surprising to me. The installer is really not designed to jump past multiple releases at all (probably better to uninstall/reinstall in those cases), so I suppose it's not too bad, as long as the plugin still loaded easily by the regular Rhino plugin loading method.

Thanks for the heads-up though, I'm just glad Rhino has a manual loading system available - if the SW plugin fails install in any way (it's much more complicated too), there's absolutely no way to manually load it.

JD

[Micha]

Hi,

I have scene with HDRI environment. If I disable the HDRI maps, save the file and open it again later, the HDRI maps are enabled again.
Can somebody confirm this?

-Micha

[kami]

Not confirmed here. They stay like they were before.
Could you post the rest of the settings? (ie. channels linked, sun enabled, physical sky for disabled, ...)

greets,
kami

[JDHill]

Hi Micha,

I don't seem to see this problem here, are using plugin version 1.6.8.0?

JD

[Micha]

Ah, I use 1.6.1.0 and will update it.

Thanks,
Micha

[JDHill]

...there are lots of new tools in 1.6.8, so I'd recommend reading through the 1.6.6 and 1.6.8 release notes topics at the top of the forum.

[bjorn.syse]

Hi!

Good work with the plugin JD!

One of my students noticed one strange thing, when trying to use all those small little + and - buttons to change the difference values in the Material Editor. They seem to change the value, but when one moves to let's say another material-layer and then checks back - the value is unchanged.

Can you reproduce this?

- Björn

[JDHill]

Hi Björn

Hmm...no, I can't seem to make it do that - as soon as you click one of them, it changes the underlying data. Are you saying that you can repeat this yourself, or is it just on that student's machine? If you can do it to, can you please provide a very specific set of steps that would allow me to see the problem?

Thanks,

JD

[bjorn.syse]

Hi, no this happens for me too. But I never use those buttons so I haven't noticed it.

Try this:

1. Create a new material and open it in material editor.
2. Go to the BSDF layer, and press the - button for let's say the roughness value a few times. The values changes.
3. Go directly (right away) to the main Material/top/root/node.
4. Go back to the BSDF-layer. The value is unchanged?

Sometimes this works, sometimes it doesn't. I've found the problem to occur more often with the +- button that controls the tiling of textures. These I can't get to stick at all.

I'm running 1.6.8.

- Björn

[JDHill]

Thanks - unfortunately that particular sequence still doesn't fault for me. I'm wondering, what regional settings are you running, because that might make a difference. I did find one thing with your comment about texture-tiling adjustment by the +/- buttons: the update to the value wasn't causing the type of change that would be seen in the viewport, so I fixed that...it's possible it may also affect the behavior in your example, but I can't be sure since I haven't yet observed that specific issue.

JD

[bjorn.syse]

Regional, as in Windows? it's probably Swedish.

That probably sortet it then, cause the fault only occured in for example Roughness if I started out a brand new material, and efter lowering the value with the - button moved very quickly to another layer or the top node. If i waited for a second or two, the value did stick.

- Björn

[kami]

i can reproduce it here.
On roughness, only if you change the BSDF very quickly afterwards. But on the texture tiling, the value always jumps back, if the number field is never selected.

[polynurb]

Hello Jd,

it's not a real bug but a little inconvenient.. when i select an object with a mxm applied and then select an object without material, it appears that the focus gets stuck on the (empty) materialeditor, so that the commandline does not accept the keyboard anymore, and you have to click into the viewport to get it back.
I had troubles lately with my workflow (that windows "not possible" sound comming up a lot) as i use keyboard for most commands, and i believe i tracked it down to that focus problem.


thanks,

polynurb

[JDHill]

Hi polynurb,

While I'm pretty sure I have seen this happen before, I can't duplicate it right now. If you can make this happen at will, do you think you could provide any more details - I suppose, things like what kind of Material component (BSDF, Emitter, etc.) was selected in the Material Editor prior to selecting the no-Material object; whether the Material Editor was on your primary screen; whether the Material has a texture selected; whether or not the Rhino Object Properties page was set to show the Maxwell page; etc.

Also, if it is really bugging you, you could try disabling Plug-in Options > Auto-select Materials - that will obviously change the selection behavior, but does it also affect this focus issue?

Thanks,

JD