Portable version of FF is still looking at the shared queue.yaml in appdata

FastFlix_6.2.1_win64.zip
Windows 11

Since I have multiple video cards I thought I'd try multiple simultaneous NVENC renders.

While this actually does work, both portable instances of FastFlix are trying to use the same queue.yaml file in appdata.

Surely portable versions should be making/using queue.yaml files in their own directories?

Start by locating the code that resolves the queue.yaml path and the portable-instance startup/configuration entry point. Reproduce the issue with two portable FastFlix instances and verify that each instance reads and writes a queue.yaml in its own directory, without sharing the AppData queue.

Written by the indexing model from the issue text.