Slow Material Editor

[grasshopper]

Hi all hope someone can help,

I got a problem with viewing the material editor in Max2009 Vray Sp2.

When ever I select Vray as render it's fine but if I select Vray for the material editor the material editor takes about 10-15 seconds to load each material slot. I found this thread on cgarchitect site http://www.cgarchitect.com/vb/30620-...2009-64-a.html which at least means i'm not alone.

Unfortunately I have tried the things people suggested like unplugging my network and checking for unobtainalble map paths but nothing worked.

If scanline or mental ray are selected everything seems to work fine so I'm all out of ideas. Is anyone else experiencing this or better yet has anyone a solution. I'm all ears.
I am having to revert to using (dare I say it) mental ray which sucks, so please help if you can.

Max2009, VraySp2
Vista Buisness 32bit
Intel Core 2 Quad 6600 @2.4GHz
4GB RAM
GeForce 8800GTX


Thanks Greg

[STUDIO_12]

The material editor is slow if work with OpenGL but is faster working in direct3d.
or if the materials are not Vray also going slower.

[vlado]

Does this happen on any scene, even an empty one, with a simple VRayMtl or Standard materials in the material editor?

Does this happen with the demo version of V-Ray as well?

Otherwise I'll have to check if I can reproduce this here as well, but I don't seem to remember an issue like that...

Best regards,
Vlado

[grasshopper]

Yes it happens on all scenes. Even empty scenes. As soon as Vray is selected as the material renderer no matter what type of material is present. Not tried the demo. I'll give it a try later on tonight.

It is acting like it is looking for network paths but don't see how why it would be

[vlado]

Ok; do you also get a lag when opening the Render Scene dialog?

Please try the demo version and let me know how that goes.

Best regards,
Vlado

[grasshopper]

Yes I get a slight lag maybe a second or two when opening the reder scene dialog.

I tried the demo and it seems fine no lag for render dialog or material editor

[vlado]

Ok, in that case can you email me to vlado@chaosgroup.com and we'll try to solve this.

Best regards,
Vlado

[bKittsARC]

Vlado, has this issue been resovled? I'm also running 2009 (64bit) and it takes about 45 seconds to open the material editor in a new scene if you have it set to load with vray materials.

Basically the preview of any vray material takes about 5 seconds each, makes it horribly slow when navigating multi-sub objects.

[vandy]

Same thing

My computer did the same thing this morning. It took almost 30 seconds everytime with the material editor. I also noticed that my internet explorer also took a long time when typing things in. Really wierd, but a little while later it fixed itself; I didn't do anything but keep working and swearing at the computer. Maybe it wasn't a max problem?
Good luck,

Vandy

[bKittsARC]

no, I don't think this is something that will just "work itself out".... I've been putting up with this for a month now. I thought it was a max problem until I realized if I leave the material editor set to scanline that the material editor works fine.

[vlado]

Vlado, has this issue been resovled? I'm also running 2009 (64bit) and it takes about 45 seconds to open the material editor in a new scene if you have it set to load with vray materials.

Basically the preview of any vray material takes about 5 seconds each, makes it horribly slow when navigating multi-sub objects.

The slowdown is caused by V-Ray trying to connect to the license server for each swatch (you can verify this if you also start a rendering process - it should take the same amount of time for the rendering to begin). In some cases, it was because the user had typed a different license server machine as the primary license server; in other cases it might be because something slows down the network connection. What exactly is causing I don't know (but it does not look like it is specific to V-Ray). For SP3 we will probably rethink how this is organized so that this wait is reduced to a minimum.

Best regards,
Vlado

[paulison]

I use Archicad which has a WIBU key dongle and If i connect to the licence server through VPN at the office it can be really slow depending on whats going on with the network. If i happen to be copying some files or doing a backup then i can get similar delays and constant pauses in Archicad while its looking for the licence. Maybe its a similar thing?

Since I've had both dongles (Vray and Archicad) plugged into my workstation i havnt had any issues...except for when textures are being loaded from the server at the office (then it gets REALLY slow, but its not a vray problem)

Is it possible that in the licence settings in vray you are specifying the name of the computer with the Dongle and there are some kind of DNS problems? I always use the IP of the machine to reduce the chances of this because when i am VPN'd to the office it is actually getting the DNS info from another office from there so I frequently get network slowdowns especially when it comes to anything relating to refreshing network shares or DNS related issues. Maybe that doesnt help but just thought i'd share my experiences on this subject.

[digitarch]

same thing

we stopped using vray materials since this terrible mateditor-slowdown. even with empty scenes, no objects, no shaders, its about 4 seconds waiting on each material editor slot to render. switching material editor renderer to scanliner solves the speed-problem but of course stops the advantages of the renderer.

using up-to-date workstations with gigabit network, max2009 vray 150sp2, scanliner and mental works fine, also other software using network-dongles are fast.

are there any updates on the wibu-software or optimizing tips installing the dongles as services/clients, using ip-adresses or server-name...?

[sea2stars]

It's odd. I had this issue when I brought my dongle home from work, but when I finally setup Hamachi to access the dongle at work from home the material editor worked normally.

[digitarch]

i hope its some kind of trick with the wibu-key settings, to me it looks like odd timeout-problems or adressinf/resolving ip-adresses.... there seam to be very few users around here having this problem, maybe they all keep the dongle in the safe