The current bounding related options:

+-b  bounding
+-bm bounding_method  (1|2)
+-mb bounding_threshold
      bsp_baseaccesscost
      bsp_childaccesscost
      bsp_isectcost
      bsp_maxdepth
      bsp_misschance
+-ur remove_bounds
+-su split_unions


become:

+-b      bounding                     = on|off
+-bm_    bounding_method              = string  valueonly
            (slab|bsp)
+-bt     bounding_threshold           = integer valueonly
+-bbbac  bounding_bsp_baseaccesscost  = float   valueonly
+-bbcac  bounding_bsp_childaccesscost = float   valueonly
+-bbic   bounding_bsp_isectcost       = float   valueonly
+-bbmd   bounding_bsp_maxdepth        = integer valueonly
+-bbmc   bounding_bsp_misschance      = float   valueonly
+-bruc   bounding_remove_user_coded   = on|off
+-bsu    bounding_split_unions        = on|off

Here mostly setting up for the future as I'd like to try some additional
bounding methods including a modification of the current bsp option.

There is some odd merge{} related bounding code which is to my eye too 
quick to push all the shapes in a merge into the infinite object bucket, 
but maybe I don't understand what is really happening or why.

The yuqk bounding is already somewhat different than that in the 
official code. It uses 64 bit floats over 32 bit floats for one - and
it restores the v3.6 and prior versions ability to turn bounding 
completely off which was lost (or removed?) in the v3.7 or v3.8 official 
code. FWIW, I guess.

Code wise the parsing is mostly there, but nothing is wired up.

Bill P.

Post a reply to this message