You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -50,25 +79,9 @@ The following list applies to Windows Server 2016, version 1.3.7 rendering image
50
79
* Chaos Group V-Ray for 3ds Max 2019 (version 4.10.01)
51
80
* Blender (2.79)
52
81
53
-
54
82
> [!NOTE]
55
83
> Chaos Group V-Ray for 3ds Max 2019 (version 4.10.01) introduces breaking changes to V-ray. To use the previous version (version 3.60.02), use Windows Server 2016, version 1.3.2 rendering nodes.
56
84
57
-
## Applications on previous Windows Server 2016 rendering images
58
-
59
-
The following list applies to Windows Server 2016, version 1.3.2 rendering images.
* Autodesk 3ds Max I/O 2019 Update 1 (version 21.2.0.2219)
64
-
* Autodesk 3ds Max I/O 2018 Update 4 (version 20.4.0.4254)
65
-
* Autodesk Arnold for Maya 2017 (Arnold version 5.2.0.1) MtoA-3.1.0.1-2017
66
-
* Autodesk Arnold for Maya 2018 (Arnold version 5.2.0.1) MtoA-3.1.0.1-2018
67
-
* Autodesk Arnold for 3ds Max (Arnold version 5.0.2.4)(version 1.2.926)
68
-
* Chaos Group V-Ray for Maya 2019 (version 3.52.03)
69
-
* Chaos Group V-Ray for 3ds Max 2018 (version 3.60.02)
70
-
* Blender (2.79)
71
-
72
85
## Next steps
73
86
74
87
To use the rendering VM images, they need to be specified in the pool configuration when a pool is created; see the [Batch pool capabilities for rendering](https://docs.microsoft.com/azure/batch/batch-rendering-functionality#batch-pools).
0 commit comments