Itoo Software Forum

Author Topic: FP area excluded by spline doesn't work if objects have XY translation  (Read 4618 times)

ZO6039

  • Newbie
  • *
  • Posts: 23
I have FP with trees (or grass) for which I use translation with X and Y minimum and maximum to break the uniform placement on the surface. I try to use spline in FP area section to exclude the part of the FP scattered objects. I need excluded area to cut exactly where spline is. But precision of the cut is what I have in XY translation for the scattered object. In another words, excluded area doesn't take in account translation because it is first in order, then translation is applied. How can I cut area with no matter what translation of the objects is?

Paul Roberts

  • iToo Software
  • Hero Member
  • *****
  • Posts: 3050
Re: FP area excluded by spline doesn't work if objects have XY translation
« Reply #1 on: August 22, 2024, 12:19:02 PM »
Hi,

I'm afraid this is a known limitation when using high translation values.


As mentioned in this tightly related post: “A possible way to avoid this kind of problem, where enabled Transform - Translation can push some items outside of the Area, would be to "limit" these values in proximate areas to the boundary line.

I hope that helps.

Best regards,
Paul Roberts
iToo Software

ZO6039

  • Newbie
  • *
  • Posts: 23
Re: FP area excluded by spline doesn't work if objects have XY translation
« Reply #2 on: August 22, 2024, 07:12:13 PM »
Thank you for reply. I have checked the included Effect in that post which works for included area. I will try to make something similar for excluded area. But in my opinion, the logic of object translation should be changed in ForestPack, so translation of objects should be done first, before applying area boundaries, to cut the objects which are out of the boundary line. Or there should be an option what to do with the objects beyond the boundary line after applying translation, delete them or keep them. There are Falloff Include and Exclude parameters in Area to tweak the edge. Why couldn't we have Cut parameter there?