narrationsd

Walt, just to be complete here, I did try the recommended method again, this time with the Bluetooth mouse.
Indeed, it works fine this way. So the issue definitely was with the not-always-complete-in-details functioning of the laptop trackpad, which is still that way after about ten years...this one was a good investment....
Noticed there are indeed a lot of apps available for dragging over Shortcuts in that magic folder; could be useful. And yes, I do appreciate the distinction between Store and non-Store MSIX; just never enjoy these unnecessary MS complications
Best, thanks again,, and hope this helps someone else.
Clive

Thanks, @walt.farrell.
Truth is that I tried that method originally at first, but on my very up-to-date and maintained Win10, the drag-drop maneuver absolutely refused to bring the icon shortcut over. Hence the suggested, which can at least be a backstop.
It occurs to me in writing this that the issue might be that I tried this using the trackpad on my laptop. There are a few other places, usually in graphic programs, where similar drags aren't accomplished, though usually where a modifier key is involved.
When I'm back to it, I'll try with a Bluetooth mouse, just to see. But this is a very standard laptop driver etc., so it may be well to offer the alternate method in the official suggestion, no?
Cheers,
Clive

Walt, thank you, yes, I purchased a Universal license the day of the announcement, and successfully installed on iPad and Win10, so far, so great.

And today, when I try it once again, the already-installed Beta activated successfully, runs fine though it asked me to verify a second time, to  get the downloadable content able to access.
I appreciate your help here over the long term, as I've had v1 licensing also for a number of years, and contributed here on betas.
What I surmise is according to observed, as follows:
- a few days ago, I got an email announcement of the beta v2, from following the proper place in the forumt
- this announcement linked to a posting here, which didn't exist. Nothing existed in the area, and this lasted if I remember for more than a day
- eventually a posting showed up -- not the referenced one -- and gave download details. I downloaded and installed -- wherever those installs are going...
- this is where I came up against the absolute refusal to activate, with perfectly good  old password, and when I changed my store login password, just to see. I could always go right into the store itself. 
- that's whenI made the post above, which seemed this morning to have been disappeared from the beta forum...hmm.
- this morning, Saturday here in the Americas, I had a look at the forum, and could see your reply because a notification lit...
- to prepare to reply, I wound up the beta again, with vpn turned off as too many sites don't like those, as I had originally also, and this time the activation occurred immediately and smoothly, if needing somehow to be done twice, as above.
- the beta also runs fine, with a lot of improvements listed to be appreciated, as always
My conclusion is that whatever was horsed up to cause the original posting not to appear, or led to its being taken down, was still horsed up in ways that caused the activation server not to work, and this lasted long enough for me to run into it. 
Eventually, this has apparently been unwound. Maybe my posting will reappear as well, or otherwise I'll attempt to DM you with the above
Best,
Clive
p.s. if you read this in an email notification, I've edited to clarify one or two points, and to remove the impression I had that my original post had been disappeared -- instead, it was as a reply to Patrick's announcement, and thus not showing in the forum posts listing -- quite rightly

Walt, thank you, yes, I purchased a Universal license the day of the announcement, and successfully installed on iPad and Win10, so far, so great.

And today, when I try it once again, the already-installed Beta activated successfully, runs fine though it asked me to verify a second time, to  get the downloadable content able to access.
I appreciate your help here over the long term, as I've had v1 licensing also for a number of years, and contributed here on betas.
What I surmise is according to observed, as follows:
- a few days ago, I got an email announcement of the beta v2, from following the proper place in the forumt
- this announcement linked to a posting here, which didn't exist. Nothing existed in the area, and this lasted if I remember for more than a day
- eventually a posting showed up -- not the referenced one -- and gave download details. I downloaded and installed -- wherever those installs are going...
- this is where I came up against the absolute refusal to activate, with perfectly good  old password, and when I changed my store login password, just to see. I could always go right into the store itself. 
- that's whenI made the post above, which seemed this morning to have been disappeared from the beta forum...hmm.
- this morning, Saturday here in the Americas, I had a look at the forum, and could see your reply because a notification lit...
- to prepare to reply, I wound up the beta again, with vpn turned off as too many sites don't like those, as I had originally also, and this time the activation occurred immediately and smoothly, if needing somehow to be done twice, as above.
- the beta also runs fine, with a lot of improvements listed to be appreciated, as always
My conclusion is that whatever was horsed up to cause the original posting not to appear, or led to its being taken down, was still horsed up in ways that caused the activation server not to work, and this lasted long enough for me to run into it. 
Eventually, this has apparently been unwound. Maybe my posting will reappear as well, or otherwise I'll attempt to DM you with the above
Best,
Clive
p.s. if you read this in an email notification, I've edited to clarify one or two points, and to remove the impression I had that my original post had been disappeared -- instead, it was as a reply to Patrick's announcement, and thus not showing in the forum posts listing -- quite rightly

@Mark Ingram
I understand there's no news about the many crash reports posted previously (here, here, and here), so I guess I can't expect much in that territory.
That said, if it might be of any help, I tested 1.10.3.1188, and I can confirm the same crashes once again (DMP files, and logs attached).
As usual, the beta seems to be working fine with the acceleration off, though the latest official 1.9.2.1035 works also with the acceleration on.
While it's possible to use the newest releases with the acceleration off, the difference is quite significant in terms of performance.
You have provided a great software, and I still hope there's a way for the devs to figure this out. It's difficult to go back
For the record, the other software I use with no issues regarding GPU acceleration are:
Cinema 4D R21 with Redshift, Blender 3D 2.93.5, and 3.0 alpha, Davinci Resolve Studio, Fusion Studio, Quixel Mixer, Quadspinner Gaea, Diffractor.
Edit: I forgot to add that the latest official Affinity Designer, and Affinity Publisher work fine with the hardware acceleration on.
As for my system specs:
Computer: Alienware Area-51 R3 CPU: AMD Ryzen Threadripper 1950X (ThreadRipper, ZP-B1) 3400 MHz (34.00x100.0) @ 4116 MHz (41.25x99.8) Motherboard: Alienware 0XF4NJ BIOS: 1.2.0, 07/24/2020 Chipset: AMD X399 (Promontory) Memory: 32768 MBytes @ 1064 MHz, 15-15-15-36 - 16384 MB PC21300 DDR4 SDRAM - Corsair CMK32GX4M2A2666C16 - 16384 MB PC21300 DDR4 SDRAM - Corsair CMK32GX4M2A2666C16 Graphics: ASUS TURBO GTX 1080 Ti NVIDIA GeForce GTX 1080 Ti, 11264 MB GDDR5X SDRAM Graphics: DELL GeForce GTX 1080 Ti NVIDIA GeForce GTX 1080 Ti, 11264 MB GDDR5X SDRAM Drive: Samsung SSD 860 QVO 2TB, 1953.5 GB, Serial ATA 6Gb/s @ 6Gb/s Drive: KXG50ZNV512G NVMe TOSHIBA 512GB, 500.1 GB, NVMe Drive: HL-DT-ST DVD+-RW GS40N, DVD+R DL Sound: NVIDIA GP102 - High Definition Audio Controller Sound: AMD Zen - HD Audio Controller Sound: NVIDIA GP102 - High Definition Audio Controller Network: Qualcomm/Atheros E2500 PCI-E Gigabit Ethernet Controller Network: Killer Wireless-n/a/ac 1535 Wireless Network Adapter Network: Qualcomm/Atheros E2500 PCI-E Gigabit Ethernet Controller OS: Microsoft Windows 10 Professional (x64) Build 19043.1288 (21H1)  
 
reports.zip attachments.zip

Click here to download the latest beta Currently there is no beta more recent than the 1.10.4 release
Status: Customer Beta
Purpose: Fixes
Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store

As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. 

If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum.
Fixed Refine Selection as New Layer with Mask preventing rendering of Artboards Fixed Brush Hardness changing when swapping tools Fixed Live Filters with Radius or Distance spuriously changing the Azimuth anticlockwise Previous release notes

Click here to download the latest beta
Status: Customer Beta
Purpose: Fixes
Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store

As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. 

If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum.
Changes
Fixed Refine Selection as New Layer with Mask preventing rendering of Artboards Fixed Brush Hardness changing when swapping tools Previous release notes

Status: Beta
Purpose: Fixes
Requirements: Purchased Affinity Publisher
Windows Store: Not Submitted
Download: Download
Auto-update: Not Available
---
We are pleased to announce that Affinity Publisher Customer Beta 1.10.2.1187 is now available as a download from the link above.
If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
This beta is an incremental update to the 1.10.1 version recently released to all customers. We recommend that you use this beta in preference to the release version if you are affected by any of the issues listed below.
---
Fixed document with 'Save History' failing to save after promoting a Group to a Layer. Fixed PSD import of Linear Burn blend mode being imported as Multiply. Vector import (SVG, IDML etc) can be created at incorrect size. Space incorrectly gets added to text on clipboard if you double click a word to highlight. Fixed bug when deleting multiple pinned objects at the same time. Other assorted small fixes. Previous Beta Release Notes
---
To be notified about all future Windows beta updates, please follow this notification thread 
To be notified when this Publisher update comes out of beta and is fully released to all Publisher customers, please follow this thread

Status: Beta
Purpose: Compatibility / Fixes
Requirements: Purchased Affinity Publisher
Windows Store: Not Submitted
Download: Download
Auto-update: Not Available
---
We are pleased to announce that Affinity Publisher Customer Beta 1.10.2.1156 is now available as a download from the link above.
If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
This beta is an incremental update to the 1.10.1 version recently released to all customers. We recommend that you use this beta in preference to the release version if you are affected by any of the issues listed below.
---
Issues with the Affinity Web Services 'My Account' Page 'Replace' in the Resource Manager converts Linked to Embedded Invalid URL hyperlinks prevent PDF export Other assorted minor fixes Affinity Publisher 1.10.1 Release Notes
---
To be notified about all future Windows beta updates, please follow this notification thread 
To be notified when this Publisher update comes out of beta and is fully released to all Publisher customers, please follow this thread

Click here to download the latest beta
Status: Customer Beta
Purpose: Fixes
Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store

As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. 

If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum.
Fixed Adjustment enclosures which affect alpha (curves, levels) not working Fixed problem when pasting raster nodes from one document to another with a different format Fixed adjustment histograms Fixed crash when adding raster formats to Astrophotography Lights Previous release notes

Click here to download the latest beta
Status: Customer Beta
Purpose: Fixes
Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store

As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. 

If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum.
Changes
Added 'Select Parent', 'Select Top', and 'Select Bottom' to main menu Changed behaviour of Select All when Edit All Layers is disabled - if you’re inside a group, it will now Select All within the group Fixed PDF passthrough getting rasterised if vector cropped  Previous release notes

Status: Beta
Purpose: Fixes and Improvements
Requirements: Purchased Affinity Publisher
Windows Store: Not Submitted
Download: Download
Auto-update: Not Available
---
We are pleased to announce that Affinity Publisher Customer Beta 1.10.0.1085 is now available as a download from the link above.
If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
Due to current and anticipated changes to help with performance issues this version is now 1.10.0 and replaces the previous 1.9.4 beta. All previous changes from 1.9.4 have been rolled into this beta.
As such, we strongly recommend that you do not use this beta for real work as data could be lost and the files you save are not guaranteed to open in previous / future versions of Affinity Designer.
---
Text
- Added Emoji support
- Improved Windows IME support for Chinese / Japanese text entry
Import / Export
- IDML Import - fixes for specific documents
- IDML Import - improved text style grouping and added import of keyboard shortcuts
- SVG Import - Parser improvements for whitespace handling
- SVG Export - Fix for export of stretched text when transforms are flattened
- RTF Import - Fixed specific crash if line breaks occurred in the vicinity of ligatures
- RTF Export - improved support for Unicode characters above 64k
- RTF Export - wasn't closing small caps correctly
Resources
- Improved performance of Resource Manager for documents containing of placed documents
- Placing an embedded document was incorrectly favouring any currently placed instance over the source file
- EPS files can now be 'Made Linked' in Resource Manager if the original source file is present
---
To be notified about all future Windows beta updates, please follow this notification thread 
To be notified when this Publisher update comes out of beta and is fully released to all Publisher customers, please follow this thread

Click here to download the latest beta
Status: Customer Beta
Purpose: Fixes
Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store

As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. 

If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum.
Changes
Improved linked documents to try to restore the correct artboard after a linked document has been modified Improved IME text editing Improved support for some lesser used Unicode characters Added Emoji support Fixed SVG export not exporting stretched text correctly when transforms are flattened Fixed SVG import to allow whitespace between "translate" and the following open bracket Fixed RTF export to close small caps correctly Fixed placing an embedded file incorrectly favouring the edited one in memory and not the source file used Previous release notes

Click here to download the latest beta
Status: Customer Beta
Purpose: Fixes
Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store

As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. 

If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum.
Allow simultaneous stacking of astro images for different filters  Fixed Info Panel not updating properly after opening images Improved Astrophotography to treat calibration masters from iTelescope the same as files from a camera (i.e. the bias is not already subtracted from the master dark) Improved Astrophotography to ignore damaged FITS files Improved Astrophotography for master calibration images created with Maxim DL by iTelescope Fixed Monochromatic Icons not affecting Adjustments Panel  Improved IME text editing Improved support for some lesser used Unicode characters Added Emoji support Fixed SVG export not exporting stretched text correctly when transforms are flattened Fixed SVG import to allow whitespace between "translate" and the following open bracket Fixed RTF export to close small caps correctly Fixed placing an embedded file incorrectly favouring the edited one in memory and not the source file used Previous release notes

Hi Mark, read your reply now a couple of beta versions back, in short order.
Impressive work by you guys.  Now, about links and CDNs...
- The CDN move really works. It was able to saturate a decent cable internet (is there such a thing...)
with peaks of up to 50Mbit/sec, in California.  This is great, and things even the size of Affinity updates arrive rapidly.
- the links. I clicked today first on the Publisher update. Bingo, took right off downloading as expected
  Then I tried here, for Photo.  As before, no joy. I had to right-click-open-in-tab, to get it
  What's the difference?  The Publisher link is https, and the Photo one still isn't
We are likely big boys and girls here amongst the betas, and can figure this out,
but it doesn't feel good, or of the enormous design, quality, and advances level we know of Affinity
Don't mean the loud pedal, just saying a feeling, and with a smile. Can't forget all the things you guys do do, either,
as you can see 

Best,
Clive

Just to be sure and to maybe make thing easier.. you know you can make text follow a path, right? So you can make it follow a curve for example, or a shape. Warping goes a lot further than just making it follow a path, I know but if you didn't know this yet then maybe it solves, or lessens the issue you have.

Keep watching this space 🙂

Juat downloading the release candidate for today, but I tried out the 603 Beta a few days ago on a reasonably complex InDesign idml file which I had done before, and this time it imported rather perfectly.
This is a great improvement from early versions, as appreciated as they were.
The document has framed local layouts, images with captions, Asian language segments, multiple sections, and lots of details like hyphenations which had thrown text layout significantly off originally.
The text layout decisioning now, while perhaps not quite up to Adobe's long-in-experience parapgraph engine a few places possibly, was just fine. Any remaining desires can be easily adjusted.
I'm no professional printing expert, but I think you have been doing a marvelous job, there in Nottingham and from whomever may also be contributing.

Juat downloading the release candidate for today, but I tried out the 603 Beta a few days ago on a reasonably complex InDesign idml file which I had done before, and this time it imported rather perfectly.
This is a great improvement from early versions, as appreciated as they were.
The document has framed local layouts, images with captions, Asian language segments, multiple sections, and lots of details like hyphenations which had thrown text layout significantly off originally.
The text layout decisioning now, while perhaps not quite up to Adobe's long-in-experience parapgraph engine a few places possibly, was just fine. Any remaining desires can be easily adjusted.
I'm no professional printing expert, but I think you have been doing a marvelous job, there in Nottingham and from whomever may also be contributing.

Juat downloading the release candidate for today, but I tried out the 603 Beta a few days ago on a reasonably complex InDesign idml file which I had done before, and this time it imported rather perfectly.
This is a great improvement from early versions, as appreciated as they were.
The document has framed local layouts, images with captions, Asian language segments, multiple sections, and lots of details like hyphenations which had thrown text layout significantly off originally.
The text layout decisioning now, while perhaps not quite up to Adobe's long-in-experience parapgraph engine a few places possibly, was just fine. Any remaining desires can be easily adjusted.
I'm no professional printing expert, but I think you have been doing a marvelous job, there in Nottingham and from whomever may also be contributing.

Juat downloading the release candidate for today, but I tried out the 603 Beta a few days ago on a reasonably complex InDesign idml file which I had done before, and this time it imported rather perfectly.
This is a great improvement from early versions, as appreciated as they were.
The document has framed local layouts, images with captions, Asian language segments, multiple sections, and lots of details like hyphenations which had thrown text layout significantly off originally.
The text layout decisioning now, while perhaps not quite up to Adobe's long-in-experience parapgraph engine a few places possibly, was just fine. Any remaining desires can be easily adjusted.
I'm no professional printing expert, but I think you have been doing a marvelous job, there in Nottingham and from whomever may also be contributing.

Juat downloading the release candidate for today, but I tried out the 603 Beta a few days ago on a reasonably complex InDesign idml file which I had done before, and this time it imported rather perfectly.
This is a great improvement from early versions, as appreciated as they were.
The document has framed local layouts, images with captions, Asian language segments, multiple sections, and lots of details like hyphenations which had thrown text layout significantly off originally.
The text layout decisioning now, while perhaps not quite up to Adobe's long-in-experience parapgraph engine a few places possibly, was just fine. Any remaining desires can be easily adjusted.
I'm no professional printing expert, but I think you have been doing a marvelous job, there in Nottingham and from whomever may also be contributing.

Juat downloading the release candidate for today, but I tried out the 603 Beta a few days ago on a reasonably complex InDesign idml file which I had done before, and this time it imported rather perfectly.
This is a great improvement from early versions, as appreciated as they were.
The document has framed local layouts, images with captions, Asian language segments, multiple sections, and lots of details like hyphenations which had thrown text layout significantly off originally.
The text layout decisioning now, while perhaps not quite up to Adobe's long-in-experience parapgraph engine a few places possibly, was just fine. Any remaining desires can be easily adjusted.
I'm no professional printing expert, but I think you have been doing a marvelous job, there in Nottingham and from whomever may also be contributing.

Maarten, that's very interesting....
Yes, I suspect Affinity can easily deal with this problem, once seeing it clearly, alongside the work-around here.  I'd modify what I said only to suggest that a desirable automatic fix mode be also one of equally available configuration choices, necessarily saved in the document  -- I think you'd still like to be able to adjust in some circumstances, as ever for getting what the human sees best.
Yes, I had some thinking this might have occurred and been part of the problem -- if you drew _again_ for example the problem curve that produces the myriad-point intersection. Drawn or traced again with not precisely the same path as the initial shape, then there're all sorts of opportunities for micro-difference -- including once again possibly primarily in the quantization given intersection probably works with measured-apparent positions rather than the Bezier points themselves. But again, Affinity guys and gals will have to know the details.
Now, I looked at your references, and have to say that's an extremely attractive presentation. Your mini-resume gives a pretty good hint how this came about ; also reminds a bit of how it was to come in weekends or evenings when consulting with the BBC, and find persons micro-refining what would become one more excellent video interval on someone's television.
As to the procedure with the sphere, it must be an exact example of the phrase on the Wikipedia page for it: 'veridical paradox'. What looks it can't be true but is, to save someone from looking it up.
The key is that this is a purely mathematical procedure, where the sphere is allowed to intersect itself along the way.  This is not physical; and I take it as due warning to what one may understand as a danger signal in other situations, that the way so much 20th century physics is based entirely on math that just 'happens' to fit with what can be even quite carefully observed --in some cases but not others -- is no full answer. Witness controversy not lessening about 'dark matter', 'dark energy', relativity/quantum irreconcilability, and whether the universe is indeed stretching as we think after the last flip-flop about this. Small matters, and that is a multiple pun.
Ok, enough on a Sunday morning, but maybe will amuse you.
Take care,
Clive

@wigglepixel, I had a look, being curious, and because I saw nothing like this on intersecting reasonably irregular figures.
What I found with your example file is that if I displace by only one pixel (or whatever an arrow-key delivers) to the left, for example of the smaller piece, the problem goes away, and i get a normal-looking few points to define the resulting object.
I suspect the problem is in some kind of quantization of exact position for points of the two matching(!?) curves on the right - where you see the points build-up.
If those curves are for example very close but not entirely matching, one could imagine how this could result in many points apparently being required to define their intersection. Or, which is the reason I mention quantization, some method of reading the points which invents a micropixel difference in plotting each curve. I'd guess the quantization theory, since that could account for a noisiness where resulting intersections seem back and forth instead  of in one smooth curve.
So it's a little hard to decide if it's exactly an algorithm problem, especially as anything but this micro-match, even using your complex curves, gives a nice and simple result.
For the time being, I do understand  that you want to match the shadow/darker section within the larger and lighter one, but the result I get  with the one-(pseudo?)-pixel offset seems to look quite good, so maybe that can be good enough.
And as a fix, maybe Affinity can arrange a configurable quantization for matching, which would be saved with the drawing, to allow you to do 'exact' matches later if you really need to. Or best, an auto-configuring one, which would react when 'too many' points were generated vs. the number of  points in either of the individual objects beforehand.
These are interesting figures; not yet imagining how they'd be used....
[my results are on the latest Beta]