07-18-2021, 07:19 PM
I use FSUIPC to start some programs I need running after P3D is started and decided to have it run the various FS KeyPad files. I added the information copied from a shortcut to the fsuipc.ini RUN section.
Run2=READY,CLOSE,C:\Users\Brett\AppData\Local\FS-Keypad\FS-Keypad.exe "C:\Users\Brett\AppData\Local\FS-Keypad\Keypads\303df744-c367-4681-a409-4ac2f187b39e.json"
However, this failed to run with an error 267 from Windows. I then wrote a Powershell script to do some testing and found that as long as I change to the FS-KeyPad directory (Local/FS-KeyPad) that command line will work. However, if I ran the script from another directory it failed to run the FS-KeyPad.
It appears that despite the fact FS-KeyPad is given the entire path to the JSON file it only uses the filename and assumes it's in the Keypads directory so it can't find it unless you change to the FS-Keypads directory. The shortcut works because the working directory is given so it effectively does the change to the directory.
I know this is a minor issue and I'm working around it by giving FSUIPC the powershell script to run it but it would be nice at some point to be able to add the command line as shown above to FSUIPC without having to create a script.
Run2=READY,CLOSE,C:\Users\Brett\AppData\Local\FS-Keypad\FS-Keypad.exe "C:\Users\Brett\AppData\Local\FS-Keypad\Keypads\303df744-c367-4681-a409-4ac2f187b39e.json"
However, this failed to run with an error 267 from Windows. I then wrote a Powershell script to do some testing and found that as long as I change to the FS-KeyPad directory (Local/FS-KeyPad) that command line will work. However, if I ran the script from another directory it failed to run the FS-KeyPad.
It appears that despite the fact FS-KeyPad is given the entire path to the JSON file it only uses the filename and assumes it's in the Keypads directory so it can't find it unless you change to the FS-Keypads directory. The shortcut works because the working directory is given so it effectively does the change to the directory.
I know this is a minor issue and I'm working around it by giving FSUIPC the powershell script to run it but it would be nice at some point to be able to add the command line as shown above to FSUIPC without having to create a script.