Flame host computer

[johnt]

Trying to open flame on my laptop in the office but the software keeps trying to connect onto a host computer’s framestore ie my desktop one. I cannot figure out how to switch it off and use the macbook’s internal framestore. Does anyone know how to?

[Sinan]

Two things here

1. You can select the host machine from the blue deop-down menu on the top left corner of the project management dialog, right under the Flame 202X version name.
2. But if you’re referring to the system trying to connect to other hosts during start-up, I’m also looking for a solution. My Linux system tries to connect to other Flame systems even if I don’t have any projects on those systems. Maybe I had at some point…

[allklier]

I found that the other day, and need to do it again as well. Let me find my notes.

[johnt]

yep i’ve looked at the blue drop down but it only shows me all the linux boxes and just ignores the internal framestore when I am in the office. When I am at home and out of the range of the wifi it works. And then if I try and run flame without wifi, then nothing.

@allklier - fingers crossed

I was trying to do a presentation this morning and nothing worked even though I had practised it at home - very frustrating.

[allklier]

That’s the thread I was thinking about…

Flame 2026 and cleaning up old storage

Thanks @Slabrie. Finally found it. But was still different. There were no old or stale files on my Linux machine. I checked every .cfg, cache, project folder. However, on my Mac, there was an older version of 2025.2.2 still installed. And it had three framestore partitions configured, two of which still existed, and one which was on a disk that is no longer with us. After removing the three framestore partitions from the sw config on the Mac, uninstalling the old 2025.2.2 version of Flame an…

There is probably a variable to turn this discovery off. The file in question is likely in /opt/Autodesk/cfg. As of 2026 there is no longer any S+W config in the setup tool.

But I just saw a terminal message fly by the other day that it was trying access a frame store on another system, even though all of mine are now 2026 and 2027.

Keep in mind that if Flame is installed, even if the app is not open, the S+W server processes are still in the background.

[allklier]

Others who manager bigger Flame fleets will know more about that and can confirm or correct…

One thing you can try. In /opt/Autodesk/sw/cfg, you can turn this variable to ‘false’

that should disable the auto-discovery. You may have to reboot for it to be picked up.

SelfDiscovery=false

When set to false, Flame will only look at the manually configured framestores in sw_framestore_map in the same folder, which by default is empty.

[johnt]

Can’t see a cfg file in sw - only a folder - inside only files with loads of hashtags nfo stuff. No selfdiscovery unfortunately. I also delteed all the cache - still not working - going home now - will look into it more later - must be something simple

[johnt]

Back at home and local host is available once more - gah

[PlaceYourBetts]

@ALan was posting about quality of life environment variables and there is one for ignoring remote gateways

setenv DL_WELCOME_SCREEN 0 #No annoying Welcome screen

setenv DL_STARTUP_LIBS_CLOSED 1 #Don’t try to load every Library upon Project opn

setenv DL_REMOTE_GATEWAY 0 #Hide MediaGateways. Show local devices only.

[ALan]

Yes, these are critical for our workflow. Note that post 2025+ the REMOTE_GATEWAY thing is non-applicable as that concept doesn’t even exists. Although we are unfortunately still running 2025.2.