Visual Analysis (FOV/FOR)

[MA_10188969]

I am looking for a way to conduct a Visual Analysis, for sight lines or sensor Field of Regard.  Ideally, we would be able to manipulate the 'visual' area to meet the human eye or the sensors visible area.  Given the 3D data in all of our Creo models, and the various scene/perspective view settings, I believe there has to be a way to create these from within Creo. 

It appears that the Manikin functionality has almost the solution (with Vision Cone & Vision Window), but I was hoping for a way to manipulate the eye’s FOV to match certain sensors we deal with commonly.  Is there a way to create a ‘custom’ manikin that would allow the FOV to be changed?  Or is there a ‘camera’ functionality that would do something similar?  Create a scene, or special view that limits the aperture & turns on perspective?

The result would be something like the attached image, with areas outside the FOV shaded/blocked.  

[LndoVnBtchmrk]

Hi, welcome to the community.

You might find this post interesting:
https://community.ptc.com/t5/3D-Part-Assembly-Design/Tip-of-the-Month-Excerpt-from-the-PTC-Technical-Specialists-E/td-p/440789

This shows how to do a "visibility" study with a User-Defined Analysis (UDA).  UDA's are part of the Behavioral Modeling Extension (BMX) so you do need to have that.

This is a very neat thing Creo can do and I've done it myself.  But once you generate this neat surface plot...then what? You can save the UDA as a saved analysis, but you can't save the results.  If the results are cleared then you must recompute to see them again which can be cumbersome since this is a very computationally expensive thing to do.  In the post I linked above you're instructed to create datum points to be able to save something from the results.  But there's so much more to these surface plots than what happens on the perimeter of the surface and it's all lost with this method.  You can always take screen shots, I suppose.

So this is a neat thing Creo can do, but it's use is limited by the inability of Creo to really do anything with the results.  I should point out that this is a problem with any two-dimensional UDA where results are plotted on a surface.  One-dimensional UDA's do not have this problem and you can actually use the results of those to drive changes to the model, create parameters, etc.