So if I was to post a scene that uses multilight lets say 4 emitters how will you guys know what intensity to move the bars to for each emitter?
Great Service by the way will be very handy!!
Well we don't move the bars at allTea_Bag wrote:Hi Fred,
So if I was to post a scene that uses multilight lets say 4 emitters how will you guys know what intensity to move the bars to for each emitter?
Great Service by the way will be very handy!!
You get the final merged MXI back and you can do whatever you want with it.Hi Mattia,Mattia Sullini wrote:Aaahh...now i can take jobs even for tomorrow....all the time i have to consider for finishing a project is the pure worktime! And the clients pay for it as a part of my special HURRY! fee. Addictive.
Today i tried to submit the multilight and from the .mxi they sent me back i was able to finetune all those effetcs that at low SL do not appear, like blurry reflections, the precise effect of frosties and anysotropy. It increased the calculation time, indeed, but is definitively useful.
PS. Uh,hey Fred, having uploaded my 15th project to your renderfarm i could define myself as a veteran, then i would have a little suggestion for you. When today i have started uploading the .vum, i was scared by the fact that maybe (i didnt) i had written 250mins instead of 25...I guess it would be useful a kind of recap of project parameters right before the upload, expecially if you have to go trough the subscription fee payment process.
I don't think we will add a recap as it is easy enough to check what you are typing before validating... Anyway if such a thing happens just send us an e-mail. If the project is still in the queue we can modify the asked render time limit in real time, and if it is already running we can stop it (but we will do so only in the case of a real emergency, and if it is at the beginning of the render).
for fast renders / test renders in low or medium resolution - while working on a project for instance.Well it was not very representative of typical projects we have to render, which are much more complex. Also we have something very precise now in the cost estimator (http://www.ranchcomputing.com/M_estimateur_cout_uk.php). You just have to look at the list, and if you have one of those systems, you know instantly the SL that the Ranch would reach in the same amount of time. For instance, if you have a Q6600 and you reach SL in X minutes, you know that the Ranch would reach SL+8.5 in X minutes too. That makes comparisons very easy no?mashium123 wrote:Hi Fred,
I wonder, why you don't use the benchwell.com-scene anymore, wich you were using with your prior 160 GHz.
(I believe, it s.th. about 15min. for SL20 or such...)
That was very a helpful. Because there is a list of systems, which we could use as reference and such... I wished you would use this benchwell.com-scene again.
Thx.
Yes, but you can inverse the reasoning (deducing time from SL), as explained in the third paragraph. Anyway, I guess I could re-run the Benchwell at SL20 if that makes you happymashium123 wrote:Hmm, well, if I looked at the Ranch as one (super-)computer, I would like to know in what time this computer is able to reach a given SL (compared to other computers) and not what additional (+)SL this computer is able to reach within a given time.
That would be easier to compare, imo.
You know, I tought it's about reaching the given goal (SL) in minimum time with the help of power, and not pushing that goal to a maximum distance.
But, hey... it's just a thought...
I'll try to do that tomorrow.
- By Matteo Villa
Other rendering engines are evolving day by day, m[…]
- By Mark Bell