Houston, we have a problem! Saving to our network takes 10 minutes, when saving locally takes seconds. I.T. says it is how MAX saves, in little chunks, and the network (Linux) doesn’t like that. Is there a MAX setting that might help?
Is it possible to save it in lacally, and then copy the file and paste into server?
That’s nonsense. Saving to fast nas should be similar in speed to saving to local disk. We never have any speed issues like that. Its probably something the way things are configured on the server end. Can you copy large file over to network and back and see the speed? if it’s fast it should be saving fast as well.
That sounds like a pain. Saving locally we turn off file compression because while it saves space, it’s slower. However if you are having a slow network issue it might be better to try file compression on. Worth a try if you cant work locally and back up to the server. But it’s clearly a network issue.
I used to have a lot of issues with network paths that didn’t exist. Try to strip the paths of anymissing assets, as above turn off file compression, and disable the setting that creates a thumbnail for the save file.
The I.T. folks have a lot of security on our server; I am talking Fort Knox lever security. I’ll try compression and cleaning up paths. I save locally, but the team isn’t very experienced, so that would be a nightmare.
Compression didn’t help. it is the 85% spot that stalls.
max up to date? remember there were some issues with the chamfer modifier a while back IIRC correctly.
We are on MAX 2024 :(. I’ll see if there is an update for it. It stalls out at 84% (3-4 minutes and sometimes much longer), so I would be interested in knowing what happens at that point of the same process.
use modmodzorb to find chamfer modifiers and remove them or collapse them. could be the culprit.
I have sometimes had scenes where TyFlow would want to recalc when saving and it wouldn’t always show its status. If you have any TyFlow objects try setting to disabled.
Otherwise we save to network every time and don’t have big slowdowns. I mean it’s not like saving to a local fast nvme, but it’s typically seconds even for big scenes. And the automatic snapshots and mirroring to a backup server make it well worth it.
Maybe try a different network cable. Especially if your network is 10Gig+ a bad cable can cause slowdowns, yet otherwise seem to work.
Test client to server with iperf3.
That’s actually a good advice, I would take it further, if you are in the office try the same from other machines/workstations, do other people have this issue? if yes then its def network/storage related. If no, you prob have an issue connecting to the network.
I tried different cables and ports. It seems to be happing to all of our users. The scenes they were using was light, but my scenes, the ones they are now using is heavier. Still, it should save just as fast as it is locally.