I've tested some dxf with these settings (and, i think, the c++ importer), my result it's not so goodragohix769 wrote: ↑Tue Jan 25, 2022 4:30 pmI use the legacy, maybe it's time to use the newer one!yorik wrote: ↑Tue Jan 25, 2022 11:52 amDo you use the legacy python dxf importer?ragohix769 wrote: ↑Tue Jan 25, 2022 11:42 am but importing directly in Fcad by Qcad pro lib, it's really really slow, it' takes a lot of minutes on my Ryzen7 workstation with 32 GB of ram
The newer, c++ one is super fast, specially with the "group layers into blocks" option... Here are my settings:
Screenshot from 2022-01-25 12-50-54.png
I'll test it with your settings, thanks a lot for the tips
If I use "goupe layers into blocks" with the majority of project that I converted from DWG to dxf with Qcad pro, Fcad simply crash.
If I don't use it, it works, but it's not so quick, and all dimensions, texts, and all is mixed (messed) in the root of the tree So I have to create some order in the caos even to rearrange the tree view with the assets. A lot of work, only to see the file. The scale draw that you import it's always a mess, because I have to calculate it every time what insert in the import screen, every draw in dwg it's different, I don't know why. This is REALLY annoying. Colors are not imported at all. After creating some group, then I have to create large compounds, because when you have a lot of line, it's not so cool to work/move (even in my WS that it's really speed up). But if you create compounds and then you want to edit some line, so you have to de-compound, edit the line, and then re-compound. Draft objects too are not convertet so all the lines are not parametric, generally speaking I have to retrace all from zero
Sadly the only solution for me, it's to preprocess all very well with Qcad pro because Fcad it's not able to manage (till now, at least!) 2D.
I already said that I (really) hate proprietary and closed standard?