I think if the timeline graphic looked better and more up-to-date, at the minute it looks a little more old-school. So I think this would help Synchro Exports looks more professional and lessens the need for external/third party software.
User creates multiple baselines in P6 and exports them as XML. He import P6 XML but he can't see baseline list in Synchro's Baselines and Scenarios window. User request this feature.
HoSang Jeon
over 4 years ago
in SYNCHRO 4D Pro
0
Will not implement
Data Export: Comments: 2 fields called “comments” with different purpose. Could it be differentiated? Comments (last one). Could the column width be limited to 100 instead of 255. That will make visualisation easier. Start & Finish time. Could...
Philip Wheeler
over 2 years ago
in SYNCHRO Control / Forms
0
Future consideration
The document tab file viewer is not very good. It should operate more like a window explorer where you can see all files at once and filter them, not just viewing 50 at a time and having to repeatedly load more. Does not work with thousands of fil...
In some flows we have necessity to use a lot of scripts to manipulate behaviour of controls. Scripts are quite repetitive. Ability to define in a csv template or similar for batch upload would be of great time saving and benefit.
When accessing the model/marking up the model in work packaging, have components properties show when component is selected
i think with work packaging, it would be beneficial that when we access the model, mark the location, and create markets, the user to see the properties as they select components. that way the planner can mark up the model screenshots with the cor...
It would be great if it was possible to convert all 3D filters to resources automatically. Then all Search Sets within Navisworks would convert directly to Synchro resources. It's possible to do manually currently.
Guest
over 4 years ago
in SYNCHRO 4D Pro
0
Future consideration
There should be a way for Mouse Windows selection to select all components inside the windows, event if the components are invisible (behind / covered by other component) Right now it just able to select visible component.
0
Future consideration
2
Planned
