Re: [Nuke-users] Windows Mapped Drive Letters vs \\ network paths

We still do delay adding them, for exactly that reason. And we have explorer open up the root of those mapped drives on startup, because sometimes if you re-add an existing share it doesn't really gell properly and you end up with the little red x. If you just double click it (or launch explorer

Re: [Nuke-users] Windows Mapped Drive Letters vs \\ network paths

I asked over on SSA and there's not really a definitive answer on mapped vs unc yet, when it comes to Nuking. They all seem to be mostly over it, so it could have went extinct as a problem along the way or been specific to certain environment combinations. I still map as a "best practice" even

Re: [Nuke-users] Windows Mapped Drive Letters vs \\ network paths

Hi Andrew. A friend of mine wrote an article about how to deal with mixed environments. It’s written for nuke 6 but it should probably point you in the right direction. https://fredrikaverpil.github.io/2011/10/28/nuke-63-small-studio-setup-for-windows-osx/

Re: [Nuke-users] Windows Mapped Drive Letters vs \\ network paths

Back in the day UNC paths were much slower then mounted drive letters for reads. I have no idea if this is still a thing with Windows 10. This is probably a good question for the studio sysadmins mailing list. On Thu, Dec 1, 2016 at 1:38 PM, Andrew Mumford wrote: > I'm in a

[Nuke-users] Windows Mapped Drive Letters vs \\ network paths

I'm in a small mixed windows / mac shop are there any caveats to using full //network paths vs mapped drive letters ? Thx --- Andrew Mumford ___ Nuke-users mailing list Nuke-users@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/