Tweet
It looks like if you give max a drive alias (d:\) or what-
ever you have it named MAX actually sees the UNC name and uses that.
What I am wondering is, does VRay use the literal Alias or the UNC
(behind the scenes) or does it matter at all? Not familiar enough with
networking to know if this is an issue or not.
For example k:\project1\maps is \\192.100.100.7\maps
so in terms of the map it reads \\192.100.100.7\project1\maps\wiremesh.jpg
and the IRMap in VRay dialog reads k:\project1\irmaps\irmap1.vrmap
Do all programs regardless use the UNC and only display the alias?
We are having some issues where network drives display the "not connected" icon on the drive name (little red X).
This is normally breif and appears to cause no problems, its as if the drive
loses connection for a second and then is fine.
There is however an issue with IRMaps not loading and I wonder if it is related.
There appears to be no other cause as the IRMap is good proven by
rendering the suspected bad frame locally where there are no apparent
connectivity issues.
I am of course aware that is the target drive is not available it will fail
just wondering why (apparently) the drive behaves normally for any
other operations or functions and the IRMap appears to not load.
The drive that show as disconnect still work, I can browse the drive and get there.
Sometimes when you refresh the explorer the x stays though otherwise the drive behaves normally.
Some slaves will render a frame without the IRMap and the next one with it.
Frames or stills that do not call an IRMap render fine.
ever you have it named MAX actually sees the UNC name and uses that.
What I am wondering is, does VRay use the literal Alias or the UNC
(behind the scenes) or does it matter at all? Not familiar enough with
networking to know if this is an issue or not.
For example k:\project1\maps is \\192.100.100.7\maps
so in terms of the map it reads \\192.100.100.7\project1\maps\wiremesh.jpg
and the IRMap in VRay dialog reads k:\project1\irmaps\irmap1.vrmap
Do all programs regardless use the UNC and only display the alias?
We are having some issues where network drives display the "not connected" icon on the drive name (little red X).
This is normally breif and appears to cause no problems, its as if the drive
loses connection for a second and then is fine.
There is however an issue with IRMaps not loading and I wonder if it is related.
There appears to be no other cause as the IRMap is good proven by
rendering the suspected bad frame locally where there are no apparent
connectivity issues.
I am of course aware that is the target drive is not available it will fail
just wondering why (apparently) the drive behaves normally for any
other operations or functions and the IRMap appears to not load.
The drive that show as disconnect still work, I can browse the drive and get there.
Sometimes when you refresh the explorer the x stays though otherwise the drive behaves normally.
Some slaves will render a frame without the IRMap and the next one with it.
Frames or stills that do not call an IRMap render fine.
Comment