Running on a MS Surface Pro 8GB machine - integrated Intel graphics
Sorry to have to say this , but please ... that is the wrong hardware ... I see people attempting to run Altium on 13 inch laptops, macbooks with windows installed, costco bargain-priced machines. It just doesn't work that way. Get a workstation grade machine. Fully loaded (used) Zbook 17 G3 or G4 can be found on ebay for below 1000$. 32G ram , Quadro graphics with 4 to 8 Gb of video ram , beefy i7 8 cores with lots of cache and unthrottled memory. Lots of computers skimp on memory speed running heavy on cpu cache. There is a difference between 40$ for 16Gb and 130$ for 16Gb memory ... speed !
I use a 5 year old G2 Zbook 17 inch in a docking station. I typically have Altium , Catia and Solidworks open at the same time without issues. Those are not exactly lightweight applications ..
Font alignment wrong - making the SCH hard to read
That is being fixed. That started when they switched to c#. There is something with the way c# engine handles fonts.
Hangs due to the SVNDbLib cache management
That i don't know. I run a a vault installation. No experience with dblibs.
High CPU usage whilst idle
I see 18% on 1 core when idle. They have a resource leak somewhere. But i only notice that after a few days of uptime.
Delays in routing, AWFUL routing performance in AD20 (fixed going to advanced settings - and selecting AD19 legacy gloss and route) - lots of ppl on the AD forum complain about that
That's due to the new routing engine introduced in AD20 . Switch the glosser off if you are resource limited. Run it post-layout.
Terrible SCH performance because it keeps hitting a server or something - fix: close Properties and /or Components Tab.
Components tab pulls data from Octopart. If your network is slow you will have sluggish response. There is an option somewhere to disable that functionality. Schematic - data management - advanced button, bottom right in the panel.
In the parts editor - changing pin names is not reflected until you 'select' all the pins after the edit.
I noticed this happens in the pcb library editor too. Especially stuff driven through a script suffers from this. There is something with the call to :robots: for post-edit refresh.
The parts editor is a bolt-on that was originally made by a 3rd party. Probably suffers from the same quirck. I don't use the parts editor. it's faster using the SCHLIB list and massage data in excel.