Fusion 20 sometimes takes forever to open open/save dialogs

I wonder if anyone else noticed this. Fusion 20 (final version) sometimes takes forever to open the open dialog, and the same thing for savers. By forever I of course mean about 20 or 30 seconds, which is an eternity.

But sometimes it doesn't do it at all, it's instant as it's always been. And this happens at random. Right now I can't get it to work fine, but sometimes I just close Fusion Studio, open it again and it's fine. Other times, it takes a reboot.

Has anyone noticed this? This is on Windows 11, I haven't used Fusion much on my Mac lately.

Do you have either a synology NAS or other network paths on your system?
This is a pretty well documented (but annoying) issue with the open/save file dialogs.

Do you have either a synology NAS or other network paths on your system?
This is a pretty well documented (but annoying) issue with the open/save file dialogs.

No NAS, I have some drives on my Mac mapped as network shares.

This could be part of the issue. I think if you search on this forum, you will find a couple of similar topics with possible solutions.

It usually happens when there's a file path in your history that's no longer connected--as Sander mentioned, a NAS that isn't currently awake, or maybe you've accessed a removable drive at some point, and Fusion's waiting to see if that drive will appear when requested.

You can also get slowdowns if the file requester history is simply very long, even if all of the resources are still connected. It usually takes a while for that to happen, though.

You can clear the recent files lists with the script "Delete File Requester History" available in Reactor. It clears all* of the recent file lists from the preferences. *It's been a while since the script was last updated. There may have been additional file history fields added to the prefs that didn't exist when I made it.

Thanks, guys. I installed that fuse, but it didn't do anything. I think it might be the network shares, since now I have the Mac turned off, but it was on all weekend and I didn't have this problem.

But I'm going to email BMD about, this shouldn't happen. It's not like I was trying to open a comp that had loaders pointing to those shares, so why would it need to take 30 seconds to even show the open dialog?

You have to do more than just install it. You have to run the script!

You have to do more than just install it. You have to run the script!

Sorry, I should've clarified. Obviously I installed, then ran the script. I know it worked because after running it, the recent files menu item was empty. But adding a loader to a new comp, or clicking browse on one that was already there, or a saver, ended up stalling Fusion anyway.

But yes, the problem lies in having my Mac shares as drives in Windows 11. My Mac had been off since last night. I just loaded Fusion Studio, clicked on the loader button, and it stalled for 20 seconds or so. Just to test this better, I closed it, then opened Fusion Studio again. Clicked on the loader button. Again, 20 seconds thinking "Should I give this guy the loader, or make him wait? Let's make him wait".

So I closed FS. Turned on the Mac, logged in, waited a minute to make sure the shares were showing in Windows. Opened Fusion Studio, clicked on the loader, browse dialog came up instantly.

I'm not unfamiliar with this kind of behavior, but usually I see it in the OS. It always puzzled me that both Windows and macOS (and I'm talking Mac OS from the 90's, Mac OS X, and macOS) go on a trance for like 30 seconds or more when they need something from the network and the network doesn't respond. I think it's fine to put some kind of timeout because sometimes the network is too busy, but why more than 5-10 seconds? I never understood that.

But well, it's not the end of the world. All it takes is to have the Mac on, but at least it's a Mac, so it doesn't consume much power. Now, if BMD would fix the Decklink Mini Monitor 4K not working in Fusion Studio, that would be orange fanta-stic.

Well, my NAS takes about 20 seconds to wake up, so a long wait is fine by me. But if it's still doing that, then it's either not the MRU lists causing the problem, or there's an additional list that the script doesn't know about. As I said, it's pretty old. You could scan through your preferences file to see if there are still file paths in there after the script has been run to find out