vrayDeadline error with Vray 7

[mori4h]

Hi, I just installed Vray 7 for Houdini, and while trying the vrayDeadline submitter i have this error:

[2025/Jan/31|17:54:22] [215 MB] error: Error in file "C:\ProgramData\Thinkbox\Deadline10\workers\GL Pedr o\jobsData\679d0f1f0337fcdc5b557d96\thread0_temp3T zDz0\vrayTest.1.vrscene", line 441: Functor "ListIntHash" not recognized

at Deadline.Plugins.PluginWrapper.RenderTasks(Task task, String& outMessage, AbortLevel& abortLevel)


It's an empty scene with just a test geo + cam + light, rest is default. Deadline is latest version, Houdini 20.5.410, Vray 7.

I installed the vray 7 standalone and updated the path in the plugins for deadline.

Everything is on the network, the vrscene is calculated locally just fine.

Any idea what's causing this?



C:\Program Files\Chaos\V-Ray\Standalone for x64\bin>vray.exe -sceneFile="D:\vrayTest.1.vrscene"
[2025/Jan/31|19:04:18] [17 MB] Reading configuration from "C:\Program Files\Chaos\V-Ray\Standalone for x64\bin\vrayconfig.xml"
[2025/Jan/31|19:04:18] [17 MB] ===============================================
[2025/Jan/31|19:04:18] [17 MB] V-Ray Standalone, version 7 Standalone Hotfix 1 for x64
[2025/Jan/31|19:04:18] [17 MB] Copyright (C) 2000 Chaos Software EOOD. All rights reserved.
[2025/Jan/31|19:04:18] [17 MB] Use -credits option for additional third-party copyright notices.
[2025/Jan/31|19:04:18] [17 MB]
[2025/Jan/31|19:04:18] [17 MB] Build 500f34b3 from Nov 17 2024, 17:56:06
[2025/Jan/31|19:04:18] [17 MB] Compiled with Microsoft Visual C++ compiler, version 19.4, target ISA: avx2
[2025/Jan/31|19:04:18] [17 MB] Operating system is Microsoft Windows 11 Pro (Build: 10.0.22631)
[2025/Jan/31|19:04:18] [17 MB] CPU: AMD, AMD Ryzen 9 7950X 16-Core Processor , 4491 MHz, threads: 32
[2025/Jan/31|19:04:18] [17 MB] ISA: SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, POPCNT, SSE4a, AVX, AVX2, FMA, BMI1, BMI2, SHA, F16C, AVX512_F, AVX512_DQ, AVX512_IFMA, AVX512_CD, AVX512_BW, AVX512_VL, AVX512_VBMI, AVX512_VBMI2, GFNI, VAES, VPCLMULQDQ, AVX512_VNNI, AVX512_BITALG, AVX512_VPOPCNTDQ, AVX512_BF16
[2025/Jan/31|19:04:18] [17 MB] RAM: 130208 MiB
[2025/Jan/31|19:04:18] [17 MB]
[2025/Jan/31|19:04:18] [17 MB] V-Ray core version is 7.00.04
[2025/Jan/31|19:04:18] [17 MB] ===============================================
[2025/Jan/31|19:04:18] [17 MB]
[2025/Jan/31|19:04:18] [88 MB] [USD] Loaded 0.23.11 USD provider.
[2025/Jan/31|19:04:19] [104 MB] Loading plugins from "C:\Program Files\Chaos\V-Ray\Standalone for x64\bin\plugins\vray_*.dll"
[2025/Jan/31|19:04:20] [221 MB] 82 plugin(s) loaded successfully
[2025/Jan/31|19:04:20] [221 MB] Finished loading plugins.
[2025/Jan/31|19:04:20] [221 MB] Reading scene file "vrayTest.1.vrscene"
[2025/Jan/31|19:04:20] [221 MB] error: Error in file "D:\vrayTest.1.vrscene", line 441: Functor "ListIntHash" not recognized
[2025/Jan/31|19:04:20] [155 MB] Closing log - 1 error(s), 0 warning(s).
[2025/Jan/31|19:04:20]
[2025/Jan/31|19:04:20] Max memory usage: 221 MB
[2025/Jan/31|19:04:20] Issues Report:
[2025/Jan/31|19:04:20] Errors:
[2025/Jan/31|19:04:20] Error in file "D:\vrayTest.1.vrscene", line 441: Functor "ListIntHash" not recognized

[mori4h]

Checked that the latest standalone version is 70004 from 19th Nov 2024, and Houdini is on 70010... Maybe standalone needs an update?

[bdancer]

1. You could use Standalone shipped with V-Ray for Houdini at the render nodes.
2. If it's not possible, you could disable "Use Array Data Hash" at the ROP settings.

[mori4h]

Using the included standalone worked, thank you!

edit: bdancer is there any way for deadline to correctly interpret the $F4 on vray's file path?
On our deadline when we double click a completed frame from the job, it opens Chaos Player with the exr sequence, however with vray it's giving me this error. I use the same tag in other renderers with deadline and they open up normally.


Using ${F}.exr also returns a similar error:

[bdancer]

> Using the included standalone worked, thank you!

Great!

> is there any way for deadline to correctly interpret the $F4 on vray's file path?

Next nighlty will translate this tag as #-pattern for job's OutputFilename, hope this'll help with this issue.