Siva Posted February 4, 2014 Share Posted February 4, 2014 Sometimes when I save my file it creates an additional file with VWTMP extension. How can I avoid this? My files are saved on server. Thanks. Siva VW 2014 Architect Imac Intel 10.8.5 Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted February 4, 2014 Vectorworks, Inc Employee Share Posted February 4, 2014 These files are part of the autosave/backup process and usually are only present when the files are open. The files are normally hidden but visible in some circumstances. You do not need to worry about these files, only the VWX file. Quote Link to comment
Siva Posted February 5, 2014 Author Share Posted February 5, 2014 Thanks Jim, the problem I have is with this VWTMP existing, whenever I tried to save my file, I get a message "The file save operation failed. Please try again, or save to a different location". I have to save as and replace the original file or manually have to delete this VWTMP file. Siva VW 2014 Architect Imac Intel 10.8.5 Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted February 6, 2014 Vectorworks, Inc Employee Share Posted February 6, 2014 If you save your files locally to the desktop, does the same behavior occur and generate the same TMP file? Or does it only happen when saving to a server? Is the server actually a server or is it another Mac/PC or an NAS device? Quote Link to comment
Kevin McAllister Posted February 6, 2014 Share Posted February 6, 2014 It sounds like you've had an out of memory error caused by Sheet Layer Viewport rendering. It often leaves a remnant VWTMP file. Do you have a lot of complicated Sheet Layer Viewports in the file. It may not be related to working off your server. Kevin Quote Link to comment
Decoyman Posted February 7, 2014 Share Posted February 7, 2014 I get the same problem. Every time I render a sheet layer viewport using Open GL the out of memory error occurs. I'm working on an extension to an individual house - nothing complicated. There are three SLVs in the file which are rendered in this way, but it only takes rendering the first one of them to trigger the problem. Why?! I'm using VW 2014 SP2 on a 17" MacBookPro, 2009 vintage. Rob Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted February 7, 2014 Vectorworks, Inc Employee Share Posted February 7, 2014 If its hitting Out Of Memory, that can definitely happen. Once an OOM error occurs, (and in a few other circumstances) Vectorworks creates this type of file to avoid losing geometry within the file itself. It is annoying, but better than losing work. This can then be resolved by saving to a new location or with a new filename. To be clear, this isn't that you are hitting your machine's maximum memory, but the amount of memory that Vectorworks itself can use. Renderworks modes likely aren't seeing the problem as it can use a huge amount of RAM, but Vectorworks itself, which runs OpenGL, is still limited to effectively ~3.5 GB. This is currently how it works, but will not be for very long as a number of large changes are incoming to address limitations like this. Quote Link to comment
bscavone Posted May 2, 2014 Share Posted May 2, 2014 Jim, When are the changes coming? We are experiencing this issue on a daily basis. As you can imagine it is slowing down productivity. Quote Link to comment
Vectorworks, Inc Employee PVA - Admin Posted May 2, 2014 Vectorworks, Inc Employee Share Posted May 2, 2014 I have not been given official dates as of yet. I assure you that the moment I am, I will be posting about it. Vehemently. Quote Link to comment
ptoner Posted August 8, 2019 Share Posted August 8, 2019 This is still happening to machines in our office. Where these ever finally addressed? Quote Link to comment
EParks Posted June 28, 2021 Share Posted June 28, 2021 (edited) I have this issue and it is causing major disruption. I have tried saving copies to new locations; rmeoving as many veiwports as possible; rmeoving as much other data hungry items too and still the files in question become almost unusable and crash regularly. This appears to have been an issue for well over 10 years (if going by the dates in other threads that cover the same issue. Has there been any useful feedback from Vectorworks on how to resolve this? Edited June 28, 2021 by EParks 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.