When this happens, V-Ray opens the file for reading and reads from it an index table that generally describes where the actual data is located in the file, for each frame. The table is relatively small and usually located at the end of the .vrmesh file. The file is kept open for reading during the rendering process, but V-Ray doesn’t read any actual data until it’s needed.
does it seek in the file to access required frame at the rendering step?Yes, V-Ray will only read the data that it needs for rendering a particular frame; it will not read the entire file.
does it make a difference if it is one big vrmesh vs 1 frame vrmesh?Ideally it shouldn’t make any difference at all.
When you’ve tested on your side, were you using vrmeshes with multiple frames inside or vrmeshes “by frame”?I was testing multiple frames inside one file.
Best regards,
Vlado