Different standard, country, code, research etc. use different set of data and formula, so with this we can allow the copilot to stick to the said instruction/data that are followed in that region.
Allow Python to copy nodal loads and member parameters
When copying models to iterate on sizes, nodal loads are not copied even when told too and also the member parameters of unbraced lengths, releases, etc. are not copied and have to be re-applied which makes it that much less efficient of a way to ...
When trying to use Python to create other models to iterate layouts, it ran into an issue with creating and deleting nodes and members. it is apparently not possible for Python to do that. Having that possibility would be helpful to give a wider a...
When running python scripts and trying to copy and paste from Copilot to better understand the scripts, there is a character limit to past back in the box and the whole output text from Python cannot be paste into the copilot chat for it to troubl...
Ability to copy or download the current conversation session.
Support separate windows for Document Assistance (PIKA) and Copilot/Co-worker interactions, rather than combining both in a single window.
Allow execution of basic slash commands, s...
Implementing the creation of design strips via the API will make the development environment complete; please include this in the next development cycle. Initially, the data contained in the "Default Span Properties" graphical interface form must ...
WILTON GONZALEZ PARRA
3 months ago
in
0
Needs review
Why can't we specify the filename for the *.ism.dgn file? It doesn't even use the RAM model's name unless it's the first time you use it or restart RAM. Allow us to either specify the filename or at least use the same RAM filename consistently. {e...
Let us be able to save the iTwin settings when we "push to file" them, & be able to save the "mappings" & "operation settings". This would keep things consistent within & between projects.