Christiaan Posted November 29, 2012 Share Posted November 29, 2012 Updating workgroup references with VW SP2 crashes VW in our office. Quote Link to comment
P Retondo Posted November 29, 2012 Share Posted November 29, 2012 Christiaan, just about to install SP2, thanks for the tip! Have you reported this to quality control? NNA, are you going to evaluate and let us know if this needs to be fixed and when? SP2 has a ton of bug fixes, some of which are important to me, but when someone like Cristiaan says it doesn't work, we pay attention. Quote Link to comment
Christiaan Posted November 29, 2012 Author Share Posted November 29, 2012 Pete, I haven't had a chance to submit a bug report yet. Made the stupid decision of applying this update while I'm on a deadline. I've only tested this on one project but SP2 definitely triggered the problem with this file. I was able to update the references with SP1 on another machine and I resolved matters on my machine (and another) by reverting them back to SP1. You could test it yourself by duplicating your VW application folder and applying the update to just one of them. Quote Link to comment
Vectorworks, Inc Employee Tamsin Slatter Posted November 29, 2012 Vectorworks, Inc Employee Share Posted November 29, 2012 Christiaan I am able to update referenced files(design layer viewport) in SP2 without a problem. Quote Link to comment
Christiaan Posted November 29, 2012 Author Share Posted November 29, 2012 Thanks Tamsin. Was yours a fresh WGR or existing one? Quote Link to comment
Vectorworks, Inc Employee Tamsin Slatter Posted November 29, 2012 Vectorworks, Inc Employee Share Posted November 29, 2012 Existing - and the file originated in 2012, has been through the pre SP1 crashing issues, but is absolutely fine now. I think something else may be causing your crash... Quote Link to comment
Christiaan Posted November 29, 2012 Author Share Posted November 29, 2012 I think something else may be causing your crash... It was definitely a combination of my files and SP2. SP1 could update the reference fine. SP2 failed every time. Quote Link to comment
P Retondo Posted November 29, 2012 Share Posted November 29, 2012 Christiaan, don't know if I want to go through what you're going through! Let us know if you get to the point of understanding what combination of factors triggers the problem. Quote Link to comment
Christiaan Posted November 30, 2012 Author Share Posted November 30, 2012 Bug submitted Pete, we'll see what VSS UK think. Quote Link to comment
Christiaan Posted November 30, 2012 Author Share Posted November 30, 2012 Bug verified by VSS UK. Passed onto Nemetschek as high priority. Quote Link to comment
P Retondo Posted December 12, 2012 Share Posted December 12, 2012 (edited) I just noticed some weirdness with WGR in 2013 SP1, in a set of files migrated from 2012. Updating an existing reference resulted in a whole series of naming conflicts. The conflicts were between resources in the target document ("Plan") and the same names that existed in the referenced document ("Kitchen") as "groups." Why there are hidden names of groups I don't know. I aborted the update, which did not cause a crash, and cured the problem by: 1) deleted the reference to "Kitchen" in "Plan"; 2) deleted the circular reference in "Kitchen" that showed the floor plan layer from "Plan"; 3) recreated the reference to "Kitchen" in "Plan," no problem experienced; 4) recreated reference to "Plan" in "Kitchen." So far, no problem with all that, and no naming conflicts. Edited December 12, 2012 by P Retondo Quote Link to comment
dominekarch Posted January 8, 2013 Share Posted January 8, 2013 Does anyone know if NNA has any response to this. It's causing big problems for our workflow right now. Switched to 2013 SP2 last week. Woops. Quote Link to comment
Christiaan Posted January 29, 2013 Author Share Posted January 29, 2013 The workaround for this problem is to also have the referenced file open when updating the file. Quote Link to comment
Jim Smith Posted January 29, 2013 Share Posted January 29, 2013 Christian, I've not seen this yet, was this a VW2013 file to start or was it Batch converted from an older iteration? Quote Link to comment
Christiaan Posted January 30, 2013 Author Share Posted January 30, 2013 The original file started in v2012 Jim. 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.