Hi everyone!
Currently running Flame2026.2.1 on MacOS Sequoia 15.7.3.
Flame is not auto mounting hosts that are in my /etc/auto_direct file at all? I have reviewed the Flame 2026-Project Sharing Guide and have verified all pathways are configured to my external raid drive (connected via thunderbolt). All hosts are MacOS.
# Symbolic links
/mnt/flame_host-1/projects
/System/Volumes/Data/Volumes**/MY_RAID_SSD/Flame2026-2-1/projects**
/mnt/flame_host-1/media
/System/Volumes/Data/Volumes/**MY_RAID_SSD/Flame2026-2-1/media
### flame_host-2** is configured the same way**!
Modified /etc/exports :
/System/Volumes/Data/**mnt/flame_host-1/projects** /mnt/flame_host-1/projects -network 192.168.0.0 -mask 255.255.255.0
/System/Volumes/Data/**mnt/flame_host-1/media** -network 192.168.0.0 -mask 255.255.255.0
/etc/auto_master :
/etc/auto_direct:
/mnt/**flame_host-2**/projects -acdirmin=0,acdirmax=0 192.168.0.11:/mnt/f**lame_host-2**/projects
/mnt/**flame_host-2**/media 192.168.0.11:/mnt/**flame_host-2**/media
But also, Is there a difference between exposing /System/Volumes/Data/mnt/flame_host-2/projects etc versus using the symbolic link /mnt/flame_host-2/projects like the example above?
Inside the Flame UI, I see the flame_host-2 but nothing shows up underneath.
But if I manually create the flame_host-2 directory in flame_host-1 and manually mount it I am able to get to the remote host shared libraries.
# flame_host-1
mkdir /mnt/flame_host-2/projects
mkdir /mnt/flame_host-2/media
# Manual nfs mount command:
sudo mount -t nfs -o resvport 192.168.0.11:/mnt/flame_host-2/projects /System/Volumes/Data/mnt/flame_host-2/projects
sudo mount -t nfs -o resvport 192.168.0.11:/mnt/flame_host-2/media /System/Volumes/Data/mnt/flame_host-2/media
Autodesk Network :
Project View (of flame-host-1):
Empty Project:
