Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - romullus

Pages: [1] 2 3 ... 519
And are you familiar with Autodesk products? :D

I wish i could say no :D

I'm not coder, so my thinking was "that must be a trivial task"... :]

Why this complicated setup? Corona already has properly implemented master control in CoronaColorCorrect texmap, they just need to add this to the rest of the maps, like triplanar and UVW randomizer.

Gallery / Re: CGI | NYC
« on: Today at 09:35:50 »
What city bus with Russian license plate is doing in NY? :D

The problem I see with this method is that in many cases it won't give us the desired result. As long as the pivot point of a element is inside the scattering area, the tool won't delete that element.

I think that having an additional option to use some objects from the scene (like the sidewalk) as the "trimmers" would be a better solution than just relying on the pivot of the elements.

Don't forget that element's pivot point is at its selection center, not at its base, so in your example those marked blades would be trimmed by the scatter. I'd suggest to actually try the feature and see if it really fails in most practical scenarios. In my opinion, which is based on short testing, current implementation works great and might be even superior over bounding box detection.

It considers the pivot of the element, not its bounding box. So any element whose pivot is outside of the defined area will disappear (grass blade growing on a plane will be visible, grass blade growing outside of plane will disappear). We may consider the bounding box or or other methods of trimming in future versions too.

Please make it optional, in many cases pivot point detection makes more sense than bounding box detection.

Here's quick comparison between spline areas, edge trimming and slicer. I think some people expected edge trimming to work like slicer. Personally i find current behaviour much more natural and realistic, but it seems that there are some issues with edge detection precision, which i'm sure will be fixed by the devs in future builds.

Bug report - edge trimming isn't working if plugged through Corona select texmap.

I think it's the case of you misunderstanding how this feature works. It removes any mesh element that are placed outside of scattered area*. It will not remove anything if your instances consist of single element, like box, or teapot in your examples.

* i'm not exactly sure how the scatter determines when element is considered to be outside of scattered area. It looks that decision is taken not by dimensions of element bounding box, but rather by the placement of its base, which IMHO is very nice feature!

Are you sure about this? It wouldn't be trimming then? It'd be more like removal.

Can't speak for the others, but that's exactly how i want this feature to behave. If i'd want to slice geometry exactly and precisely along the edges, i could use Corona slice instead.

As for the installation, i had no issues at all - installed RC1 build and everything worked. Maybe there's some issue with multi-loader setup, like it was the case recently? OTOH, if you already tried unpack method and it still doesn't work, then i have no clue how to help, other then suggest to contact the support.

Can you show your setup and the result that you get? There shouldn't be any "slice effect" - edge trimming is removing whole mesh elements that falls outside of scattered area.

[Max] Daily Builds / Re: Clouds playground!
« on: 2022-10-01, 10:02:52 »
I forgot to thank the team for the seed parameter, it's so much easier to quickly evaluate different clouds positions now, so thank you very much! :]

Pages: [1] 2 3 ... 519