Multitexture bucket issues with DR

[Svetlozar Draganov]

Glad to hear you sorted it out.
Let us know if it happens again.

[akc]

Is there is some thing new about it? We have the same problem with refractive objects. It is difficult to reproduce it, it's some kind of random bad bucket effect. And it looks different on different machines...

Many thanks in advance,

Alex

[Svetlozar Draganov]

Which V-Ray version you are using?
The latest 3.10.03 has some bug fixes on that matter - our advice is to update to that version and check if the same issue still appears.

There is also a bug with Bitmap node in 3DSMax 2014/2015 which could be workaround if VrayHDRI is used instead - please check the thread bellow:
http://forums.chaosgroup.com/showthr...t=bucket+gamma

[akc]

Thank you Svetlozar,

sorry, it was actually the wrong thread to ask about it, because we use Maya 2015 and release build of V-Ray 3.0. I've searched for this problem on the forum and this thread was one of the latest.

Which nightly build would you recommend to use with Maya? Or may be there is a official update around the corner?

Best regards,
Alex

[Svetlozar Draganov]

Then it would be better to open a new thread into Maya section or contact us directly at support@chaosgroup.com

The issue you are talking about looks very similar to the one reported bellow:
http://forums.chaosgroup.com/showthr...773#post641773

[trixian]

Ok, I'm going to nekro this thread, as we are having lots and lots of issues with multitexture specifically.

We use this on loads of stuff, and prefer it over vraymultisubtex because of the randomizations of hue sat and gamma, plus the faster workflow when loading multiple textures.
Most times this is used on floors and similar generated with the floorgenerator script (from Suurland as well), but happens on any othe object using the plugin-map.

We just (today) upgraded all machines to vray 3.20.01 while keeping the multitexture version 2.01 (latest) as it is loaded by all machines from a network location together with other freeware plugins.

We all run W7 and 3dsmax 2015 a.t.m, all updates included

We have 3 workstations, and 4 slaves.

• 3 of our slaves are consistently rendering correctly, with any of the workstations.

• One of the slaves renders wrong on all dr jobs regardless who submit it.

• Our 3 workstations can not contribute to each others dr jobs at all, for some reason, when using Multitexture.

• Multitexture renders ok on any workstation when the job is started from that specific workstation, but fail when contributing to dr. (Meaning the plugins is loading correctly and can be used on the machine as normal).

The main effect of this is dr-machines not loading the texture, just returning the diffuse value of the material.

This happens with both the 3dsmax bitmap-loader, and vrayhdri lading the maps.

Please look into this

[tricky]

We just (today) upgraded all machines to vray 3.20.01 while keeping the multitexture version 2.01 (latest) as it is loaded by all machines from a network location together with other freeware plugins.

We have in the past (many years ago) let our servers load plugins from a central location. We had some problems, though I don't recall exactly what they were. We now have them installed locally on each machine. Have you tried that?

Another issue we have had is when we use multitexture within an XREF scene. Mind you, this typically only gives gamma-type problems if I recall.

[trixian]

Well, here's an update.
Copying the plugin locally on all machines (slaves & workstations), actually worked.
I must say I'm quite relieved, but at the same time I find it strange that loading it from the network would result in dr failing while starting a regular max-session is ok.
Is this a Vray issue (how it handles DR and max), a Jerry Ylilami screw-up, or plain old Autodesk?

[tricky]

Well, here's an update.
Copying the plugin locally on all machines (slaves & workstations), actually worked.
I must say I'm quite relieved, but at the same time I find it strange that loading it from the network would result in dr failing while starting a regular max-session is ok.
Is this a Vray issue (how it handles DR and max), a Jerry Ylilami screw-up, or plain old Autodesk?

Good news

[tashko.zashev]

Well, here's an update.
Copying the plugin locally on all machines (slaves & workstations), actually worked.
I must say I'm quite relieved, but at the same time I find it strange that loading it from the network would result in dr failing while starting a regular max-session is ok.
Is this a Vray issue (how it handles DR and max), a Jerry Ylilami screw-up, or plain old Autodesk?

Do you run the V-Ray spawner on this render node as a service ?
If yes, then please check the login account used by the service. Maybe it can not access the plugin folder.

Do you use the Transfer missing maps option ?

[trixian]

Spawner is always running as a service on all machines, and the service has admin light for it's logon id.
Transfer missing maps is also on as default here now, though not cached assets.
In addition, the path in the ini file pointing to the shared plugins folder was set up with UNC-paths and regular letter-mapped drives paths, but it made no difference.

We ended up making a halfway automated system where we set up a dropbox account that hosts the plugins, which then shares this folder into our workplace's dropbox.
Remapping the path is the ini file to the new shared Dropbox folder actually works, so we still get the benefit of a central repository, and the max loads them correctly. Still more hassle than hosting them on a central fileserver.

[tashko.zashev]

Thanks for the update.

Would it be possible to run a test with V-Ray spawner started manually and inform us about the result?
If you are not satisfied with the results you get with Dropbox, we can offer a remote session in order to troubleshoot the issue further.