William F Pokorny <ano### [at] anonymousorg> wrote:
>
> Fixed case with cutaway_textures in difference{} block where if first
> shape was not textured, it was being left with no texture during the
> rendering phase.  Results in such cases now align with intersection -
> and difference{} is really implemented as an intersection with all but
> the first object inverted.
>

[Running Windows 10]
I am currently working on an elaborate 'object-slicing' scene that makes use of
cutaway_textures and a #default finish{...} statement. I have attached a
simplified version of the scene; would you mind running it in your current yuqk
fork? I would be curious to know if the scene produces what I see, given your
updates to cutaway_textures (and possibly both the specified #default behavior
as well as your current behind-the-scenes #defaults).

It requires a *square* render, at any resolution you choose. I designed  the
various textures and finishes-- and the #default finish-- after experimenting to
find the best combinations; I hope they still work correctly in your
fork...especially the un-textured intersection box. On my end, the results are
consistent in both official v3.7.0 and 3.8 beta 1.

There are 2 switches in the scene , with 4 possible permutations. This is what I
see:

#declare WHICH_TEST_ = 1;
#declare USE_CUTAWAY_TEXTURES_ = off;
a totally white object inside a rectangular red box, against black

#declare WHICH_TEST_ = 1;
#declare USE_CUTAWAY_TEXTURES_ = on;
a yellow and blue object (with a slight red tint), inside a rectangular red box,
against black

#declare WHICH_TEST_ = 2;
#declare USE_CUTAWAY_TEXTURES_ = off;
a totally white object against black

#declare WHICH_TEST_ = 2;
#declare USE_CUTAWAY_TEXTURES_ = on;
a yellow and blue object against black

Post a reply to this message

Attachments:
Download 'cutaway_textures_test_for_wp_from_kw_1_2024.pov.txt' (3 KB)