POV-Ray : Newsgroups : povray.general : A little help about old vers. : Re: A little help about old vers. Server Time
18 Jun 2025 18:50:57 EDT (-0400)
  Re: A little help about old vers.  
From: GioSeregni
Date: 18 Jun 2025 12:10:00
Message: <web.6852e454ce24a8bbeeec206c59126100@news.povray.org>
"Bald Eagle" <cre### [at] netscapenet> wrote:
> "GioSeregni" <gms### [at] hotmailcom> wrote:
>
> > General algorithms are no good in my opinion.
> > They are recursive and have unintelligent ways.
> > They consume memory.
> > They exaggerate in the points that are already rich and perhaps are deficient in
> > the points that need it most.
>
> What you could do is test the distance between points, and points that are far
> apart can get refined, and points that are close together can get skipped.
>
> However, I'd suggest making it more sophisticated than that - test the curvature
> along some distance on the surface.  Flat areas get skipped, and highly curved
> areas get refined.   Find some way to appropriately weight the curvature vs
> distance metrics.
>
> Unnecessarily subdivided flat faces could be simplified into a single quad.
>
> Not easy work - very tedious.  But well commented code and a flowchart of the
> logic would help in future development.
>
> - BE

You're right, but my goal is more modest. I would leave the rendering engine the
option to adapt the quality to the distance.
Second Life did it many years ago, and I think that more or less all 3D
rendering programs do it.
I don't actually know, in advance, when I create an object for my library, at
what distance it will be seen. I use the library to obtain landscape contexts
where things are as light as possible.
We got into this discussion because jr, rightly, about the BMW, said that
certain parts were too simplified. Even with the smoothing of the triangles. For
this reason, for me it is important to be able to keep the weight of the object
light, but also to have a tool for fine-tuning the critical points.
Implementing mesh enrichment is a good starting point in my opinion. If I want,
when well tested, I could also make it recursive on the entire model.
But it must generate the model. The method we saw is more of a feature of the
render engine, it is volatile. In my opinion it should be addressed at the pov
ray engine level... like "remeshing <SplitValue, WPdistance, etc etc> "


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.