I haven’t used V-Ray for a while but I’m getting back into it for a simple TyFlow particle job, and I’m seeing really poor GPU performance. I’m using Max 2023, the latest V-Ray GPU, and the latest TyFlow. The scene has a few million particles cached via TyCache and rendered as low-res spheres, with instancing enabled but render times are insanely slow.
V-Ray hangs for ages on compiling kernels, “Cleaning up geometry” takes forever, and the “Starting render” phase is just as bad. It’s like it’s ignoring instancing entirely. I’m running 2 × RTX 3090s and I swear this setup used to handle similar scenes much faster.
Others in the TyFlow support group are reporting the same issue, and consensus seems to be that this is a V-Ray GPU problem, not TyFlow.
Honestly a bit weird to come back to V-Ray after 18 months and find GPU rendering hasn’t improved at all. Especially disappointing given they’ve also pretty much dropped Phoenix dev alongside jacking up the pricing and making licenses more expensive. Any insight from the team?
this is quite an urgent issue given its a commercial job and my render farm is all GPU
several other people also having the same issues as well on the tyflow facebook support
There definitely is a huge slowdown between frames when rendering tyCache with geo within it. It’s very possible that instancing is not supported on the GPU, but the devs must confirm. I’ll log the case for investigation.
There’s an easy workaround, however, which you can try: disable the Shape operators in the tyFlow (so as only to export the particles), export to tyCache, and use VRayInstancer for the instancing instead. To pick the tyCache as a particle system, you need to enable the Particle Interface in the tyCache settings (tyCache > Elements > Particle interface > Enable particle interface). I don’t get the slowdown when rendering it in the GPU like so. Try it out.
EDIT: Logged as (internal tracker ID: VGPU-6858 ).
Just bumping this again really hope you guys can take a proper look…
This issue still makes it borderline impossible to use TyFlow with V-Ray GPU in any serious workflow. It’s a massive bottleneck and directly adds extra time and cost to projects we’re basically forced back onto CPU rendering, which is painfully slow for compared to GPU
Over the last few years I’ve used this combo on probably 90% of my paid work. So I just want to reiterate: not fixing this doesn’t just feel like a technical gap it feels like a decision against long-term users. It’s actively making things harder for the people who rely on your tools the most.
Hope this can be escalated it’s a real deal-breaker.
We have some Tyflow tasks that were not finished, including this one. The developer working on this left the team, and no one picked up after him so far. This is not meant to be an excuse, it is not great we haven’t tackled this yet.
It is one of the highest priority items this year, and so far no progress sadly. We will escalate this today again
Wanted to check on this and see if there are any new updates or an ETA as to when this will be working again? I was planning on using V-Ray GPU with TyFlow extensively, actually have been attempting to, but it’s just not possible in this state. I’d love to keep using V-Ray, but it’s looking like I’ll have to move to another GPU renderer as I need a working solution immediately.
Seems to be a common theme at Chaos good devs leaving (see how Phoenix development stalled).
I know it’s your job to spin this, but breaking something as core as TyFlow GPU support is just dumb, especially when it’s essential to any particle work in Max.
Waiting a year to fix it isn’t good enough tbh
Since Chaos sold out to investors, the overall direction and quality of the product has tanked. I’ve already cancelled my extra V-Ray licenses, stopped using Phoenix, and after spending hundreds on CPU cloud rendering (while my 4090 GPU farm sits idle), I’m done. I wasnt even THAT fussed about the pricing but now I look at what’s happened it can only be viewed as anti user taking our sub money to develop things we dont use.
This is the final straw after 15+ years and 25+ V-Ray licenses
.
In hindsight, we should’ve switched to Redshift or Octane the moment Chaos started deprioritizing its core tools in favor of a range of average real-time products, raising prices, and forced subscriptions.
I know an increasing number of people are pretty unhappy about this.