Skip to Main Content
Need Support? Let’s guide you to the right answer or agent.
Status Future consideration
Categories General
Created by Guest
Created on Feb 20, 2024

Automation using Visual Scripting

Visual Scripting is a feature that uses a graphical interface to lower the entry barriers for users to create their own automations and tools with or without the need to code. Current technology exists today in various forms such as Grasshopper, Dynamo and Bentley's own GenerativeComponents.

Do you have a need for an easy entry into automating workflows and would a lower the entry barrier and help your day-to-day activities.

  • Guest
    Reply
    |
    Mar 4, 2024

    That would be great if line element could be able to embed the visual scripting / vba codes so as to form a part of 3D modeling. When you modify the line, the whole 3D model linked to the line would be updated automatically. That is something like 3D linestyle but more powerful than that.

  • Guest
    Reply
    |
    Feb 26, 2024

    This is definitely a good direction.

    I think it is important to be able to edit the scripts in both visual and text form, so that the script can be edited in either way.
    Python, Lua and VBA are good candidates for this. VBA has the advantage of being already existing, which means that this could be useful to edit already existing codebases, but aside from that Python is probably the best choice.

    Being able to connect the script to external ressources, such as excel files, python scripts, or maybe even command line programs, would also be a great advantage, and allow further automation.

  • Guest
    Reply
    |
    Feb 25, 2024

    It would be great to re-introduce GC as part of Mstn... see how Grasshopper and Dynamo are integral to Rhino and Revit respectively. Having said that:

    1. Automating workflows: it would be good to modernise GC to enable it operate on elements in the dgn model without locking them in its graph... like Dynamo can. This would open the way for GC to replace all those klunky VBA macros.

    2. GC is more scripting friendly compared to GH for beginners. It would be good to build in support for Visual Studio IDE into Mstn:GC like the current VBA editor in Mstn. It is a known problem that visual scripting gets quite unweildy quickly and users tend to progress or revert to text based scripting at some point.

    3. Built in VS should also align with the Python tools that I think are coming to Mstn. Not sure, maybe GCScript should be replaced by Python; and the current GCScript IDE replaced by a customised version of VS Express built into Mstn.


  • Guest
    Reply
    |
    Feb 22, 2024

    Hello, this is the sort of thing I am also campaigning for.

    Using visual scripting to build custom extensions that activate on events or user intervention.

    https://microstation.ideas.aha.io/ideas/MSR-I-1457