something wrong with material editor(slow materials showing)

[lukx]

There is something wrong with opening material editor, slots are loading really slow. It's only when vray is used to present material. When using standard it's okay. Enyone else noticed the same problem with new build?

[joconnell]

Yes - and I'm not using large bitmaps either, just glossy reflections in most cases.

[lukx]

for me it's loading slow even when there are just pure grey samples and it's on E6700 with 4GB ram.

[vlado]

Which max version is that? What licensing scheme are you using? It might be slow because V-Ray is trying to obtain a license every time that it renders a ME slot; if there is a problem obtaining the render license, this might take a while.

Best regards,
Vlado

[lukx]

I'm using software lic and 3dsmax 9 x 64. so what can we do with joconnell to have it work like RC2.

[vlado]

Ok, the next question is if your license server (VRLServer.exe) is running on the same machine or on another machine in the network.

Currently on Win64, V-Ray requires that the VRLServer.exe is used to grant the rendering license; in difference on Win32 machines if there is a local license installed, V-Ray will use it directly without requiring the VRLServer.exe to work.

Since in the Win64 case, the communication between V-Ray and VRLServer happens over the network, I suppose this may be where the problem occurs. When you click the Edit/Set license server info in the Render scene dialog, what do you have there?

Best regards,
Vlado

[lukx]

VRLServer.exe is runnig localy on machine that is using vray.
In edit/set in License server I added : localhost (this is how it was in RC2)
Connection port: 30303 (default). Online auth (empyt) - what is it for anyway?

[Paul Oblomov]

Hm. I think, that on win64 with max9 x64 (and of course max you can copy folder Program Files (x86)\Common Files\ChaosGroup (from 32-bit VRay) to Program Files\Common Files\ChaosGroup (this is the default folder, where native 64-bit programs store their files) - in this case you don't need to run lic server every time you launch max9 x64. It will work as in max8 with x86 VRay.

[lukx]

Hm. I think, that on win64 with max9 x64 (and of course max you can copy folder Program Files (x86)\Common Files\ChaosGroup (from 32-bit VRay) to Program Files\Common Files\ChaosGroup (this is the default folder, where native 64-bit programs store their files) - in this case you don't need to run lic server every time you launch max9 x64. It will work as in max8 with x86 VRay.

I did it and the problem is still the same.

[vlado]

Lukx, please check your private messages.

Hm. I think, that on win64 with max9 x64 (and of course max you can copy folder Program Files (x86)\Common Files\ChaosGroup (from 32-bit VRay) to Program Files\Common Files\ChaosGroup (this is the default folder, where native 64-bit programs store their files) - in this case you don't need to run lic server every time you launch max9 x64. It will work as in max8 with x86 VRay.

This will not work, as the license number for a true 64-bit program is different from that for a 32-bit program. That's why the vrlserver needs to be running on x64; it is a 32-bit program and so uses your existing license key. If it were a true 64-bit program, you'd need to get a new license key. This is because the CPU identifies itself in a slightly different way to 32-bit and 64-bit programs.

Best regards,
Vlado

[Paul Oblomov]

Your lic server were launched ?

[Paul Oblomov]

I'm telling about max9 64-bit. Why when I delete this folder (in program files) VRay asks for a license ? It really works again, when this folder (with lic info from 32-bit) is back.

[vlado]

I'm telling about max9 64-bit. Why when I delete this folder (in program files) VRay asks for a license ? It really works again, when this folder (with lic info from 32-bit) is back.

<shrug>It doesn't work for me either.

Best regards,
Vlado

[Paul Oblomov]

Strange (shrug twice). Maybe it's because I'm using win2k3 ?

[vlado]

Could be... I was testing on Vista Beta 2 64-bit edition.

Best regards,
Vlado