Latest SPs on max, latest Version of VRay 3.6.
Situation:
Polygon object with an applied "Displace"-Modifier (The standard max one, not VRayDisplacement). Inside it as a Map a VRayHDRI-Map with a 32bit exr file.
Distributed rendering with one slave, slave has VRaySpawner started as administrator. In the host machine, "Transfer missing assets" is on, cached is off.
Expected behaviour:
Both of the nodes render the displace-effect.
Observed behaviour:
The slave node ignores the displace modifier.
Other observations:
According to the log, the displacement-map does not get transferred when using VRayHDRI bitmap loader. As soon as I switched the bitmap loader to the standard max one, the map got transferred.
Conclusion:
In this constellation VRay ignores the VRayHDRI-Map in the Displace-Slot when deciding which assets to transfer. Bad. Behaviour can be circumvented by using the standard 3ds max bitmap loader, so no troubleshooting by support is required for this issue.
Situation:
Polygon object with an applied "Displace"-Modifier (The standard max one, not VRayDisplacement). Inside it as a Map a VRayHDRI-Map with a 32bit exr file.
Distributed rendering with one slave, slave has VRaySpawner started as administrator. In the host machine, "Transfer missing assets" is on, cached is off.
Expected behaviour:
Both of the nodes render the displace-effect.
Observed behaviour:
The slave node ignores the displace modifier.
Other observations:
According to the log, the displacement-map does not get transferred when using VRayHDRI bitmap loader. As soon as I switched the bitmap loader to the standard max one, the map got transferred.
Conclusion:
In this constellation VRay ignores the VRayHDRI-Map in the Displace-Slot when deciding which assets to transfer. Bad. Behaviour can be circumvented by using the standard 3ds max bitmap loader, so no troubleshooting by support is required for this issue.
Comment