|
|
Christopher James Huff <chr### [at] maccom> wrote in
news:chr### [at] netplexaussieorg
> with radiosity (it certainly does make sense with radiosity). An
> environment map would not be much faster than reflection, gives very
> imperfect results, takes more memory...no reason to use it, many
> reasons not to use it, so why add it?
the main purpose why I thinked of that - I'm creating small tutorail, and
I'm writting like - this is a sphere + normal that can be render in POV,
3dSMAX 4, etc. And compare it with this isosurface, that would not be so
easy to create in most scan-lines programs.
I wanted simmilar thing for reflection. This here is a real reflection that
we can create with POV, and here comes image of _same_ scene but with env-
map... hmmm how can I create env-map in POV ? This is the only 'category'
in with POV cannot simulate work of 'less complicate' renderers.
> Not a new idea, in fact, a pretty old one. Intersection point,
> distance, normals (raw and perturbed), ray origin and direction...
Is some path beeing wrriten currently for that ?
--
#macro g(U,V)(.4*abs(sin(9*sqrt(pow(x-U,2)+pow(y-V,2))))*pow(1-min(1,(sqrt(
pow(x-U,2)+pow(y-V,2))*.3)),2)+.9)#end#macro p(c)#if(c>1)#local l=mod(c,100
);g(2*div(l,10)-8,2*mod(l,10)-8)*p(div(c,100))#else 1#end#end light_source{
y 2}sphere{z*20 9pigment{function{p(26252423)*p(36455644)*p(66656463)}}}//M
Post a reply to this message
|
|