Incident Solar VB.net Problem

I have used this definition that maps sun potision and draws a grradient of solar radiation on numerous occasions. Yet, when I open it now, the SPA VB.net script produces only null values. I am using the latest gh build currentlly, which is the only difference I can think of since it worked last. I really know very little about VB, but I have absolutely know clue how to get the null values to actually work. Could there be an issue with the VB script in the new build? Does anyone have solutions to get the outputs of the SPA component to produce values?

The definition can be found here:

http://www.tedngai.net/experiments/incident-solar-day.html

Attachments:

01.jpg, 262 KB

Replies to This Discussion

Permalink Reply by Andrew Heumann on August 9, 2012 at 11:45am

The legacy script components do not seem to work any longer in v9. in any case I've gone through and updated all the non-functioning scripts.

Attachments:

sun_system-Irradiation-Day-v9.gh, 33 KB

Permalink Reply by Dan Raznick on August 9, 2012 at 11:58am

Excellent work indeed. Thank you very much.

-Dan

Permalink Reply by David Newton on August 9, 2012 at 12:42pm

Excellent! Was just dealing with this problem. Thanks!

Permalink Reply by Dan Raznick on August 14, 2012 at 3:44pm

Andrew, thanks again for your help with the Solar-day script. I'm now working with the Solar-time and Solar-year scripts. I tried replacing the non-functioning components in that too, but the SPA component is still having the same problem. Did you change the vb.net script(s) too?

Definitions found here:

http://www.tedngai.net/experiments/incident-solar-current-time.html

http://www.tedngai.net/experiments/incident-solar-analemma.html

Permalink Reply by Andrew Heumann on August 14, 2012 at 4:11pm

the changes I made were:

1. to switch from legacy to updated vb.net components

2. to ensure that all inputs operating as "lists" were specified properly in the new components. Note that v9 loses this information in the legacy components, so you have to infer from the code whether it's expecting a list or not.

3. Update all pre-rhinocommon code to rhinocommon equivalents. On3dVector -> Vector3d OnBrep -> Brep etc.

Many of the scripts in these other definitions are actually identical to the scripts in the first one, so you should be able to just copy-paste and replace them in most cases.

Permalink Reply by Ali Who! on September 1, 2012 at 11:18am

Hi Andrew!

I am also new to vb and I'm trying to learn that by pdf tutorials. But the tutorials through the net were written for old versions of grasshopper, which doesn't work in newer version!

How can i update the script. Is there any routine rules for updating "the non-functioning scripts"?

Permalink Reply by Manuel on August 7, 2013 at 4:05pm