Does anyone know why it takes a hundred times longer to save a file over a network as opposed to saving the file directly to you local HD (and then copying it over the network)?? Was hoping Vue 5 Infinite might finally address this.......but nope?? Has anyone had similar experiences or know of a setting in vue to aid this issue? PS.....ecosystems rock!!!

I should clarify that this is only with the actual .vue file. Saving renders over the network takes just a second.

.vue compared final renders (jpg i assume). Look at the file sizes to understand the differences in speed. I think it is as simple as that. Saving over a network. This phenomen i know since the early days of networking. I guess it has to do with memory allocation. What the operating system probably has to do is, to save the file temporarily on your local disk and then start the network copy functions (with less memory maybe even because the major application allocates a lot of memory already). Instead of having it on your local disk already and do it directly when you do it as a system function. What i learned as well is that saving over a network can be a dangerous thing. Another source for potential coruption of files i would say. What happens when the network connection breaks down in the middle of the saving mode? What happens when the other computer crashes by any reason? A lot of extra danger i would say. Especially when you have different file systems even (I have a network of Macs and Windows PCs). So i stay with the classical way. Save it locally and transfer it then manually to another computer.

Just to add to what wabe is saying, I think Vue does a lot of calculation during the save scene process. For example, populate a large (6000x6000) procedural terrain with an ecosystem. The file size might be around a few hundred mb. But you'll notice that even if saved locally it takes quite a long time to save a file of that size, far longer than you would expect if it was just writing to the disk. This is because I believe Vue is also calculating/saving out the location/coordinates for each ecosystem object. From what I've observed this is done as it is saved, and I'm assuming the data is appended to the vue scene during the process. Now, do this over a network and you've probably got relatively small packets being sent. As such each one is not taking advantage of the full bandwidth of your network, but it is being slowed down as opposed to writing to a local disk. I also believe it's probably done this way to save memory. As if you had to pre-calculate all this stuff before the save you could quite possibly run out of memory then. Please note this is just my assumptions on the matter, but I do know for a fact that Vue reads in each ecosystem coordinate when you load a scene, which can be far longer than the corresponding scene save, so it's safe to say that it is also saving each coordinate. Hope that helps.