I think you misunderstand. IndexCtl only affects the xrefs in a DWG. It doesn't affect a partial open. But you need to set the IndexCtl inside the original DWG from which the xref is loaded - it won't help setting it in the layout DWG e.g.
So simply put, whatever xreffed layers are frozen / off won't get loaded with IndexCtl = 1 or 3. Portions cut from xrefs using xclip won't get loaded if IndexCtl = 2 or 3.
Knowledge is proportional to experience, but wisdom is inversely proportional to ego!
My little bit of "wisdom": Hind-sight is useless, unless used to improve the next forethought!
I guess I am not seeing the point here. Are you telling me that layers frozen/off in the layout don't get reloaded when the drawing is re-opened? I set my INDEXCTL to 3 in my base drawing, and the same on the layout drawing. Then froze one of the layers in the xref. When I reopened the layout, the layer was still frozen, but also still listed within the layer manager. I guess I assumed that the layer would just not be loaded. Maybe I'm just thinking about this wrong. Thanks.
As I've explained previously, the layer name is still loaded, the linework, blocks, text, etc. inside that layer is not reloaded. It just makes ACad use less RAM because it doesn't need to have entities in memory which won't show.
Think about it, if the layer wasn't even listed, how would you be able to turn it back on later?
Knowledge is proportional to experience, but wisdom is inversely proportional to ego!
My little bit of "wisdom": Hind-sight is useless, unless used to improve the next forethought!
Good point. Guess I will just give it a try. My question is, why is this even a variable? Why ever load information that you aren't going to use? I guess if you are trying to extract data such as block attribute information you would want every piece of geometry loaded. But why would you be doing this in an Xref'd layout? You don't have to answer this. I just think this logic is what was confusing me. Again, thanks for all fo your help on this issue.
Last edited by oliveoil; 2010-01-22 at 01:02 PM. Reason: elaborated
it might be an old post..
but just had the problem myself (a very annoying one indeed, the cursor not moving but jumping)..
the SOLUTION for me was to reconcile the layers...
We switched our indexctl to 3 a few months ago and not many of us were clipping xrefs. now that we are clipping xrefs, our hatches are disappearing, polylines don't show up, crazy weird stuff. No that i read through this post i can see what is happening.
What a pain in the bleep.
Thank you kindly
Cad Committee Technical Adviser
R14 - C3D 2012
http://www.youtube.com/user/butzers03xtreme I drive a Silverado, its loud and i like it
Yes, I've found similar problems before. Usually on hatches / blocks. What I've noticed is if the Hatch setting out point / block insertion point falls outside the clip, the hatch/block won't get shown (usually). Try modifying the hatches with HEdit and setting the setting out point to somewhere inside the hatch itself. Blocks (unfortunately) needs redefining for this to work. Perhaps it helps
I've never had the issue with PLs though. Are you using the default LWPoly or set to use old (pre 2000) 2d Polies?
Knowledge is proportional to experience, but wisdom is inversely proportional to ego!
My little bit of "wisdom": Hind-sight is useless, unless used to improve the next forethought!