Name X

Tobiwan, that is exactly what I was looking for - perfect! Thanks for the replies!

I have a feeling the answer is no...but is there a way to display measured/nominal primitives in the 2D cross section viewer?  Here is my situation - I've got laser scan data of the wing contour, from which I cut some cross sections.  I've also got probed aileron hinge holes that lie on the same planes as the cross sections.  I also have numerically created nominal points at the tangent of the leading edge of the wing, and I auto-extracted those measured points from my scan data.  I've the cross sections created without issue, but what I really want to be able to do is show the cross section in the 2D viewer, but also display the measured/nominal aileron hinge holes and the auto extracted/nominal point on the leading edge along with the cross sections.  Can't seem to find a way to do it, any ideas?  Thanks in advance. 

Thanks for the replies -
I end up having to reduce the resolution down to 130 dpi and then it works every time.  Taking another look at it, the image quality isn't all that bad, so I can live with it for now.  Another workaround I found is to scale down my snapshot size in the options menu - reducing to 75% or 50% of default snapshot size allows me to increase the resolution - a horse apiece I guess.  I can make it work for now until I get the newer version. 

Hello All -
I recently started creating customized reports in IMInspect, which is a really cool feature and makes some sweet looking inspection reports.  The trouble I'm having though, is when trying to export the report to PDF, I keep getting the IMInspect error message saying "At least one image could not be generated.
The image resolution might be too high".  The obvious fix for this would be to reduce the default IMInspect resolution from 300 DPI to something less - but this ends up making the inspection reports look bad, especially when trying to show some nice color error maps of a curved part.  It seems strange to me that the image properties don't all mesh together to allow simple exporting without manipulation of image quality.  I am still using IMInspect version 11.0.7, so maybe this has been fixed in newer versions.  (still waiting on my company to fork over the maintenance agreement renewal costs!!! >:()  Anyone know of any work-arounds for this?  I guess I could resort to exporting them to .html, but I don't like how it doesn't have a nice page layout and isn't very printable. (........or maybe there is a workaround to the .html formatting?)  Any suggestions would be appreciated!!!  Thanks in advance!

Still seems to happen regardless of the number of points probed.

I keep encountering a somewhat annoying error when probing holes that have diameters slightly larger than the diameter of the probe tip of my Faro Arm.  I can get around the error by selecting the "probe is larger than hole" option, but if the probe isn't larger than the hole, won't I be misrepresenting the center point?  Has anyone encountered this problem or have any recommendations on how to get around it?  (besides using a smaller ball probe, that's not always an option!)  Thanks in advance! 

I have only used IMInspect in V11, but so far I am very impressed.  I use a Faro Laser Tracker in combination with a Faro Platinum arm quite frequently, so the introduction of the move device function has worked quite well so far (once getting over the learning curve).  It is much more intuitive now instead of fighting through n-centerpoint pairs and leapfrogs.  I also like how things can be much more customized inside of IMInspect instead of being stuck with the sometimes annoying default settings we were stuck with in version 10.  So far so good!  I agree about the alignment history in the tree view as well, nice option and much easier to trace back and uncover an issue than trying to look at alignment matrices.