> Gooood. I was affraid that you meant "POV community" as "POV world" which could
> change "clamped" sense a lot.

ehhhh :) no comment... :)
 
> Have you done some "unclamping" for radiosity code ? Have you some results ? Any
> patched version available ?

Nope.
I am writing my own GI renderer and studied radiosity/monte carlo/irradiance caching
over
years.... then tried to look how POV is doing that.

When I saw the GI code in POVRAY, I sat down and started to cry :)
Many bugs! Bugs meant by misunderstanding light theory and many nifty
"methods" of coping with "crossing 1's value".

I know the code is working, but is highly limited in some areas eg. light is not so
well
propagating in corridors, tunnels etc. due to many limits bound on GI values during
caching and mixing with diffuse coefficients - no matter how many GI bounces you
gave in rendering settings.

I think that it is the time to redesign radiosity code, there are so many new theories
and
algos now... somebody could boost POV in XXI century.

Post a reply to this message

"T.J.Viking" wrote:
> 
> [...]
> 
> I think that it is the time to redesign radiosity code, there are so many new
theories and
> algos now... somebody could boost POV in XXI century.

Very funny.

Instead of making 'wise' comments just get the POV-Ray source from

http://www.povray.org/download/

and implement a better radiosity function.  If you are as competent in
that matter as you pretend to be this should not be a problem.  If not i
suggest you either stop your complaints or support your critiques with
some proof.  This of course would require actually using POV-Ray.

Christoph

-- 
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 28 Feb. 2003 _____./\/^>_*_<^\/\.______

Post a reply to this message

"T.J.Viking" <vik### [at] bp-domarpl> wrote in message
news:3e646626$1@news.povray.org...

> I think that it is the time to redesign radiosity code, there are so many new
theories and
> algos now... somebody could boost POV in XXI century.

If you can provide a decent patch, I'm sure it will make it's way to megapov.
Once megapov gets enough features, it tends to become the standard
pov-executable for the majority of users.

Post a reply to this message

> > I think that it is the time to redesign radiosity code, there are so many new
theories and
> > algos now... somebody could boost POV in XXI century.
> Very funny.

Yup very funny indeed :)


> Instead of making 'wise' comments just get the POV-Ray source from

Being wise is not my mission...
 
> and implement a better radiosity function.  If you are as competent in
> that matter as you pretend to be this should not be a problem.  If not i
> suggest you either stop your complaints or support your critiques with
> some proof.  This of course would require actually using POV-Ray.

Yes I was, I am & I will (I hope) use POV :)
Your problems are not my problems, I can live with it how POV is working.

I do not understand one thing, why POV community is so touchy about any
complaints..... POV is marvelous, but as everything on the world can be better.

And one word to you guys..... go for a walk, and leave POV for a while... you are
going crazy
about you "preccious"

Post a reply to this message

"T.J.Viking" wrote:
> 
> [...]
> Your problems are not my problems [...]
> 
> I do not understand one thing, why POV community is so touchy about any
                                         ^^^^^^^^^
> complaints..... 

You gave the reason yourself.  Because it is a community.  Just making
complaints without supporting them with actual arguments and proofs is not
of any help.  Do you really think people actually using POV-Ray everyday
can't complain about its shortcomings themselves?  What you said clearly
places you outside the community.

I strongly suggest you reread my last post because following its
suggestions will almost surely guarantee you friendly replies to your
postings.  

Christoph

-- 
POV-Ray tutorials, include files, Sim-POV,
HCR-Edit and more: http://www.tu-bs.de/~y0013390/
Last updated 28 Feb. 2003 _____./\/^>_*_<^\/\.______

Post a reply to this message

> You gave the reason yourself.  Because it is a community.  Just making
> complaints without supporting them with actual arguments and proofs is not
> of any help.  Do you really think people actually using POV-Ray everyday
> can't complain about its shortcomings themselves?  What you said clearly
> places you outside the community.

I really appreciate what youve done to the community Chris,
but you simply not understanded my intentions...

My intention was to start talking about changes to the radiosity code.
Do not put that heavy work to one and only person... its undoable in
the current state of code - in my opinion most of the features rely on
structures used not only in radiosity code...
 
> I strongly suggest you reread my last post because following its
> suggestions will almost surely guarantee you friendly replies to your
> postings.  

Your suggest leads to nowhere...
Many people was using GI in POV for years and know their problems better
than me and you. Let them speak about it if you even matter about "community".
It is not communism it is more like democracy - let other people have their
opinions and needs.

The matter is open... let the people speak, then start implementing.

Post a reply to this message

On Tue, 4 Mar 2003 09:38:24 +0100, "T.J.Viking" <vik### [at] bp-domarpl> wrote:
> > Gooood. I was affraid that you meant "POV community" as "POV world" which could
> > change "clamped" sense a lot.
>
> ehhhh :) no comment... :)

Sorry. Your CV at http://news.povray.org/search/advanced/?s=Viking&a=1 is short
so I wasn't sure your intentions. The meaning of some recent threads made me sad
and I become sensitive.

> > Have you done some "unclamping" for radiosity code ? Have you some results ? Any
> > patched version available ?
>
> Nope.
> I am writing my own GI renderer and studied radiosity/monte carlo/irradiance caching
over
> years.... then tried to look how POV is doing that.
>
> When I saw the GI code in POVRAY, I sat down and started to cry :)
> Many bugs! Bugs meant by misunderstanding light theory and many nifty
> "methods" of coping with "crossing 1's value".

Can you refer to exact line in sources? Knowing what is broken can allow make it
better. Having more info MegaPOV can make those bugs "optional". Can you share
your knowledge and help us make it better ?

> I think that it is the time to redesign radiosity code, there are so many new
theories and
> algos now... somebody could boost POV in XXI century.

Tomku, zarówno zródla POV-Raya jak i MegaPOV sa publiczne, z checia
przetestujemy twoje propozycje. Zachecam do wypuszczenia patcha. Jesli tylko
jestes chetny do wspólpracy zapraszam do kontaktu ze mna: abx### [at] abxartpl :-)

ABX

Post a reply to this message

> Can you refer to exact line in sources? Knowing what is broken can allow make it
> better. Having more info MegaPOV can make those bugs "optional". Can you share
> your knowledge and help us make it better ?

Yes I will provide full list of "bad points" in code.
Where should I post it ? Which group would be the best for such discussion?

Post a reply to this message

On Tue, 4 Mar 2003 10:39:13 +0100, "T.J.Viking" <vik### [at] bp-domarpl> wrote:
> Your problems are not my problems, I can live with it how POV is working.

Wait, Tomek!

Did you said you have read the sources ? Did you said you have seen bugs there ?
Do you want to be parasite only ? We (community) give you application,
resources, contests, nearly on-line help. Please give us something too. POV-Ray
wasn't created in one week. Everyone bring something to it during last eleven
years. Having your post we have signal something is wrong. Writing what
*exactly* is wrong you can make time of repair short. Just complaining you did
not help us at all and we are still at the same place with the same real life
burdens and own current tasks opened.

ABX

Post a reply to this message

On Tue, 4 Mar 2003 12:25:08 +0100, "T.J.Viking" <vik### [at] bp-domarpl> wrote:
> Yes I will provide full list of "bad points" in code.
> Where should I post it ? Which group would be the best for such discussion?

I think:
- The povray.programming for current source code discussions.
- The povray.unofficial.patches for complete working changes.
- The povray.binaries.utilities for uploading files.

http://www.povray.org/resources/newsgroups/


ABX

Post a reply to this message