Altium slows down when dragging some components.

[palpurul]

Hello,
I've just received a PCB layout job from one of my customers. It's a flex PCB design with about 600 components.

The problem is that when I try to move some components (99% of them) Altium behaves very sluggish.

Let me show you this in a video:
https://streamable.com/wc34b5

The component on the right (1 pin header) doesn't cause any problem when dragging, it's from the default Altium library (miscellaneous_connector.Intlib I think). The component on the left (diode) is generated by the customer it's from their library and whenever I try to pick one up and move it, Altium slows down terribly.

Thanks in advance!
What would be the cause of that, how can I fix it?

[thm_w]

D1 has a 3D body while TP7 has none. So its doing additional 3D clearance violation checks when you are moving D1. Still normally it would never be that slow.

What version is this? Do you have another version installed you can try on.
What are system specs?

If necessary you can turn off on-line DRC, but, that shouldn't be required unless its a very old system.

[palpurul]

Actually I tried this on many PCs. There is some kind of a problem with the project I assume.

When I try the version 17 it works great, but later versions it always sluggish.

[Batang]

I have seen this before and it always turned out to be a library problem.

[palpurul]

I have seen this before and it always turned out to be a library problem.

THat's what I was thinking as well. Have you ever solved it?

[thm_w]

I have seen this before and it always turned out to be a library problem.

Library problem, as in, the entire library is corrupted? Or as in, an issue present in all footprints?

Maybe you could unlock primitives, delete the 3D body, see if that does anything.
Or copy the footprint to an empty library and load it from there.

https://www.altium.com/documentation/knowledge-base/altium-designer/slowness-in-specific-areas

[Doctorandus_P]

I have seen this before and it always turned out to be a library problem.

It may have something to do with a library, but if you pay Mega $$ each year for some software, then I would at least expect it to be robust enough to not get brought down on it's knees by some library issue like that. So I say it primarily is a bug in the software that manifests itself when there is some library issue.

This also means I would let their customer service handle it. Maybe make a bug report.

[ajawamnet]

I would shut off the online DRC first.  Is it possible to share that PCBDOC?