Jump to content
Sign in to follow this  
Christiaan

Don't recommend 2013 SP2 if you use WGRing

Recommended Posts

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.

Share this post


Link to post

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.

Share this post


Link to post

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...

Share this post


Link to post
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.

Share this post


Link to post

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.

Share this post


Link to post

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 by P Retondo

Share this post


Link to post

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.

Share this post


Link to post

Christian,

I've not seen this yet, was this a VW2013 file to start or was it Batch converted from an older iteration?

Share this post


Link to post

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×
×
  • Create New...