Hello we are encountering problems with # tag for sequential loading in vray proxy object. Its totaly random sometimes it loads sometimes not, and also <use_alembic_offset> and <offset> are used even if they are disabled with sequentioal loading.
We are on vray 6.10.08 and max 22. Can someone confirm this?
Thanks
We’d be keen on investigating a sequence that fails.
Any sequence it doesn’t matter. The # just doesn’t work. Sometime it popups if you check/unchek some other parameter (like flip axis) but when I move the timeline it disappear again.
V-Ray doesn’t create *proxy* sequences consisting of multiple filenames.
As such, yours must be an ABC loaded via our proxy, and the variables for what is inside an ABC sequence are many, and out of our control.
It doesn’t repro here, naively attempting it, and we have no other report of such behaviour (but we have had three of ABC issues, unrelated to this.).
So, without a misbehaving sequence, we’re in no position to help you.
edit: in *nightlies* we have minor issues with abc preview in viewport (code logic), but none seems to affect sequence loading for rendering.
Yes is alembic sequence of course, sorry I didn’t mention it. I thought it was obvious because the alembic parameters I mentioned. I’ll send some files then.
Thanks
I just updated to the lates slable and its still there. So its not an UI problem, but in render loads fine.
Something has been found by the devs, they’re working on a fix.
Thank you Lele
Hello!
I sometimes export alembic sequences from Houdini to use in Max and I have this issue all the time. As I was creating my file to send to you I think I solved it! Houdini’s timeline starts at 1, max starts at 0. I set my max timeline to start from 1 and be the exact length of the alembic sequence and I haven’t had any more issues with loading. Even after closing and opening the file, saving out viewport sequences etc. Basically everything that caused the file to unload previously.
I haven’t had any issues with frame offsets.
Hope this helps!
Also please share any tips from the Devs team.
There are so many advantages to using Alembic sequences over one humongous Alembic there are too many to write down! I’d love to see a more stable solution for these in future updates.
Cheers!
Hello! The above worked for me but I’m now running into issues again. There seems to be more stability when rendering in GPU, when swapping to CPU the alembic keeps dropping out. As in displaying and rendering as a box. To fix it I need to swap around the Preview Type in the Vray Proxy, this reconnects the alembic somehow. I’ve uploaded a simple scene along with the alembic here. https://drive.google.com/drive/folders/14W74rAYq-Na3f54igLdpB8GPh1FyuZmx?usp=drive\_link
If someone could please take a look and let me know if there is a fix for this that would be great!
To get back on this, the original issue is fixed, the loader was getting confused if a frame had no data in it.
Many thanks for the report and help!
@richard_stewart this should have fixed your issue as well, likely.
I couldn’t repro it on my side, let me know if it isn’t fixed though!
Unfortunately after a year of persuading Thinkbox sequence tag in vray scene still doesnt work on Deadline. I know this is not your fault but maybe you have better leverage how to convince them to fix it.
edit: nvm, i was wrong. 
We’ll see what can be done.
It has been working for me over deadline when rendering with GPU. With CPU Rendering, most of the time it was not loading the file and rendering a box. This was also happening intermittently in the viewport and rendering when working locally with the CPU renderer selected. Technically I have no idea how to fix this, but in terms of functionality maybe the solution is not through a vray proxy but rather through a new type of Alembic loader/file import system. I’m working mostly with Houdini and there is a specific node for Alembic files and needs the sequence tag $F4 to load a sequence. When you go to a frame that is out of the range of the alembic sequence the object just disappears, to me it looks like it’s the bounding box display maybe be part of the problem as it keeps popping back to that.
There are so many advantages to using a sequence over a single file. The main one for me is that the cache can fail halfway through and at least you have something that can get rendering right away but if a single alembic cache dies halfway through you need to start over, also you can check the sequences for issues while the cache is still going.
Sorry to bang on about it! Just trying to give as much info as possible.
Cheers!
You are very welcome!
If you have a failing cache, and ideally a houdini file that exported it, we’d be keen to see it.
If we can reproduce it, then there’s a chance for a fix.
Hello I’m here again
Because of this bug in Deadline only way how to render Vray Scene sequence is creating one Vray Scene file which includes all frames for example
include “test_1000.vrscene”
include “test_1001.vrscene”
include “test_1002.vrscene”
#include “test_1003.vrscene”
.
.
.
.
this workaround renders fine but it loads all the frames to RAM at once which takes soooooo much time and RAM. So my question is how can I solve this.
Thanks