Hello all,
I am an FDOT Connect User. We are having issues when using the new civil labeler tool. If we try to undo a command, it deletes all callouts that we have created using the civil labeler tool, and it doesn't allow you to re-do the command. We have lost so much progress on plan labeling because of this. Has anyone else had this problem, and if so what is the work around?
Good morning Matt. This certainly an alarming issue. Could you share a little more information on what you are experiencing? I have done a quick test in 22R1 and see the undo command operate as I would expect removing each placed label one at a time. I am not running FDOT's configuration, but would like to do some testing on my end to make sure that I don't see something similar. What version of the software are you running?
Thanks,Steve
www.envisioncad.com
ORD - 10.12.02.04 / 10.10.21.04 / 10.10.01.03 / 10.08.01.33Power GEOPAK / Power InRoads - 08.11.09.918Civil 3D - 2021 / 2022
Hey Steven, thanks for your reply. We are running ORD 10.10.1.3.
After spending hours labeling plans, we have lost so much work for myself and other users in our office. When you undo, it deletes anything you placed with civil labeler, and it doesn't let you re-do. It's quite frustrating, and is impacting our productivity.
We have experienced this as well, though my understanding was that this problem occurs independent of the FDOT WorkSpace. We are currently running FDOT Connect10.10 MR2 (built on ORD 10.10.21.04).
Eddie Giese, PEProduction Manager | Senior Roadway EngineerLicensed in FL & PAACEC FDOTConnect Instructor on behalf of FDOT
Patel, Greene & Associates, LLC PowerGEOPAK V8i SS10 (08.11.09.918)OpenRoads Designer 2021 R2 (10.10.21.4)OpenRoads Designer 2020 R3 (10.9.0.91)ProjectWise Explorer CE 10.0.3.453LumenRT CE Update 14 (16.14.60.98)
Thanks for your response, Eddie! I asked them about this at FLUG this year, and I was told it's a bentley issue. Not sure how to correct or work around. Have y'all found a solution?
Not so much a solution as a best practice. We try to keep our TEXTRD files federated as much as possible to minimize the impact of corruption or, in this case, re-work due to a bug. That, and avoiding the Undo tool in any TEXTRD files...