Hi there a way to easily identify the error component of hops calling file…
any way to find the component easily using python or some plugins…
Basically my referencing script was quite a big and it has many cluster inside them.
I have the same issue. Unfortunately I haven’t found any direct method of debugging as I know from Visual Studio for example. I think creators of this add-in should consider this problem. From my experience I can advise to check:
- How many times Hops component is running and if it’s too many there is a mistake in “GetInputs” (TreeAccess=True and should be False).
- “GetInputs” should be flattened before entering component.
- Create additional output with name for example “debugging” and then connect anything to it and see in main file what is created at output.
Planes at input work very bad and can be rotated inside hops (it’s serious bug in this add-in). I walked around it in 2 ways: add rotation angle at input and then rotate plane inside Hops code or parse plane data to string with necessary accuracy (point and all 3 vestors).
I hope it will help You. I think this add-in has huge potential but it needs serious improvement in field of debugging. Best regards!
Thanks @Tadeusz ,i had used debug context bake .
After some time i stopped using hops for bigger geometry computations (most of the time they are slower than the normal vanilla scripts)…only using them for time consuming task such us ladybug daylight, view analysis ect,…