 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Possibly of interest to you:
https://www.martinjules.com/projects/single-project?id=5
- BW
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Bald Eagle" <cre### [at] netscape net> wrote:
> Possibly of interest to you:
>
> https://www.martinjules.com/projects/single-project?id=5
>
He apparently succeeded in writing his own parser for POV-ray (using Java?) He
mentioned elsewhere that he likes developing real-time rendering techniques;
it's difficult to tell from the video if he implemented that. (BTW, it looks
like he and his school mates(?) are still using v3.6).
It will be interesting to follow this work, to see if they eventually succeed in
coming up with a scheme to *directly* export an STL file (and not just for
mesh/mesh2 triangle-based objects...unless they figure out a way to turn
POV-ray's math-primitive objects and CSG into triangle meshes! *That* would be a
really important development.)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Kenneth" <kdw### [at] gmailcom> wrote:
> It will be interesting to follow this work,
Well, the idea was that if you really wanted to, you could contact him directly
and find out all sorts of things.
We can use all the help we can get regarding every aspect of POV-Ray's
development.
- BW
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hey Kenneth:
Have you seen this? (mesh projection camera)
https://wiki.povray.org/content/Reference:Camera
Max Distance
This is an optional floating-point value which, if greater than EPSILON (a very
small value used internally for comparisons with 0), will be used as the limit
for the length of any rays cast. Objects at a distance greater than this from
the ray origin will not be intersected by the ray.
The primary use for this parameter is to allow a mesh camera to 'probe' a scene
in order to determine whether or not a given location contains a visible object.
Two examples would be a camera that divides the scene into slices for use in 3d
printing or to generate an STL file, and a camera that divides the scene into
cubes to generate voxel information. In both cases, some external means of
processing the generated image into a useful form would be required.
- bw
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Bald Eagle" <cre### [at] netscapenet> wrote:
> Hey Kenneth:
>
> Have you seen this? (mesh projection camera)
> https://wiki.povray.org/content/Reference:Camera
>
I've used the mesh camera in the past-- actually just toyed with it-- but not
since I bought my 3-D printer and began learning about STL...so your reminder is
interesting news! Previously, I never really grasped the docs' info about
max_distance (and making 'slices' of a scene). I do need to go back and
investigate these possibilities...and to re-learn some of what I have probably
forgotten about the mesh camera <*sigh*>
Maybe I simply 're-invented the wheel' with my own object-slicing code
scheme here (?!)
Thanks! :-D
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Kenneth" <kdw### [at] gmailcom> wrote:
> I never really grasped the docs' info about
> max_distance (and making 'slices' of a scene).
Yes, that's the part that really caught my attention - there's no CSG, so I
wonder if there will be a significant speed-up.
Just mesh the screen with quads of triangles, and then rotate the mesh to flip
it up, and then scan down onto your object. Use the 0.1mm height of your print
for your max depth, and that should do it.
I'm also wondering if this would be a good way to do some of the
object-to-isosurface stuff that's been talked about, and also be used as a sort
of pseudo-trace() to get all the intersections of a ray.
I just saw it when researching other things (as always) and thought you would be
interested. :)
- BW
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
