aeronoise shouldn't work horribly with mlt, what you would end up doing would be to break up the image into many parts and render each seperatly and the aeronoise just chooses the region where the image should be rendered. it would be a little complicated to set up though.

whatever catches my fancy at that moment: lots of interpol and thrills for organic, snowden and all my english indie rock for assorted stuff, and chemical brothers for robotics.

i got onto the site for like 4 seconds and noticed that there were already over 12 posts in the forum. how are people posting in the forum if the site's only been up for a day or two

indigo is free, it's sdk costs money. thus indigo is not the product, the sdk is. lux doesnt have an sdk for connecting with software and thus it is not really a competitor. plus, the use of one does not prevent the use of the other, i often use open source software and it's competitors in my stuff.

well, never said it was perfect. its not realy a profesional renderer anyway, i want to open source it more for people who want to start to write there own renderers rather than for development or for artistic use.

pretty much. better question would be, why not another renderer? the more renderers there are the greater the competition there is to write a better renderer that more people can use that will render faster. the only possible result of this is more better renderers so people will be able to chose fr...

woo, finaly, will we have a forum soon?

give it a couple of weeks and i'll see what i have to do, if any body knows the subtleties of this issue, please do speak up. new pic at 400 mutations, rendered overnight. i dont know why its so grainy, but at least it works. maybe rendering it over the weekend will serve it better. http://i23.tinyp...

as it turned out, that was not the issue at all. i was wasting my time playing with the path tracing classes as the problem was in the metropolis class and in how Fresnel worked. its now fixed and in theory a bit faster. i might release the source soon, apparently if i copywriter it or something alo...

problem with amd is not there speed, its the actual technology that goes into them. amd doesnt have the same fan control and heat control that intel does and while it starts out faster, it looses speed over time do to frequent overheating.

are they object oriented, because object orientation becomes a big issue in ray tracing. it can be done without it, but its very hard to do and becomes non extensible.

amd does not have nearly the same quality of technology that intel does. check out dell's small buisness deal vostros for some nice bang for your buck. plus, if you go intel+ nvidia, you get the option of using cuda which will accelerate many renderers in the future.

right, i have no idea what you mean by unterstud. if you mean by parimeters set in the file, no they arent done like that yet. right now i have an interface for setting parimeters. if you mean file format for the scene- there is a .tlr which is basicaly a txt which holds a slightly modified .obj fil...

i basicaly got my raytracer working one year after having started learning to program (alot less actualy) i only started learning to program about this time last year, and attempted my raytracer right around march. i realy only got it working about may though, so i dont know. it realy depends on wel...

the majority of the problem seems to lie it two areas A: the equation i was using for the direct lighting was double dd = d.dot(d); double mm = (atHit.now.normal.dot(d)) * - (lumpatch.normal.dot(d)) * (1 / (dd*dd* lumpatch.time)); where d was not normalized. fixed it now reads: Vector3 df=d.normaliz...