Pink dimensions in an IDW

[Anonymous]

Hello,

After creating an IDW with Assembly and sub-assembly (views) we make then associative and also LOCK the views. But after updating the 3D model alles the view are f*cked up. Some views are missing parts and some views are totally gone.

After turning hiden lines ON and then OFF the view is great again. But we have 20-30 views on a drawing and this takes much time.

[Curtis_Waguespack]

Hi gomn,

Can you explain LOCK all views? My thought is that it is related to that, but I don't follow what you mean by that term in this context.

I hope this helps.
Best of luck to you in all of your Inventor pursuits,
Curtis
http://inventortrenches.blogspot.com

[mcgyvr]

Yeah something in your process is causing the references (to edges/points/lines,etc..) to be lost.. 

You will need to pinpoint when/why thats happening..

[Anonymous]

Thanks for reply !

See the attachements. We have a main Assembly with Sub assemblys inside. But we need to show the Main and Sub assemblys.

Some views totaly vannish

we use INV 2015 PRO,

[Anonymous]

Stil the same problem

[asiteur]

Hi,

I think you miss understand the principle of 'locking', this llocks camera related properties, no more. A drawing will always represent the 3d model as it is.

What kind of things do you do when you 'update' your 3D model? Detaching dimensions is just something that happens sometimes.

If you update something simple, like the length of a rod everything should be fine. But as soon as you start replacing objects you'll have issues almost for sure.

As said by others before, you should go into your model and check which changes have this effect, and see if you can for example attach the dimensions lines a bit differently.

[johnsonshiue]

Hi! The behavior does not sound right to me. Could you show me an example (iam, ipt, and idw files) here or sent it to me directly (johnson.shiue@autodesk.com)? I would like to understand the behavior better.

Many thanks!

[ThrainnThorarinsson]

Hi,

Did this problem have a solution?

I actually came here looking for answers to another problem regarding sick dimensions but reading through this reminds me of another problem I had at work.

I use Tube and pipe to model up a pumping station for district heating (Rigid steel pipes). Later on, I create various levels of detail to represent different sections of the pipe structure as I want to represent them on a drawing. This I can not do by dividing the sections between different tube and pipe assemblies, which is the reason I'm using a level of detail. Anyway, the problem is when I have laid out the drawing views of the different levels of detail and dimensioned them as I want to  I cannot have the .iam open at the same time as the .dwg (I use .dwg not .idw) or the dimensions on these views all become sick. Only the views of these different levels of detail become corrupted, no others. And as I said, this only happens if the .dwg is open when I work on the .iam. If I close the .dwg before opening the .iam and then close the .iam before opening the .dwg again it is alright.

Does anyone know the reason behind this?

@johnsonshiue 

[johnsonshiue]

Hi! If I understood your issue correctly, it was about the ability to edit multiple LODs at the same time. You may have read some of my replies to the similar topics before. Basically, there is a technical limitation with LOD.

LOD was introduced to INV back in 2006. At the time, the computers were 32-bit based and Windows has system memory limit to 2GB (up to 3GB with a switch). Such limited memory did not allow our users to build large assemblies (medium to today's standard). LOD tried to address the problem by unloading documents to free up more RAM for other operations.

It is a memory management tool, not a configuration tool. Though it does exhibit some configuration ability, however, it was not built for that purpose. In short, LOD is merely a way allowing user to unload some documents when memory isn't enough. One iam file having multiple LODs does not mean each LOD can be edited at the same time. You can load an assembly in LOD1 and also LOD2. This means you essentially load the assembly twice but in different memory segments. When you try modifying the assembly in one LOD state, you are editing the document. Naturally the assembly in LOD2 will be blocked from being edited.

This limitation can be exhibited in various ways. For example, you have Assembly LOD1 opened, while the drawing references LOD2. My suggestion is pretty much what you are doing right now. Edit one LOD at a time and make sure no other LODs of the same document are loaded. This will avoid the problem you are seeing.

Many thanks!