Emit Location vs Get Closest Location. What's faster?

Discussions about SOFTIMAGEs© Interactive Creative Environment©
Pancho
Posts: 659
Joined: 19 Sep 2010, 09:28

Emit Location vs Get Closest Location. What's faster?

Post by Pancho » 22 Mar 2014, 15:49

Well, not so much more too add. If you need to determine the surface normal, weight or texture values usually you can go both ways on a static mesh. Is there any advantage of one over the other? Especially with millions of executions it makes for sure a difference.

Cheers

User avatar
rray
Moderator
Posts: 1810
Joined: 26 Sep 2009, 13:51
Location: Bonn, Germany

Re: Emit Location vs Get Closest Location. What's faster?

Post by rray » 22 Mar 2014, 18:51

Would need some tests (try the built-in ICE stop watches for that).
My guess is that EmitLocation is faster since it's only an attribute that gets read. But ClosestLocation is so optimized that it could be equally fast.
softimage resources section updated Sep 26th 2026

User avatar
Mathaeus
Posts: 1778
Joined: 08 Jun 2009, 19:11
Location: Zagreb, Croatia

Re: Emit Location vs Get Closest Location. What's faster?

Post by Mathaeus » 22 Mar 2014, 22:53

+1 for Emit location as faster. Should be way more predictable, as it is fixed. Get closest Location relies on searching by distance. By the way, Emit Location is writable, if you create the emission from positions, for example, still it's possible to set Emit Location, using Get Closest Location or something else.

forton
Posts: 210
Joined: 25 Nov 2011, 16:57

Re: Emit Location vs Get Closest Location. What's faster?

Post by forton » 23 Mar 2014, 23:07

Mathaeus wrote:Emit Location is writable, if you create the emission from positions, for example, still it's possible to set Emit Location, using Get Closest Location or something else.
Thanks for the tip Mathaeus, I didn't know that!