Why is it that Vray (build N) takes so long to cancel a render? Is there a specific reason why a bucket can’t be killed immediately when you cancel the render? I find myself wasting a LOT og time waiting because of this…
i think it has something to do with clearing the memory again. there used to be a thread about this some time ago.
I find it pretty annoying too actually.
wouter
Thanks, Flipside… Actually, I think I started that thread also. I just thought I’d ask one last time before I go raving mad.
Why should vray be different than any other renderer, regarding memory?
It this also the case in the new beta release?
be glad that you don´t use DR. :twisted:
with the 1.46 betas you have to close all clients or your server will hang forever, sometimes.
there is a long road to go till we see v1.5 as it should be.
im wondering how some betatester could made promises like “v1.5 will be out soon” or “only a few minor bugs to fix”, back in june. :evil:
seeing this 1.46 beta-bug-mess:
DR still not working after 1 year!!
opacity, glossy, lightmap problems.
and how really think that the standalone will make things better?
it will become worse, trust me.
ah i lost hope. i want a rendere that works without “exception in blahblah” windows poping up all day. 
It’s the same in the 1.46 version, especially when using bucket mode or with 3d displacement.
ah i lost hope. i want a rendere that works without “exception in blahblah” windows poping up all day.
hey just turn off the vray log window then. 
Hi percy,
It’s not in the log, it’s a real popup! Usually I click it away and there’s no problem, I wonder why they come up actually. Sending the file each time it pops up would be a full time job though 
wouter
ps: why is that quote thing not working for me?
oh I see. Ok haven’t gotten any of those. been using DR fine since yesterday.
this is done with DR. and its high poly. still havent seen any error or anything yet and th epoly count keeps raising. there is glass which means reflection and refraction and there is no problem with it. there is also glossies in the scene too. not sure whats not working for you
I’m just trying out all kinds of stuff in the new build, and I get popups regularly. I’m playing with fur, displacement, lightmaps, etc…
I will pay more attention to them if it comes again
you rendered one highpoly image with nearly no maps.
how many renderslaves are rendering on that image?
there are so many things to consider.
the problem is that it happens to often that with 10 clients, one will hang or render strange buckets.
i agree vray DR works 3 of 5 times.
that you have to remove temp files on render clients is a bug that should be fixed easily, but it´s known since 1.46.02 at least. ok i wrote a batch to do this but hey is it my job to fix vray flaws?
now sure someone will say : use 1.09.3r as 1.46 are betas.
but do we have a choice when we want DR?
render stripes, sure. at least this way it will work.
Eh well, is it our job to fix the bugs of 3dsmax? No, but we have to find ways around them nevertheless.
Best regards,
Vlado
no of course not.
but you make money with selling a product for max.
i love how developers blame others for their mistakes.
it is maybe the case here, i don´t know what causes all the DR problems with max 6/7.
but it reminds me a bit on your changes to the render setting with every new version.
no documentation of changes and the customers have to pull one’s hair out to solve the problems.
so you should understand why people complain? not? 
no of course not.
but you make money with selling a product for max.
Yep, that’s why I said we’re trying to find ways around them
Best regards,
Vlado
You guys have been busy since I started the thread. Just in time before Mr. Prozac…
I can’t remember having had the same problem with any other renderer, so it can’t be all MAX??
if i have to guess, then i think it is the same issue as the not working pause button.
correct me if im wrong.
but if im not wrong then i read that checking for mouseclicks or keystrokes will slow down vray so much that this feature is disabled.
maybe it takes so long because vray will only check every 10-15 seconds for a user input?
at least it´s an idea, when you hear no other comments.
Don’t think that’s the reason, because you don’t have the problem with simple scenes.
was only a idea.
just now im waiting for 10 minutes that i can use max again because i chanceled a rendering of a scene where i use lightmaps.
vray just hangs (100% cpu utilization, no viewport update).
first i saw no progress on the lightmap and now it looks like i have to quit max via the taskmanager. i can repeat this problem with many high poly scenes + displacement.
We need a ‘kill’ button instead of just ‘stop’
If the problem is the way max stop button behaves, isn’t it possible to make a vray-stop button? Something that works like task manager that kills everything inside the process immediately except the process itsself?
regards,
wouter