Avoid Creating VWTMP File

[Siva 0]

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

[PVA - Jim 2,381]

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.

[Siva 0]

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

[PVA - Jim 2,381]

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?

[Kevin McAllister 1,146]

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

[Decoyman 1]

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

[PVA - Jim 2,381]

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.

[bscavone 0]

Jim,

When are the changes coming?

We are experiencing this issue on a daily basis.

As you can imagine it is slowing down productivity.

[PVA - Jim 2,381]

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.

[ptoner 26]

This is still happening to machines in our office. Where these ever finally addressed?