On 06/03/2023 15:12, Bald Eagle wrote:
Hi, Bill.

> Just to make clear what the mechanism of the Insert Menu is, it's just a
> directory of text files that copy-pasted into your scene.
Thanks for info, I had a look at this structure, it's simple, will be
easy to modify.

> Some of the ideas you have would be great but better suited for either include
> files or as example scenes.
No doubt, we can include in menu only code snippets, that use data from
'inc's.

> Certainly taking a mesh and placing it into a well-composed scene, predominately
> governed by the camera location, and giving it 3-point lighting, an HDRI
> lighting sphere, and good radiosity settings would be fairly easy to do and
> really provide instant guidance for even the newest of users.
This is exactly what I would like to have, still looking for good set of
studio environments. Prepare such environment is not easy task for
newcomer.

> There certainly are a lot of little tricks like this, scattered throughout the
> forum and the documentation.  Since the list is potentially endless, such things
> might best be collected into a zip archive with subdirectories dedicated to the
> larger/more complicated ideas like the animations.
Having such cookbook will help a lot to start working with POV quickly
and smoothly, saving a time on digging in manuals.
Something like best practice ...

> We could collectively write an entire book on CSG, and that topic probably
> deserved its own document complete with references to CG texts websites, and
> how-to videos.
I believe it will be demanded material for those, who wants to study CG
more deeply. Not so many people knows what CSG is, because most of the
scenes are made from polys now.

> Yes, we are a bit short on meshes, and that could be a good idea for another zip
> archive.    Part of the appeal of primitives and procedural scenes is that they
> are SMALL, and don't contribute much to the overall size of the POV-Ray
> distribution.  Whereas my recent "unrolling" of the vase generated two 28 MB
> ASCII CSV files.
I said 'low-poly', while mean small object, also constructed from POV
native solids too, sorry for misunderstanding. As an example I've
attached few small poly-objects fetched from my standard Z-Brush
installation. Not sure about licensing, but, suppose, it can be checked.
If publishing of them is correct under POV license, we can look at them
as a seed of future prefabs library. Just let me know if you want more
of them.

> The ideas are indeed endless, and the key is to thoughtfully create the required
> text files that strike a good balance between doing enough to suggest further
> variations and applications, but not so much that it becomes too busy and
> confusing.
Exactly, but at present time for the first look of a new user, POV is a
complicated tool for programmers, not for end-user. The idea is to
introduce it as a simple toy, to help users to make a first steps, with
sequential increasing complexity.

> For example: I had a project going to provide a working code example for every
> single
keyword:http://news.povray.org/povray.binaries.misc/thread/%3Cweb.604598da4b83c70f1f9dae300%40news.povray.org%3E/
Interesting, I will look at it.
--
YB

Post a reply to this message

Attachments:
Download 'prefabs.png' (35 KB) Download 'prefabs_obj.zip' (50 KB) Download 'prefabs_pov.zip' (56 KB)

Preview of image 'prefabs.png'