This has been changed for performance reasons:
When you hover the cursor over a Point-cloud object, the plugin must check each dot, and return a valid "hit" when intersecting.
This is done at CPU level, and we noticed that may cause viewport lag with dense objects.
For this reason, we limit the checking process only to a number of dots by object.
Since we changed significatively the Point-cloud mode (this is described in
the FP9 release notes), hit-testing process is affected as well.
Initially we have defined a limit of 1000 dots by object for testing. This may be changed in
forestpack.ini:
We included several parameters in the configuration file (forestpack.ini) for fine tuning:
- cloudPointsByObject (default: 250000): number of points of each Forest object. Setting it to 0, reverts to the classic Point-cloud mode.
- cloudHitTestMaxPoints (default: 1000): maximum number of points used for hit-testing (to select items on viewport). You can reduce it, to improve hit-testing performance.
- cloudSubSelDensity (default: 300): percent of points for selected items on Custom Edit mode.
- cloudSubUnselDensity (default: 100): percent of points for unselected items on Custom Edit mode.
Depending of your feedback while the beta, me may increase this default value (although you may change it manually). But please note this also affects viewport performance.
Also usually moving the cursor a bit over nearest dots returns a valid hit, letting you to select the Forest object.
3DS Max includes a hit-testing mode at GPU level, but is disabled by default (we unknown the reasons).
But even enabling it (which can be done from Maxscript), i think it's not available for third-party plugins.
Topic: Point Cloud - hard to select (Read 560 times)
