Error loading Voxel 0 for mesh file

[mori4h]

Hello,
Suddenly we started randomly getting this type of errors with Vray on this project, and we can't seem to figure it out. The error is reported via Deadline, but it's not a deadline issue. It's related to vrmesh and the vrayproxy. I tried changing to UNC and even to another server and the error persists.

2023/02/15 20:49:46 INF: [11680] [09652] [V-Ray] ================================================== ==========

2023/02/15 20:49:46 INF: [11680] [09652] [V-Ray] Console created, V-Ray 6.01.00 for x64 from Feb 14 2023, 13:15:15

2023/02/15 20:49:46 INF: [11680] [09652] [V-Ray] ================================================== ==========

2023/02/15 20:49:46 INF: [11680] [09652] [V-Ray] Compiled with Microsoft Visual C++ compiler, version 19.24

2023/02/15 20:49:46 INF: [11680] [09652] [V-Ray] Host is 3ds Max, version 25

2023/02/15 20:49:46 INF: [11680] [09652] [V-Ray] V-Ray DLL version is 6.01.00

2023/02/15 20:49:50 DBG: [11680] [09652] FOREST 8.0.7 V-Ray DLL loaded from c:\programdata\autodesk\applicationplugins\forestp ackpro2023\contents\plugins\2023\ForestVRay60.dll

2023/02/15 20:49:56 INF: [11680] [09652] Done loading file: C:/ProgramData/Thinkbox/Deadline10/workers/GLNODE11/jobsData/63ed4084e7e16837ac37d2bf/pa2_s620_lgt_v001_main.max

2023/02/15 20:49:56 INF: [11680] [09652] SYSTEM: Production renderer is changed to V-Ray 6 Update 1. Previous messages are cleared.

2023/02/15 20:49:56 WRN: [11680] [09652] A non OSL shader (Map V-Ray for Rhino :: Issues (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map V-Ray for Rhino :: General (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:49:56 WRN: [11680] [09652] A non OSL shader (Map #835 (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map #109 (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:49:56 WRN: [11680] [09652] A non OSL shader (Map Chaos Phoenix :: Wishlist (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map #102 (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:49:56 WRN: [11680] [09652] A non OSL shader (Map Chaos Phoenix :: Wishlist (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map #848 (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:49:56 WRN: [11680] [09652] A non OSL shader (Map #106 (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map #105 (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:49:56 WRN: [11680] [09652] A non OSL shader (Map #106 (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map #850 (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:49:56 WRN: [11680] [09652] A non OSL shader (Map #922 (VRayCompTex)) was connected to the input 'Input_map' of an OSL shader (Map #928 (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:49:56 WRN: [11680] [09652] A non OSL shader (Map #941 (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map #942 (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:49:56 WRN: [11680] [09652] A non OSL shader (Map #1217 (Gradient Ramp)) was connected to the input 'Input_map' of an OSL shader (Map #1218 (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:49:56 WRN: [11680] [09652] A non OSL shader (Map #1216 (VRayCompTex)) was connected to the input 'Input_map' of an OSL shader (Map #943 (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:50:01 WRN: [11680] [09652] A non OSL shader (Bitmaptexture_VRay (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map V-Ray 3.0 for Maya public beta :: General (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:50:01 WRN: [11680] [09652] A non OSL shader (Bitmaptexture_VRay (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map #842 (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:50:01 WRN: [11680] [09652] A non OSL shader (Bitmaptexture_VRay (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map V-Ray 3.0 for Maya public beta :: Images (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:50:01 WRN: [11680] [09652] A non OSL shader (Bitmaptexture_VRay (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map #844 (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:50:01 WRN: [11680] [09652] A non OSL shader (Bitmaptexture_VRay (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map V-Ray 3.0 for Maya public beta :: Problems (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:50:01 WRN: [11680] [09652] A non OSL shader (Bitmaptexture_VRay (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map #852 (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:50:01 WRN: [11680] [09652] A non OSL shader (Map #118 (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map #117 (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:50:01 WRN: [11680] [09652] A non OSL shader (Map #118 (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map #846 (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:50:01 WRN: [11680] [09652] A non OSL shader (Map V-Ray for SketchUp :: General (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map #119 (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:50:01 WRN: [11680] [09652] A non OSL shader (wgxlbc3aw_4k_albedo (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map #901 (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:50:01 WRN: [11680] [09652] A non OSL shader (Albedo (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map #918 (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:50:01 WRN: [11680] [09652] A non OSL shader (Albedo (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map #919 (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:50:01 WRN: [11680] [09652] A non OSL shader (Albedo (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map #917 (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:50:03 WRN: [11680] [09652] A non OSL shader (albedo (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map #951 (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:50:03 WRN: [11680] [09652] A non OSL shader (ulylecao_4k_albedo (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map #2138626855 (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:50:03 WRN: [11680] [09652] A non OSL shader (Map #2138626845 (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map #2138626848 (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:50:05 WRN: [11680] [09652] A non OSL shader (Map #21_VRay (VRayBitmap)) was connected to the input 'Input_map' of an OSL shader (Map V-Ray for Modo (OSL: Color Correction)). This can lead to suboptimal performance, and will be less portable. Try to use only OSL shaders.

2023/02/15 20:54:10 ERR: [11680] [09652] [V-Ray] [DefMeshFile::getVoxel] 59: Error loading voxel 0 for mesh file "S:\2023\playground_altice_2023_pa2\20_assets\ env\ florest\06_caches\proxy\MT_PM_V67_Picea_rubens_01_ 06.vrmesh"

2023/02/15 20:54:10 ERR: [11680] [09652] [V-Ray] [VUtils::MeshVoxel::load] 59: Error loading mesh voxel

2023/02/15 20:54:10 ERR: [11680] [09652] An unexpected exception has occurred in the network renderer and it is terminating.


Any idea of what it might be? We also using Forest Pack the latest version. (ignore the extra spaces on the path, its a paste issue)

Several vrmeshes are being used, locally it's fine. The specific vrmesh is random.

We getting desperate here eheh

[mori4h]

I've tried everything and still no solution, other than reimporting the mesh, exporting as alembic (instead of vrmesh) and replace the proxy with the abc. It solved the issue.

So there seems to be a bug/problem with vrmesh?

[mori4h]

Any idea what might be causing this? We've stopped using vrmesh in the middle of production to avoid this issue.

[vladimir_krastev]

Hi, thanks for posting. Could you upload a simplified version of the scene that reproduces the issue? Please do that here or trough our support contact form. Please do not forget to include a link to this thread in your e-mail so we can track your issue.

[oleg_svirsky]

Same problem, solution??

[vladimir_krastev]

Hi, oleg_svirsky could you share a bit more details about your issue? It will be great if you could share the log as mori4h did. Are these issues happening in every scene? Are you having the same issue if you render the scene with distributed rendering or another render manager other than Deadline?
Have you updated your V-Ray and Deadline to the latest versions?

[oleg_svirsky]

this is happening with local render, with big projects 1400+ accets whet turning of conserve memory it renders better, less errors, if i render with distribute render some of machines render fine and some cant render at all

[oleg_svirsky]

i think that the problem in assets and memory management. all assets is stored on nas (ssd) server

[saddington_baynes]

We had a similar issue in Maya,

We discovered it was only happening when we submit 2 or more different proxy assets that are rendering at the same time. In order to avoid this we setup dependancies so that each set of renders with a different proxy asset waited until the previous one finished.

Not a full solve but a decent work around.

Here is my original post detailing more of our issue: https://forums.chaos.com/forum/v-ray...error-getvoxel