I don't think I know what you mean. If it is that you want the curve numbers written out as text tags, use the reworked example below and adjust it to your needs.
/Ola
old version that has been fixed by now. I'd ask you to test this on the Rhino6 beta (which I am using to test this), but it looks like you're using a cracked version of Rhino so you probably don't have access to that.…
urs x 365 days ), and with modulus in the screenshot above, i could manage to do for every hour. but sometimes in my definition, i have a range from 1 to 35040, which is 365 x 24 x 4 ( 4 here defines every 15 minutes), on other word, when the number is one, then i have 01:00 O'Clock, when the number is 2 then i have 01:15 O'clock, when the number is 3 then i have 01:30 O'Clock...etc , so when the number is 97, which is the next day ( and after the number 96 which is equal 24 hours x 4), then I should have again 01:00 O'Clock.
I hope my idea is clear, thanks in advance!
Nassif…
gone with the wind topic: since this is utterly Academic the main issue here is to oversimplify LBS (in real life: a collection of columns/beams/slabs/X members + tube frame rigid members (shafts/elevators/cats/dogs)). Reason is that if we use the real "solids" (turned into meshes) as the "node" pool for the hinges required ... only HAL 9000 could solve it in "real-time" (for instance an E5 Xeon 1630 v3 takes ... several minutes). And this is ... er ... challenging I must say. This is a typical case where "simplifying" means "stupidity" almost instantly.
Spam on:
where's my collection of "bend-a-truss-that-looks-like-a-tower" K1 demo defs? Is in this workstation or in another? (blame Alzheimer).
Spam off.
More soon.…