Announcements

The Autodesk Community Forums has a new look. Read more about what's changed on the Community Announcements board.

Linking parameters to levels of detail

charlesharington
Contributor

Linking parameters to levels of detail

charlesharington
Contributor
Contributor

Is it possible to link a parameter to a level of detail?

For example if I am working on an assembly instead of a 0mm mate using e1 then when I want an exploded view of that area making a level of detail where e1 is set to 100mm creating an instant exploded view?

This would allow the explosion of various areas of the model to be linked and adjusted easily.

0 Likes
Reply
Accepted solutions (1)
825 Views
5 Replies
Replies (5)

admaiora
Mentor
Mentor

You can do it with iLogic

Admaiora
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.

_____________________________________________________________________________
Facebook | Twitter | Youtube

0 Likes

charlesharington
Contributor
Contributor

I have tried this however the lod change has to be driven by Ilogic to update the parameter and the change does not occur when changing lod for drawings as it is not an I logic change. Am I missing something?

0 Likes

jtylerbc
Mentor
Mentor
Accepted solution

What @admaiora said is technically true - this could be done with iLogic.  However, I question the reason for wanting to do it that way in the first place.

 

Levels of Detail are primarily a memory management tool for working with very large assemblies where computer performance becomes a problem.  You use them to free up memory by unloading components that aren't relevant to your current task.  For example, if you are designing a car, and currently working on the exhaust system, you probably don't care about the detailed models of the radio knobs or the cigarette lighter.  So you create an LOD that suppresses those irrelevant components and reserves the memory for the type of work you are currently doing.

 

LOD's don't naturally interact with constraints or parameters in any way.  While iLogic could be used to create a type of connection, it sounds to me like you really need to be using Positional Representations instead of LOD's.  They are intended to suppress or override the offset values of constraints, and would thus be able to do what you're attempting without needed any sort of iLogic programming.

jtylerbc
Mentor
Mentor

@charlesharington wrote:

I have tried this however the lod change has to be driven by Ilogic to update the parameter and the change does not occur when changing lod for drawings as it is not an I logic change. Am I missing something?


 

No, you're not missing anything, which is another argument for doing it with the PosRep method I described.  There might be ways around that, but they would cause a delay between switching to the LOD and the constraint parameters changing.  For example, you could set up the iLogic such that it checks to see what LOD is active and changes the parameter value accordingly.  You could then set that rule up to run "Before Save".  So there would be a time between changing the LOD and saving the file in which the parameter value did not match your intent.

 

Also, regardless of how you trigger it, the LOD method won't be creating multiple states for the constraints to exist in.  It will just be changing a single constraint between possible values.  At no point would it ever be possible to show the assembly "assembled" and "exploded" at the same time.  To be able to do that, you'll need the "Override" functionality of the Positional Representation.

0 Likes

johnsonshiue
Community Manager
Community Manager

Hi! Like experts have mentioned earlier, LOD is a memory management tool. It is not supposed to alter design intent. When a component is suppressed, the given document is unloaded from memory.

Many thanks!

 



Johnson Shiue (johnson.shiue@autodesk.com)
Software Test Engineer
0 Likes