<![CDATA[A faster way to obtain shadow_info?]]>Hello,

I would like to obtain SunDirection vector a lot of times on a whole year.
But the method below is too slow. Is there a fast form to find out SU shadow_info?


vec=[]
info=Sketchup.active_model.shadow_info
atime=Time.now

for i in 0..50000
  info["ShadowTime"]+=600
  vec<<info["SunDirection"]
end
]]>https://community.sketchucation.com/topic/133595/a-faster-way-to-obtain-shadow_infoRSS for NodeTue, 12 May 2026 13:57:49 GMTThu, 01 Mar 2012 10:20:34 GMT60<![CDATA[Reply to A faster way to obtain shadow_info? on Thu, 01 Mar 2012 12:04:31 GMT]]>It's not actually getting the info that's slow. It's setting it.

When I ran the test it took ~11sec to run.

When I removed info["ShadowTime"]+=600 it took ~0.15sec to run.
That's why I hoped using start_operation would help - but alas. But at least, when you do this, ensure that Shadows are not on in SketchUp.

]]>https://community.sketchucation.com/post/1313624https://community.sketchucation.com/post/1313624Thu, 01 Mar 2012 12:04:31 GMT<![CDATA[Reply to A faster way to obtain shadow_info? on Thu, 01 Mar 2012 11:59:52 GMT]]>Thanks thomthom, maybe could be added to wish list ruby access to SU Solar Position Algorithm in a fast way.

]]>https://community.sketchucation.com/post/1313623https://community.sketchucation.com/post/1313623Thu, 01 Mar 2012 11:59:52 GMT<![CDATA[Reply to A faster way to obtain shadow_info? on Thu, 01 Mar 2012 11:32:00 GMT]]>hmm... I looked at it. But found no optimized way. I tried making constants of the string -in case the creation of the strings for every iteration had a cost - but no change.
And you can't address the info with numeric indexes either...
I also wrapped the whole block in a start_operation with the disable_ui argument to true - but still no performance difference.

]]>https://community.sketchucation.com/post/1313619https://community.sketchucation.com/post/1313619Thu, 01 Mar 2012 11:32:00 GMT