export ACIS option in DXF importer crashes and ACIS objects are not imported #51476
Closed
opened 6 years ago by matali23
·
6 comments
No Milestone
No project
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#51476
Loading…
Reference in new issue
There is no content yet.
Delete Branch '%!s(<nil>)'
Deleting a branch is permanent. It CANNOT be undone. Continue?
System Information
Windows 7 x64
Blender Version
Broken: 1cfc481
Short description of error
When ticking the option to export ACIS, the import will try to create a file with a very long name and crash. Without this option, it works, although ACIS object won't be imported.
Exact steps for others to reproduce the error
I can't provide the file as I have no rights on it. But it seems the addon create a xxx_surface_.sat, then xxx_surface_.001.sat, then xxx_surface_.001.001.sat, etc. adding 001 on each next sat file, until reaching the windows limit.
replacing line 1310 in do.py with
solves the problem, but solids are still not imported.
Changed status to: 'Open'
Added subscriber: @matali23
I learned as much as I could about Python as you asked and did my best.
Changed status from 'Open' to: 'Archived'
Here the importer relies on the dxfgrabber library . I have been in contact with its developer a lot when developing the dxf importer. He says, there is no open documentation on DXF solids, since AutoDesk just inserts solids in binary format into the dxf. He was only able to export the solids to sat files. So the behaviour you experience is not a bug "but a feature". We could also just ignore the solids completely, as it was the case with the former dxf importer. At the time when developing the dxf importer there was no python library to read sat files. Therefore, you might rephrase your problem as a feature request. But I am not able to help you with this right now - even if you find a python library for sat files.
Apparently you try to import quite a big file, if you hit the limits of windows? You might try to import the file to another software and export it to a different format. FBX importer might be able to deal with solids.
ok, I can understand. Maybe adding a warning or UI feedback about ignored elements would help users to understand what happened.
What about the patch? I think those line don't do what was intended and at least in this case, it solve the problem by incrementing 001 to 002 to 003 instead of making the name always longer with 001, 001.001, 001.001.001, 001.001.001.001, etc.