I have been using the pro version and have discovered some issues with its autorouting engine that I have reported [HERE](https://easyeda.com/forum/topic/Auto-Router-completes-but-does-not-route-all-nets-f5189818b0ef430e8c86c151ddf41f6d)<br>
<br>
It is clear that the Pro version and standard versions do not share the same autorouting engine, and that the more mature standard local routing engine is far superior. I would even go as far as to say that the Pro version autorouting engine is beta level software at best.
I would therefore like to propose that the option to use the existing mature local autorouting engine be integrated into the pro version.
I assume that as the local autorouting engine is a standalone program it accepts an input from the editor and should therefore not be too difficult to integrate.
Alternately if this is not possible can some clarification on how the local autorouting engine can be used as a workaround. i.e. is there a workflow that allows the project to be exported, run in the local autorouting engine and then reimported?
/DM
Chrome
109.0.0.0
OS X
10_15_7