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...
Announcement
Collapse
No announcement yet.
Canceling a render?
Collapse
X
-
Tags: None
-
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?
Comment
-
be glad that you don´t use DR.
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.
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.
Comment
-
It's the same in the 1.46 version, especially when using bucket mode or with 3d displacement.
Comment
-
Originally posted by percydamanah i lost hope. i want a rendere that works without "exception in blahblah" windows poping up all day.
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?
Comment
-
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
---------------------------------------------------
MSN addresses are not for newbies or warez users to contact the pros and bug them with
stupid questions the forum can answer.
Comment
-
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
Comment
-
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.
Comment
-
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?
Comment
-
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??
Comment
Comment