Announcements

Between mid-October and November, the content on AREA will be relocated to the Autodesk Community M&E Hub and the Autodesk Community Gallery. Learn more HERE.

MayaBatch with Reference's fails to render

MayaBatch with Reference's fails to render

Anonymous
Not applicable
844 Views
2 Replies
Message 1 of 3

MayaBatch with Reference's fails to render

Anonymous
Not applicable

Hi Everyone,

 

We are unable to use Thinkbox with MayaBatch with renders to external reference files that don't instantly fail, but we aren't using Maya MASH. If we include the references inside the file itself, it renders fine else wise it just does this with no details on why it is exiting. I saw that someone referenced it may be a bug in 2018.3 but can anyone confirm such? 

 

C:\Users\administrator\Desktop>"C:\Program Files\Autodesk\Maya2018\bin\Render.exe" -r redshift -x 1920 -y 1080 -s 48 -e 48 -b 1 -rd "Y:/********/CWL_Elevate/CGI/Maya/images" -im "<Scene>/<Camera>" -proj "Y:/SundbergFerar/CWL_Elevate/CGI/Maya" "Y:\********\CWL_Elevate\CGI\Maya\scenes\Rescue Vignette\Shot1n2_Lighting_v8.mb"

 

Initialized VP2.0 renderer { Version : 2016.11.40.12. Feature Level 5.

  Adapter : NVIDIA GeForce GTX 1080 Ti

  Vendor ID: 4318. Device ID : 6918

  Driver : C:\Windows\System32\DriverStore\FileRepository\nvdd.inf_amd64_1beb6cbf8800706c\nvldumdx.dll,C:\Windows\System32\DriverStore\Fil:23.21.13.8795.

  API : DirectX V.11.

  Max texture size : 16384 * 16384.

  Max tex coords : 32

  Shader versions supported (Vertex: 5, Geometry: 5, Pixel 5).

  Active stereo support available : 0

  GPU Memory Limit : 11264 MB.

  CPU Memory Limit: 62076.1 MB.}

OpenCL evaluator is attempting to initialize OpenCL.

Detected 2 OpenCL Platforms:

 0: Intel(R) Corporation. Intel(R) OpenCL. OpenCL 2.1 .

Supported extensions: cl_intel_dx9_media_sharing cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_d3d11_sharing cl_khr_depth_images cl_khr_dx9_media_sharing cl_khr_fp64 cl_khr_gl_sharing cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_icd cl_khr_image2d_from_buffer cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_spir

1: NVIDIA Corporation. NVIDIA CUDA. OpenCL 1.2 CUDA 9.1.56.

Supported extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_nv_create_buffer

OpenCL evaluator choosing OpenCL platform NVIDIA Corporation.

Choosing OpenCL Device GeForce GTX 1080 Ti.  Device Type: GPU  Device is available.

[Redshift] Redshift for Maya 2018

[Redshift] Version 2.6.21, Sep  6 2018

// Maya exited with status 1

0 Likes
845 Views
2 Replies
Replies (2)
Message 2 of 3

sean.heasley
Alumni
Alumni

Hi @Anonymous

 

There is indeed a known issue for this that was fixed with Update 4 of 2018 but it was using MASH like you mentioned above.

 

Even though you aren't using any MASH in your scenes I would recommend updating your 2018 and attempt to render.

 

 

0 Likes
Message 3 of 3

sean.heasley
Alumni
Alumni

Hi @Anonymous

 

Just wanted to check in to see how things were going. Are you still having this issue?

 

If your issue is resolved, please click Accept as Solution on the posts that helped you so others in the community can find them easily.

 

 

0 Likes