Jim Terry Posted February 19, 2011 Share Posted February 19, 2011 I have a full up to date 2011 running on XP Pro that is fully updated. The crashes I have experienced are legion. I have never had a VW edition crash like this one. I have to save like avery 30 seconds because I don't know when the next will happen. It not only occurs on my desk top but on my laptop as well. All drawings all the time. Work arounds have included deleting the xml and lck files after the crash. This seems to give me a little more time. Of course tech support is closed until Monday. If I had my 10 disk here I would downgrade. HELP Quote Link to comment
Ray Libby Posted February 19, 2011 Share Posted February 19, 2011 Try updating your video drivers. It would help to have your computer specs to troubleshoot. Put that info along with your version of Vectorworks in a signature. Click on the my stuff link at the top, Edit Profile. Quote Link to comment
Jim Terry Posted February 19, 2011 Author Share Posted February 19, 2011 So computer info below. My laptop has a NVIDIA GeForce Go 7900 GS which has just been updated and it also experience crashes. Quote Link to comment
Ray Libby Posted February 19, 2011 Share Posted February 19, 2011 Thanks. Try uninstalling Quicktime and install the version on the Vectorworks DVD. Quote Link to comment
Jim Terry Posted February 19, 2011 Author Share Posted February 19, 2011 Anyway of getting that version somewhere else? I won't be near that install disk for awhile. Quote Link to comment
Ray Libby Posted February 19, 2011 Share Posted February 19, 2011 They do have older versions of Quicktime for download. I don't have an install disk so I don't know what version comes with it, maybe someone else can check. Quote Link to comment
Jim Terry Posted February 21, 2011 Author Share Posted February 21, 2011 Turned out I had my install disk with me. So far so good, but I haven't done any heavy lifting yet. Quote Link to comment
Jim Terry Posted February 25, 2011 Author Share Posted February 25, 2011 (edited) Crashed again. This time I just moved a unit. Quick fix, as usual, delete the Lightwright exchange files. In fact I just turned it off. I'll turn it on when I need it. Edited February 25, 2011 by Jim Terry Quote Link to comment
SAR Posted February 25, 2011 Share Posted February 25, 2011 I do not know it this will help, but I have had similar crash problems. Turning off the Lightwright exchange is the quick fix. I I was told by Kevin the problem is with symbols that have some how been saved as a lighting device within the symbol. He did have a script that fixed it, and said later service packs will address the issue. I still have occasional problems with SP2 even with the installed version of Quicktime. I am not sure if this is the same issue as you are dealing with. Steve Ross Quote Link to comment
Jim Terry Posted February 26, 2011 Author Share Posted February 26, 2011 I think that cuts closer to my problem than anything else. My symbols folder is a hodge podge of self created stuff and adapted stuff that has been with me since .mcd days. I think one of these days, I'll have to go into that folder and purge what I don't need (Studio Spot?????) and just redo all the ones that I use all the time. Not sure, though, why turning off Lightwright exchange solves the problem temporarily. Did not have this problem at all in 10. Quote Link to comment
michaelk Posted February 26, 2011 Share Posted February 26, 2011 I've had occasional problems with old symbols - created in VW 9, 10, 11, 12, '08, etc. (mostly my own, but occasionally a stock symbol) - causing problems like debilitating lags and crashes. Deleting the offending symbol or replacing the offending geometry in the symbol immediately made the program happy. Usually the problem was self-intersecting geometry (like a sweep or EAP) in the symbol that, perhaps, was tolerated in an earlier version but not in 2010 or 2011 (when these issues started coming up for me). Not sure what to make about Lightwright exchange solving the problem temporarily.... good luck mk Quote Link to comment
Jim Terry Posted February 26, 2011 Author Share Posted February 26, 2011 Not sure if turning off Exchange helps or not. I think it does. After 5 straight crashes, I deleted the .xml file and THAT is what stopped the crashes.... for awhile. My thought was that since Exchange creates the xml, why not just turn it off until I need it. So far, so good. Quote Link to comment
JBenghiat Posted February 26, 2011 Share Posted February 26, 2011 It's possible the XML file became corrupt, so Spotlight was trying to refresh Lighting Devices with impossible data. There also might be an issue with writing the file to disk. See if this thread is of any help http://techboard.vectorworks.net/ubbthreads.php?ubb=showflat&Number=151732#Post151732 -Josh Quote Link to comment
M T S Posted March 1, 2011 Share Posted March 1, 2011 how do find out which symbol or object is causing crash problems? I've restarted at least 19 times today!!! This SUCKS!!! Quote Link to comment
michaelk Posted March 1, 2011 Share Posted March 1, 2011 Duplicate the file. In the duplicated file - from the resource browser, delete one symbol at a time (starting with the accessories) and choose delete every instance of this symbol. After each deletion do whatever makes it crash. For me it's usually zooming or fly over. Rinse and repeat until you find it.... Good luck mk Quote Link to comment
StagemanGraham Posted March 9, 2011 Share Posted March 9, 2011 I've the same problems - only I'm not using data exchange. Crashes when I insert instruments. Sometimes the first, sometimes the 50th. Once the file crashes once, it's game over and I can't insert any symbols at all without it dumping. MACBOOK PRO OSX 10.6.6 6 GB Memory Quote Link to comment
SAR Posted March 9, 2011 Share Posted March 9, 2011 It may be a different issue, but just make sure that both radio buttons are unchecked in Lightwight exchange. Steve Quote Link to comment
John McKernon Posted April 17, 2011 Share Posted April 17, 2011 This definitely sounds like the lighting device-within-a-symbol problem. It's not directly related to Data Exchange, but it tends to be triggered whenever instruments are refreshed. It can happen if place a light on the plot using the instrument insertion tool, and then later select that light/lighting device and make a symbol out of it. What I wish I could remember is if SP3 for VW2011 fixes this. SP3 was released just a few days ago, if you haven't installed it yet you should do so ASAP. If SP3 doesn't fix it, the only cure is to find the symbol that has a lighting device contained within it and delete all instances of it from your drawing. Good luck! - John Quote Link to comment
Vectorworks, Inc Employee klinzey Posted April 18, 2011 Vectorworks, Inc Employee Share Posted April 18, 2011 The lighting device-within-a-symbol problem was fixed for SP2. There was a bug with Undo and the data exchange that was fixed with SP3. Quote Link to comment
TimOlson Posted April 22, 2011 Share Posted April 22, 2011 Hi Jim, this has happened with me also, most notably when I was using focus points with duplicate array. I lost several hours, always got to about the same point, when the file would crash. it would get to the point where all I would try to do is move one fixture and it would crash. out of desperation, I thought "maybe if I just go do something different for a while, it may clear up". and it did. I can't remember what exactly I did, but something in a viewport I think. I also stopped using duplicate array with focus points and with fixtures that were focused already, and that seemed to help. That problem was on a file imported from autocad; yesterday I had a file that originated in VW 2010 and did a (limited) amount of focus points by click/drag duplication and had no problem. I also need to scour my symbol folder - years and many rev's worth of symbols floating around in there. Peace, Tim O 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.