I agree with everything listed above, and would like to add a few specific requests for release 3.3:
- May the Enscape grasshopper components also be compatible with Rhino.Inside (revit)
- May multi-asset placement by radius, rectangle, or region have a live interface within the Grasshopper UI
- May the Video Path receive a NURBS curve input, and accept a list of points, vectors, and time stamps along that curve
- May the Batch Panorama feature be based on a collection of Points
- May there be a node-based material-creation/preview feature similar to Unreal Engine