Maxwell Render

Hi Jeremy,

excuse this rather raw info , but i can't really tell you more:

i see objects occasionally loose their material.
it is not something completely new (i reported some time ago), but it just happened again a few times right now.
i have no idea why it happens!!

i only found out when sending jobs to the network:

the viewport texture still displays right, but for rendering it will want a "proxy" texture from local path.
now a texture from C:\ will crash network (i don't send dependencies)

i always check these paths in the wizard now so i found the bad guys.

the really strange thing is:

- maxwell properties in properties don't show any mat assigned.

- material properties in properties will show as usual : plugin activated and maxwell material with correct name "seems assigned"

this is all on rhino5.


any ideas are appreciated, it is giving me a tough time finding these objects as i can only invers-select unassigned materials,
which takes 15min+ with the hundereds of materials i have comming in from blocks/scenery.

**

Another weirdness i encountered is that assigning materials started to take very very long in this particular scene.

sometimes up to 20 sec. for just a single object.
this is when i assign via right click-assign to sel.objects. or if i execute command via CL. (maxwell_assign...)

it does not slow down when i go via the rhino properties-material-browse!

hope this info gives you some clue!

thanks,

Daniel

_________________
workstation: EVGA SR-2 / dual x5650@3.5Ghz / quadro 4000

little update..

maybe the problem is the process of material assignment itself?!
i just noticed that all of a sudden the material got assigned really quickly (via rightclick) so i double checked, and in deed the material did not get into the maxwell properties.

so maybe the objects in question never got the material, which i thought they lost.

however, textures are displaying as expected.. at least initially.

i am on a deadline right now, and can't spend time to reproduce a new scene.
i'll try later.

daniel

_________________
workstation: EVGA SR-2 / dual x5650@3.5Ghz / quadro 4000

That is strange, but I don't know what to tell you. I need a set of steps by which to reproduce, so that I can analyze what is happening. And then, it might be that it would no longer happen on the next week's V5 beta. If you could reproduce in V4, we would be in business.

_________________
Next Limit Team

i know.. v5 buisness

next time i encounter an object i'll export it for you to take a look.

btw. i read somewhere in the rhino NG that the sdk is frozen now?

is that true for your environment , too?

_________________
workstation: EVGA SR-2 / dual x5650@3.5Ghz / quadro 4000

That means that I can write V5-specific code without the risk of that code being broken prior to V5 release, but it does not mean that Rhino V5 itself will not continue to have various bugs randomly flitting in and out of existence from week to week.

_________________
Next Limit Team

I would check this again with the current (5.1.2012.417, 4/17/2012) beta. I observed a problem this morning with layer-material assignments with the previous build (sorry, I don't know exactly which version it was), but cannot reproduce it anymore after updating to the current beta.

_________________
Next Limit Team

thanks for the hint!

i am ok for now and will test when i am done with my current session.

compered to the ibl-caustics-(merging) problem that hit me too now, the material bug was quite an easy one

_________________
workstation: EVGA SR-2 / dual x5650@3.5Ghz / quadro 4000