Page 1 of 1
simulens diff/freq values void after 100
Posted: Fri Sep 25, 2009 9:45 pm
by 3dtrialpractice
OK seems I narrowed the problem down.. and simulens is only unresponsive to diff/freq values over 100 on either diffraction or frequency.. Is this how is suposed to be.. becasue the values go up into the thousands?
Now the scatter value does affect the render look on values over 100.. even into the thousands the scatter works well.
(rendered from maya 2009x64plugin w multilight ON :intensity and color)
win xp64 -xeon 3ghz- 16gig RAM- 2xQuadroFX4600 15000rpm SAS drive
Re: simulens diff/freq values void after 100
Posted: Sat Sep 26, 2009 12:17 am
by 3dtrialpractice
Is there a situation that one would use/see a difference in setting either of those vaules(diff/freq) to the THOUSANDS? Becasue anything over 100 on either value doesnt change the look of the render..
Re: simulens diff/freq values void after 100
Posted: Sat Sep 26, 2009 4:13 am
by Mihai
Yes, you're right. The range of the sliders is off. Would it be better for max to be 100, or 1000 for more precise changes?
Re: simulens diff/freq values void after 100
Posted: Sat Sep 26, 2009 8:03 pm
by 3dtrialpractice
ohh good idea.. to set it to work with 0-1000 for precision..
thank you for your attention I am very happy v2 came out to us!
Re: simulens diff/freq values void after 100
Posted: Mon Sep 28, 2009 11:35 pm
by 3dtrialpractice
acctually.. now that i think about it.. maybe for scripting and prompt rendering its just good enough to have 0-100
Re: simulens diff/freq values void after 100
Posted: Tue Sep 29, 2009 1:20 am
by rusteberg
Mihai wrote:Yes, you're right. The range of the sliders is off. Would it be better for max to be 100, or 1000 for more precise changes?
i noticed the same thing... i'd have to vote for precision........
Re: simulens diff/freq values void after 100
Posted: Wed Sep 30, 2009 2:27 am
by Bubbaloo
What is the cutoff? What if I want a ridiculous amount of Simulens? It should be possible.
Re: simulens diff/freq values void after 100
Posted: Fri Mar 05, 2010 10:54 pm
by tom
Fixed in 2.0.2