Jump to content

Mark Farnan

Vectorworks, Inc Employee
 View Profile  See their activity

  • Posts

    112

  • Joined

  • Last visited

 Content Type 

Posts posted by Mark Farnan

    zoom VW 2008

    in General Discussion

    Posted

    Hi Gavin,

    I can reproduce this on monitor 2 (only) if I am using two monitors and monitor 2 is positioned to the left of monitor 1. Do you have your monitors set up like this?

    Unfortunately I don't see any nudge problems in any case.

    Mark

    VW 2008 - Symbol Referencing buggy?

    in General Discussion

    Posted

    Hi Chris,

    For your update problem, the first 2 things that come to mind are:

    1. Did you save the source file before you updated? (Does the Nav Palette show it as out of date?)

    2. Maybe there's a refresh bug? If you move the symbol that didn't appear to update, does it then suddenly update?

    Regarding your four items:

    1. You're so right. We'll look to do that.

    2. That's a trickier one. Do we do that for all referenced resources? Does that run the risk of complicating the drawing for users who don't really care? Maybe just doing #1 above would be enough?

    3. I agree that we can do better than a "Selection is Locked" message there.

    4. We don't have that because there's currently no way to just update that symbol definition without updating everything else in the file. So the command would actually be "Update the reference to the file that contains this symbol definition." But your point is well taken - we'll think about how we might be able to address that.

    Thanks for your thoughts here and in the Wish List Items area.

    Mark Farnan

    Core Technologies Manager

    Nemetschek NA

    Zero K file corruptions on the Mac in VW 12.5.2

    in General Discussion

    Posted

    Hi everyone,

    We thought that we had successfully addressed all of the zero K file corruptions issues in 12.5.2, but we have found another variation. We think this variation is much less common because the set of users who we were working with last spring who were experiencing these types of problems in 12.5.1 have not reported recurrences using their regular workflows in 12.5.2.

    Regardless, our current reproducible case is: if you have multiple VectorWorks files open and you activate a VectorWorks file from the dock, do anything or nothing with that file, then send that file back to the dock, then save what appears to be the new active file without clicking on it (using manual save or Autosave), the corruption will occur.

    If you work in such a way that you think you might encounter the problem described above, we recommend that:

    a. If you save a file immediately after sending a different file to the dock, click on the file you want to save first.

    b. If you use Autosave, and sending files to the dock is part of your workflow, consider changing your Autosave settings to:

    - Autosave to a backup file.

    - Autosave by number of operations rather than by number of minutes.

    Rest assured that in the next release, this problem will be fixed and there will be new safeguards in place to prevent the overwriting of existing files with zero K or otherwise corrupt files.

    Sincerely,

    Mark Farnan

    Core Technologies Manager

    Nemetschek NA

    A question for those with corruption issues

    in General Discussion

    Posted

    Hi everyone,

    I think the problem is that everyone who has tried to use this download so far is using a dongled version. I have posted a new application that works with dongled versions here:

    http://download2.nemetschek.net/seed/VW69163b.zip

    So, the new instructions are:

    --------------------------------------------------

    For those of you who need immediate relief from the zero K file corruption problem, you can download a beta version of the VectorWorks application that fixes the problem.

    The use this new application, please follow these steps:

    1. Rename the VectorWorks application that is currently in your 12.5.1 VectorWorks folder from ?VectorWorks? to ?VectorWorks ? orig?

    2a. If you are using a non-dongled version of VectorWorks, download the following file: http://download2.nemetschek.net/seed/VW69163.zip

    (Use this file if you don't know what a dongle is.)

    2b. If you are using a dongled version of VectorWorks, download the following file: http://download2.nemetschek.net/seed/VW69163b.zip

    3. Unzip the file to get the new VectorWorks application.

    4. Drop the new VectorWorks application into your 12.5.1 VectorWorks folder.

    Please let us know if you see any evidence that this new application does not completely fix the zero K file corruption problem.

    --------------------------------------------------

    Maybe someone with a fast internet connection could download this dongled version and confirm that it runs ok, then post to this thread with a confirmation.

    Thanks,

    Mark

    A question for those with corruption issues

    in General Discussion

    Posted

    Hi everyone,

    Let's try this again.

    For those of you who need immediate relief from the zero K file corruption problem, you can download a beta version of the VectorWorks application that fixes the problem.

    The use this new application, please follow these steps:

    1. Rename the VectorWorks application that is currently in your 12.5.1 VectorWorks folder from ?VectorWorks? to ?VectorWorks ? orig?

    2. Download the following file: http://download2.nemetschek.net/seed/VW69163.zip

    3. Unzip the file to get the new VectorWorks application.

    4. Drop the new VectorWorks application into your 12.5.1 VectorWorks folder.

    Please let us know if you see any evidence that this new application does not completely fix the zero K file corruption problem.

    Thanks,

    Mark

    A question for those with corruption issues

    in General Discussion

    Posted

    Hi everyone,

    For those of you who need immediate relief from the zero K file corruption problem, you can download a beta version of the VectorWorks application that fixes the problem.

    The use this new application, please follow these steps:

    1. Rename the VectorWorks application that is currently in your 12.5.1 VectorWorks folder from ?VectorWorks? to ?VectorWorks ? orig?

    2. Download the following file: http://download2.nemetschek.net/seed/VW69097.zip

    3. Unzip the file to get the new VectorWorks application.

    4. Drop the new VectorWorks application into your 12.5.1 VectorWorks folder.

    Please let us know if you see any evidence that this new application does not completely fix the zero K file corruption problem.

    Thanks,

    Mark

    A question for those with corruption issues

    in General Discussion

    Posted

    Junker,

    A fix is in the works but we still have more work to do on it. I'm sorry I can't give you timeframe at this point.

    But with some care on your end this problem should not still be "haunting" you. Are you using Expose a lot? If so that might be what's going on. If not and if you're following the recommendations I listed above and you're STILL having problems, please let me know.

    Thanks,

    Mark

    A question for those with corruption issues

    in General Discussion

    Posted

    dr paaj,

    If the corrupt files are zero K then it certainly sounds like you are experiencing the file corruption problem that has been identified in this thread. I'll post our recommendations again because they've changed slightly as we've learned more:

    Our investigation so far has shown that the problem happens when you minimize a VectorWorks document or use Expos? to activate a document, then immediately save. If you minimize a VectorWorks document or use Expos? you may notice that the data bar and mode bar of the newly activated document are not displayed. THIS is when the problem happens. If you don't click on that document to fully activate it, any save you do can or will cause the partially activated document to become zero K on disk.

    Another point to note: when you get the "An error occurred while saving this file. This file is now corrupt on disk. Try saving to a different location..." message, you may find that you are unable to save to a different location (the error dialog will just keep coming up). In this case, try clicking in the document that you are trying to save, and then save to a different location.

    At this point we would advise Mac users to make sure their Autosave is saving to a backup folder and to not minimize VectorWorks documents or use Expos? to activate documents.

    We are testing a possible solution to this problem and hope to get the fix in the hands of our users as soon as we can.

    Mark

    A question for those with corruption issues

    in General Discussion

    Posted

    Hi Donald,

    I don't doubt that there are more anomolies when you put documents in the dock. We've made good progress on our investigation and have found that we are not always fully activating the document that should be activated. I wouldn't be surprised if apple-tilde and maybe other actions that activate documents might cause similar problems.

    Thanks for all of the clues.

    Mark

    A question for those with corruption issues

    in General Discussion

    Posted

    Hi everyone,

    Here?s more information on the zero K file corruption problem:

    Contrary to our initial suspicions, it now looks like "open files that are not yet saved to disk" don?t have anything to do with the corruption.

    The problem appears to happen when you minimize a VectorWorks document and then immediately save.

    In VectorWorks 12 on the Mac when you have more than one VectorWorks documents open and you minimize one of them you'll notice that the data bar and mode bar of the newly activated document are not displayed. THIS is when the problem happens. If you don't click on that document to fully activate it, any save you do that doesn't involve clicking on that document (like through Autosave or if you use cmd-s) can or will cause the partially activated document to become zero K on disk.

    It is still true that if you get the "An error occurred while saving this file. This file is now corrupt on disk. Try saving to a different location..." message, you may find that you are unable to save to a different location (the error dialog will just keep coming up). In this case, try clicking in the document that you are trying to save, and then save to a different location.

    At this point we would advise Mac users to make sure their Autosave is saving to a backup folder and to not minimize VectorWorks documents.

    We are continuing to investigate how to best fix this problem and get it in the hands of our users.

    Thanks to everyone for helping us reproduce this problem.

    Mark

    A question for those with corruption issues

    in General Discussion

    Posted

    Hi Everyone:

    We have been losing files also (on PC's) ... You work on a drawing and when you go to save (or autosave) when you're done the file is gone from the drive that you are working from...

    Hi Tom,

    This is more of a missing file problem than a file corruption problem. To my knowledge we have no other users reporting this behavior. We'll do some testing here - please let me know if you get more clues. You may want to move at least a couple of your machines back to the previous version of Explorer to see if that helps.

    Mark

    A question for those with corruption issues

    in General Discussion

    Posted

    As for the PDF issue, I've figured out that if you are saving over an existing file, then you either after to rename it or delete the existing file first... otherwise you get a PDF with 0kb... another fabulous feature.

    Graham, I'm not seeing this on my G5 running MacOS 10.4.8. Are you running 10.3.9 like Donald is?

×
×
  • Create New...