Wesley Burrows Posted February 1, 2018 Share Posted February 1, 2018 Has anyone else run into this? Happens everytime. Isn't file specific (happens across different ones) and if I save the VW file as VW2017 and export with 2017 it works just fine. Link to comment
0 Vectorworks, Inc Employee Nina Ivanova Posted February 1, 2018 Vectorworks, Inc Employee Share Posted February 1, 2018 Hello Wesley, Would you, please, attach an example DWG so that we can investigate? Thank you, Nina Link to comment
0 Wesley Burrows Posted February 1, 2018 Author Share Posted February 1, 2018 1 hour ago, Nina Ivanova said: Hello Wesley, Would you, please, attach an example DWG so that we can investigate? Thank you, Nina Attached is a fresh DWG (just received this morning) imported into a blank drawing. Crashes everytime I try to export a DWG. Venue_1.vwx Link to comment
0 Wesley Burrows Posted February 1, 2018 Author Share Posted February 1, 2018 Also here's the original DWG. pp_04.dwg Link to comment
0 Vectorworks, Inc Employee Nina Ivanova Posted February 2, 2018 Vectorworks, Inc Employee Share Posted February 2, 2018 Thank you, Wesley! Yes, this is a known problem for SP2, which is already fixed for SP3. It appeared after some restrictions done in the third party library, which we use for reading and writing DWG files. We had to adapt our code to follow the same restrictions. This problem appeared in a very special case - export of negatively scaled symbol instances with attached to the symdef record format - which usually happens when you have an imported DWG. There are 3 such symbols in your document - 01PSBB01, 01PSBD01 and 01P054. Detaching record format from mentioned symdefs fixes the problem (and there is no loss of data after export to DWG - see images). Thank you for reporting and sorry for the inconvenience. Nina Venue_1.vwx Link to comment
0 Wesley Burrows Posted February 2, 2018 Author Share Posted February 2, 2018 6 hours ago, Nina Ivanova said: Thank you, Wesley! Yes, this is a known problem for SP2, which is already fixed for SP3. It appeared after some restrictions done in the third party library, which we use for reading and writing DWG files. We had to adapt our code to follow the same restrictions. This problem appeared in a very special case - export of negatively scaled symbol instances with attached to the symdef record format - which usually happens when you have an imported DWG. There are 3 such symbols in your document - 01PSBB01, 01PSBD01 and 01P054. Detaching record format from mentioned symdefs fixes the problem (and there is no loss of data after export to DWG - see images). Thank you for reporting and sorry for the inconvenience. Nina Venue_1.vwx Thank you for the info! Link to comment
0 Tparabia Posted March 4, 2018 Share Posted March 4, 2018 is there anyway to search the drawing to find negatively scaled symbol instances? Link to comment
0 Shrunken Ned Posted March 5, 2018 Share Posted March 5, 2018 same problem. How do I search for the negatively scaled symbols? Link to comment
0 Vectorworks, Inc Employee Nina Ivanova Posted March 6, 2018 Vectorworks, Inc Employee Share Posted March 6, 2018 Tparabia, Shrunken Ned, You can do the following in order to be able to export your documents to DWG - as a temp workaround until you get the SP3 version where the problem is fixed: Save your document as a new one, just for the export purposes. Create a new resource of type Script. Copy the script from the attached txt file inside the opened Script Editor window, compile and run it (be sure to have Language set to VectorScript). It will detach all the records from the negatively scaled symbol instances and corresponding symbol definitions. If you still see a crash even after you have run the script, then, please, send the original document to me. Best Regards, Nina DetachRecordsFromNegScaledSym-updated.txt 1 Link to comment
0 Shrunken Ned Posted March 9, 2018 Share Posted March 9, 2018 It did still crash VW. Sent you VWX file through PM Link to comment
0 chrisjones Posted March 12, 2018 Share Posted March 12, 2018 I'm having problems with VW2018 publishing DWG's. I've had to convert a full project back to VW2017 just so I can export to DWG. Every drawing I've tried to export crashes. VW2018 is just unusable in this state. Does anyone know when SP3 is being released? Link to comment
0 Vectorworks, Inc Employee Nina Ivanova Posted March 13, 2018 Vectorworks, Inc Employee Share Posted March 13, 2018 On 3/10/2018 at 12:16 AM, Shrunken Ned said: It did still crash VW. Sent you VWX file through PM Problematic negatively scaled symbols with attached records, placed inside other symbols, were not fixed. Fixed version of the document was sent via PM. Updated VectorScript can be found in my previous post. Link to comment
0 bruce a+ Posted February 27, 2019 Share Posted February 27, 2019 I was having the same problem with 2 sheets (out of many) in a 2018 SP5 project crashing VW on DWG export, I imported it into 2019 SP2 and it still crashed. I ran the above script in my 2019 file and the 2 drawings exported to DWG without crashing. Seems like this export DWG / negatively scaled symbol issue needs to be fixed in the next 2019 service pack? Link to comment
0 bruce a+ Posted February 27, 2019 Share Posted February 27, 2019 Further to the above post, the script deleted symbols that I had created or modified, concrete blocks and gas heater for example, from my VW files. I assumed 'removing the record' would remove some attached data, not the actual symbol. Luckily I have the original 2018 file to keep working on. Link to comment
0 Vectorworks, Inc Employee Nina Ivanova Posted February 28, 2019 Vectorworks, Inc Employee Share Posted February 28, 2019 12 hours ago, bruce a+ said: Seems like this export DWG / negatively scaled symbol issue needs to be fixed in the next 2019 service pack? It might be, but also might be some different issue, which we need to investigate. All the previous fixes are already in VW2019. If you send the document and export settings, we could do more investigations. 12 hours ago, bruce a+ said: Luckily I have the original 2018 file to keep working on. As a rule, when there is a need of special document edits in order to complete some export or whatever else, you must work in a copy of your original document. Link to comment
Question
Wesley Burrows
Has anyone else run into this? Happens everytime. Isn't file specific (happens across different ones) and if I save the VW file as VW2017 and export with 2017 it works just fine.
Link to comment
14 answers to this question
Recommended Posts