dave davidson

you have to model the lights as this engine isnt like the other engines once you have modeled the light source you have to give it a maxwell emitter material and then set the light up with the wattage etc yourself. i think they are doing light conversion in some plugins but that will only work on the default 3d apps lights (but im sure you will have to tweak the settings after it has converted to get them right )

try a cube as an emitter inside an open cone ( with the normals facing inwards) that is reflective to act as a spot light and aim it at the objects, this will give you caustics that will show up fast

"thanks for the replies -- hey Dave, have you seen better render-times out of fry? or at least less noisy images after a 24hrs." in many many instances fry is faster ( atleast for me that is ) i have very rarely ever had to do a 24hr+ render. hope that helps

ive used both and from what i know is i can get equally if not better quality out of fryrender as i can maxwell. with a better workflow inside cinema 4d so fryrender to me is a bonus to my rendering experience IMHO. thats just my thoughts on the matter. and like they said as the better users with talent (not that there arent any there now) come over and start using it you will see better renderings just like you did when they started using maxwell. As for when the demo is coming well "when its done" springs to mind your lucky you dont have to wait until version 1 is out before trying it, so its not all bad having to wait a little longer is it, plus as was stated before once its demo there will be no cheap purchase price.

quoted for agreement.

quoted for agreement this isnt a new thing at all :/

hmm "waiting for the right moment to make them public" LOL like when we hand over the money they make them public. nah that dont sound right. yeah good idea to hold onto them till the moment is right

thats the spirit

lol bless

"I read an unofficial statement by another user over there that the "beta look" was back. As I recall, at one time we "Beta Lovers" were told that the "beta look" was wrong and bad and that we were wrong and bad for wanting it back." quoted for agreement.

check the file size of the downloaded package mine always reads around the 22mb so its only getting half of it before it bombs out

im sure i can, just give me a moment

i play with both too and will continue to do so and when vray comes to c4d i may have to play with that i personally like using as many engines as i can and then use each one for their own strengths

doing a happy dance is all well and good if its for something they are about to get, this is not the case here is it. people are not getting displacement in 1.5 and who knows when the next version will come out, we all know how long this one took. thread is locked over there so atleast they cant continue to talk about something they arent even getting :/ and playing catch up is indeed correct, saying it is the next level of displacement is interesting "always one step ahead" sort of thing but they havent got it working and its been a long time hasnt it so yes lets hope that when it does come its a fully working next level super duper better than everyone else displacement, but until then i think they shouldnt have announced that one we aint getting it and two showing pictures of something that is going to change

well i still cant get over the thread discussing displacement and render times etc BUT WE AINT GETTING DISPLACEMENT so why talk about it and whats the point discussing the render times etc if it doesn't work right because if it did it would be in 1.5. i,m confused maybe i should start a thread about some other feature we ain't getting, but maybe one day we might :/ they need to be talking about what we are getting in 1.5 grrr