I can confirm this is a bug in the CSG code, which is now fixed. thanks for the report! -- Chris
Post a reply to this message