anni's tower takeover cad thread *now featuring explanations*
hi guys!

i’m no longer competing, but i’m still trying to make cad’s of a robot that might work, just as, random ideas or explorations. i’ll try to do one every two months as i see the meta change, and i’ll log my work here. don’t expect regular updates, but i’ll be open to questions in this thread…
update to everything:

i’ve now made a playlist, this is pretty awesome ngl. here you’ll find everything automatically labelled “tower takeover cad” from me, and i’ll occassionally go through and add in my explanations.

also: here’s a link to the 2018 parts library [https://drive.goog…](https://drive.google.com/open?id=1qxjcdodescticrltgwqu7qypofiorxoq)
Hi,


What attempts have you made at this? Have you got any code written yet?


Thanks hello bo, - - you are absolutely right, we have to add more architectural examples. i will also try to blog about those things. give us some time to come up with those new content. - - thanks for your input. - - all the best, - jan blessenohl - the telerik team - - check out telerik trainer, the state of the art learning tool for telerik products. - [@lawnnerd](/u/lawnnerd) 
good news! 

franz, 


the team has completed an improved handling of this type of station. the team ran a manual update for this specific station and will running an update against all stations with the latest precipitation code this afternoon. this will ensure that all current and past… its kind difficult to understand in my POV but not impossible  

imagining it while reading


can you show some codes? or samples on what you want to achive? [image] ryan\_blything:

i have difficulty understanding why (since ultimately, rts should be dependent on keyboard press rather than frame rate).

builder experiments are structured around a drawing loop and event cycle that is driven by the screen refresh rate. so the keyboard is checked once … well, i raised an issue with id support whom escalated it with engineering or something and it's now working. they did say they'd text me updates and haven't received anything from them so whether they did anything or whether it just started working.. who knows. 

but yeah, looks like the answer is calling / talking to support. [@sunlightworking](/u/sunlightworking) this is only a start but you could have fun using subd to model it, break the shape into 2 repeating ‘arms’ that then join together.

[[viewcapture20210611\_093810]](https://aws1.discourse-cdn.com/mcneel/uploads/default/original/4x/b/9/e/b9ec0eea392ef36150b75631db22d3817573de5b.jpeg "viewcapture20210611_093810") There could be a variety of leaderboards. Like one of top points overall, and another for the most points gained in the previous 4 weeks or something. I may never top to overall leaderboard, but I have a chance of getting on a monthly leaderboard. Well.



Think about what you know about lifts.



Go with the theory of 2 lifts, one you have more than 1 lift the logic is the same you just have more options.



Lifts go 1 of 2 ways. up or down.  

A lift at floor 1 told to go up, if someone rings the bell on 3 and the lift is going there or passing there on the way up and the person said "up" on 3.. then it will stop, otherwise if its not due to stop there and the person said down, it wont. The other lift will get the job, or if both are going up, then it will be the first available lift.



Your lift needs states waiting/up/down



Your logic shouldnt be that complex, so, write down in words what your logic choices are, senarios etc



Then you should be ready to code it thanks everyone for your suggestions. i went with a modified version of [@weekend](/u/weekend)’s:

[[screenshot from 2020-02-22 06-44-57]](https://media.blenderartists.org/uploads/default/original/4x/a/d/6/ad62e605b45c9294a1a33960e705f2a07772113c.jpeg "screenshot from 2020-02-22 06-44-57")

since the idea was to have the ability to have the arrows appear independently, instead of simple subtraction, i fed the result through nodes equalling 1-4x^2, which is an inv…