|
![](/i/fill.gif) |
Christoph Hormann <chr### [at] gmx de> wrote in
news:3DB1D68A.499B34D2@gmx.de
> - from what you write in the documentation about the collisions i
> conclude you have not solved the 'particles penetrating the
> surface'-problem. You might try function based environments like i'm
> using for my mechanics simulations.
Hellow,
little OT suggestion - how about changing POV work philosofy to get a big
hmm calculations utility, that can work togeather with external programs.
Now schemat is like :
* pov parses scene
* pov is doing some pre-calculations like photons
* pov is rendering scene lines 0..height
I suggest something like :
a) pov starts and :
b) Now pov works as hmm some kind of server (not web server ofcourse :P)
he keeps in memory all nesesary data, and response to following possible
requests :
* commands
- load and parse scene "..."
- unload current scene (dealloc)
- quit
* render
- render pixel
- render sample (for AA)
- render line
- render area
* scene phisics informations
- is point (x,y,z) inside object called "..."
- intersection (x,y,z) in direction (X,Y,Z) of object "..."
- normal of object "..." in point (x,y,z)
- color of object in (x,y,z)
- color due to diffuse
- ... refelction
- photons
- etc
From technical side, possible comunication pipes could be i.e.:
- DDL sharing memory in Windows
- pipes in Unix/Linux ? (i'm newbie in this topic)
- files (in any OS, but it may be slow, unless files are i.e. in RAM disc)
- some TCP/IP protocol ? it would be realy greate and will allow very nice
cluster rendering
Possible usage :
- cluster rendering
- additional editors / front-ends
- external programs like phisicla smulations
--
#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
|
![](/i/fill.gif) |