Oliver Hauser Posted October 26, 2018 Author Share Posted October 26, 2018 @Nikolay Zhelyazkov Just did a little experiment. I moved the vwx file from my project folder which is stored on Google drive file stream to my desktop. I re-opened the file and tried to edit the title block in the same manner and it worked, no crashing. Has this got to do with the folder hierarchy? Quote Link to comment
Vectorworks, Inc Employee Nikolay Zhelyazkov Posted October 26, 2018 Vectorworks, Inc Employee Share Posted October 26, 2018 @Oliver Hauser 1 minute ago, Oliver Hauser said: Has this got to do with the folder hierarchy? - Yes. As of SP-1, it is good to have your active vwx file in a folder hierarchy with depth at least 4-5, that has only this file in it and no additional files and folders. Quote Link to comment
Oliver Hauser Posted October 27, 2018 Author Share Posted October 27, 2018 Great thanks. Quote Link to comment
LVLDME Posted November 1, 2018 Share Posted November 1, 2018 I am also having this problem. Even in a file that worked fine up until version 4 and now on my version 5 export I get spinning beachball when I try to go to title block manager to change the version number and the application. I have a deadline so I will go and manually put filled text blocks over where I should be able to change info through the title block manager until this issue gets solved. Quote Link to comment
Vectorworks, Inc Employee Nikolay Zhelyazkov Posted November 2, 2018 Vectorworks, Inc Employee Share Posted November 2, 2018 @LVLDME, Have you tried moving your active file in a folder hierarchy with depth at least 4-5, that has only this file in it and no additional files and folders? Quote Link to comment
Oliver Hauser Posted November 2, 2018 Author Share Posted November 2, 2018 Easiest fix is to move the file to your desktop and work on it from there. Once done you can move it back to where ever you need for archive. Quote Link to comment
frv Posted November 7, 2018 Share Posted November 7, 2018 I am on OSX 10.13.9 with the same crash. Titleblock manager simply crashes VW2019. Tx for the workaround, , it does work so I can at least update the title blocks. Please fix this asap. Cheers Francois Quote Link to comment
Eli van Hooff Posted May 11, 2020 Share Posted May 11, 2020 @Nikolay Zhelyazkov This actually still works as in VWX 2020 latest SP, on Windows for one of my students.... Without this method it kept crashing.... Quote Link to comment
Vectorworks, Inc Employee Nikolay Zhelyazkov Posted May 11, 2020 Vectorworks, Inc Employee Share Posted May 11, 2020 Hello @Eli van Hooff, Could you send me a crash log so that I can check if this is the same crash? Thanks, Nikolay Zhelyazkov Quote Link to comment
Eli van Hooff Posted May 11, 2020 Share Posted May 11, 2020 @Nikolay Zhelyazkov Looking at the crashs, we could not find that VWX had crashed, but that CineRender did... She will try to re-create this crash after the lessons... 🙂 So far we have this: Beschrijving Pad naar toepassing met fout: C:\Windows\System32\DriverStore\FileRepository\nvlt.inf_amd64_b2022deee1f104cf\Display.NvContainer\NVDisplay.Container.exe Probleem met handtekening Naam van probleemgebeurtenis: APPCRASH Naam van de toepassing: NVDisplay.Container.exe Versie van toepassing: 1.15.2586.5913 Tijdstempel van toepassing: 5c75252f Naam van foutmodule: combase.dll Versie van foutmodule: 10.0.18362.693 Tijdstempel van foutmodule: 1fabb0ef Uitzonderingscode: c00000fd Uitzonderingsmarge: 0000000000043443 Versie van besturingssysteem: 10.0.18363.2.0.0.768.101 Landinstelling-id: 1043 Aanvullende informatie 1: a625 Aanvullende informatie 2: a62514fcf816511cba42b9c716df4c74 Aanvullende informatie 3: a6ad Aanvullende informatie 4: a6ad64229730ee9d403e8cdb1b6ef9c9 Extra informatie over het probleem Bucket-id: 273ca8313df8ae632a39b432d8c266d2 (1889739649136617170) Quote Link to comment
Vectorworks, Inc Employee Nikolay Zhelyazkov Posted May 11, 2020 Vectorworks, Inc Employee Share Posted May 11, 2020 Thanks @Eli van Hooff, If it crashes again look for a crash log file following the instructions from below. On 10/17/2018 at 5:51 PM, Nikolay Zhelyazkov said: You are working on Windows, right? If so, open your VW user folder at "<user name>\AppData\Roaming\Nemetschek\Vectorworks\2019\" and look for a .dmp file that was created when your VW crashed when opening TBManager. Quote Link to comment
Eli van Hooff Posted May 11, 2020 Share Posted May 11, 2020 @Nikolay Zhelyazkov Hereby: VWCrashDump.dmp.zip Quote Link to comment
Vectorworks, Inc Employee Nikolay Zhelyazkov Posted May 11, 2020 Vectorworks, Inc Employee Share Posted May 11, 2020 7 minutes ago, Eli van Hooff said: @Nikolay Zhelyazkov Hereby: VWCrashDump.dmp.zip You have attached a shortcut to the crash log. I cannot open this. The actual crash log file is required. Quote Link to comment
Eli van Hooff Posted May 11, 2020 Share Posted May 11, 2020 @Nikolay Zhelyazkov Ah sorry... Just forwarded what I got from my student... Here by the right version: VWCrashDump.zip Quote Link to comment
Vectorworks, Inc Employee Nikolay Zhelyazkov Posted May 11, 2020 Vectorworks, Inc Employee Share Posted May 11, 2020 17 minutes ago, Eli van Hooff said: @Nikolay Zhelyazkov Ah sorry... Just forwarded what I got from my student... Here by the right version: VWCrashDump.zip Seems like there is something wrong with this file, still cannot open it, sorry. Could you give me a test file and steps to reproduce the crash if possible? Thanks. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.