I have seen this a few times now - if you import and try to Georeference a Vector PDF and the snapping to pixel locations in the image fail to work during the Georeferencing process, yet vector PDF snaps work once the image is georeferenced the issue is caused somehow by Bluebeam Revu - if you take a good PDF and break it up using Bluebeam, something changes in the PDF that throws TBC georeferencing process off so that the snapping fails until the image is georeferenced after which the PDF Vector Snapping works just fine.
This could be a Bluebeam defect or a TBC defect - I am trying to get a file over to Trimble so that they can take a look to see if there is anything that they are doing / not doing to cause the issue.
Alan
4 Likes
Alan, have you found a solution to this? We are having the opposite problem. The PDF georeferenced fine with snaps, but after it’s georeferenced the snaps do not seem to work. Thanks!
Try geo-refrenceing it again, click save snaps off, register, click save snaps back on and register. @Cole_Palmer
That worked! Alan also mentioned his new PDF Manager command fixes some of these bugs. Thanks for the info Erik!
We have also found that if you go to Support - Options - Advanced and then change Direct X to OpenGL2 that after a TBC restart fixes the issue
2 Likes
I’ve had a similar issue occur regularly where it will appear on my plan view as though vector snaps are not working to georef the pdf during import (but are) and opening up a new plan view fixes the issue of the snap icon not showing up. not sure if it’s related but it’s similar enough i thought i’d mention it because the outcome post georef is still the same.