Locked layers in dwg missing in revit

[vancikv]

I have a dwg with most of the layers locked. I can't see these layers in Revit, although they're present among Import Categories. They appear when unlocked in the dwg. Is there another way to show them? Is there some comprehensive explanation of this behaviour e.g. in AKN (I couldn't find one)? Revit 2022.

[David_Knight]

I can not reproduce this.

I tried linking, and importing.  same result.

Did you check that "All Lyaers" are being brought in vs just "Visible" layers on the link/import menu?

Did you check that on VG you have the boxes checked to view them?

Locked layers were imported, and were visible without any changes.

"Frozen", and "Off" layers were imported, but were not visible.  I had to turn them on in VG.

[vancikv]

Hm, thanks for trying, anyway. Based on your answer I have also tried and failed to recreate the issue in a newly created test file. The real file has some distinguishing features that could be blamed, like it probably originates from Civil 3D, has a Revit coordinate system and is located a large distance from origin (like 8000 km). When I unlock all layers, I can see everything just fine and when I re-lock them and reload the link, everything disappeares (except for the layer that was already unlocked in the original version of the file) from the viewport, but stays in imported categories.

[rborszich]

Late replying to this, but today I was able to confirm that locked layers in DWGs will position themselves far away from the project/origin, when linked/imported into Revit.  Unlocking the layers and reloading in Revit returned them to the correct position.  I know that C3D content like cogo points, tin surfaces and alignements behave the same way; separating themselves from the rest of the layers, FAR away from the origin. 

I have no idea how I've made it this far without being aware of this.

[vancikv]

Probably not always, though, as @David_Knight found out. I'd like to know why and when exactly this happens. That said, though, I actually forgot about this issue since it last happened because it's quite marginal to me 😀