I'm attempting to launch Fallout 3, via FOMM, using FOSE AND FPS Limiter. I was hoping to just override the normal FOSE launcher, with the command -fpslimit XX, but I get the "Failed to Launch: the system cannot find the file specified.
I've attempted just the command as above, fose_loader.exe plus the command, the entire directory and program and command, the command in quotes…
It might be very obvious, but how should I be inputting commands here?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Note how the path to the program is in quotes, but the arguments are not. If this still gives you problems, make sure that you have updated FOSE to the latest version (1.2) and that you installed FPS Limiter correctly (as far as I remember, fose plugins have a separate folder).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My command line that I entered is: "C:\Program Files\Bethesda Softworks\Fallout 3\fose_loader.exe" -fpslimit 50
Still, however, I get the cannot find file error. I'm using FOMM 0.9.15, FOSE 1.2b, and Fallout 3 1.7. I'm using the FOMM override default launch command line, under settings.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you are on Vista or 7, there are a lot of protection of the contents of the Program Files folder. You could try to allow fose_loader to run as an administrator (rightclick->Properties->Compatibility tab, check the checkbox that says "run as administrator"). If that does not work, you could install Fallout 3 to a folder ourside Program Files. If you plan on using a lot of mods (or making a few), I recommend that you do that. It will save you a lot of headaches.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
fomm doesn't allow command line arguments at the moment; everything you type in is interpreted as a part of the filename of the process to launch, even if you use quotes.
I've committed a change to fix it, so you can do it if you either rebuild fomm yourself or wait for 0.9.18.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm attempting to launch Fallout 3, via FOMM, using FOSE AND FPS Limiter. I was hoping to just override the normal FOSE launcher, with the command -fpslimit XX, but I get the "Failed to Launch: the system cannot find the file specified.
I've attempted just the command as above, fose_loader.exe plus the command, the entire directory and program and command, the command in quotes…
It might be very obvious, but how should I be inputting commands here?
I've not used FPS limiter, but from your description, I would expect the commandline command to be something like this:
"C:\Games\Fallout 3\fose_launcer.exe" -fpslimit 60
Note how the path to the program is in quotes, but the arguments are not. If this still gives you problems, make sure that you have updated FOSE to the latest version (1.2) and that you installed FPS Limiter correctly (as far as I remember, fose plugins have a separate folder).
My command line that I entered is: "C:\Program Files\Bethesda Softworks\Fallout 3\fose_loader.exe" -fpslimit 50
Still, however, I get the cannot find file error. I'm using FOMM 0.9.15, FOSE 1.2b, and Fallout 3 1.7. I'm using the FOMM override default launch command line, under settings.
I would expect this part to be your problem:
*C:\Program Files*
If you are on Vista or 7, there are a lot of protection of the contents of the Program Files folder. You could try to allow fose_loader to run as an administrator (rightclick->Properties->Compatibility tab, check the checkbox that says "run as administrator"). If that does not work, you could install Fallout 3 to a folder ourside Program Files. If you plan on using a lot of mods (or making a few), I recommend that you do that. It will save you a lot of headaches.
I'm still functioning on Windows XP, but I'll see if that works out.
Still no go. I can't seem to get a working response no matter what I've inputted into the command line.
fomm doesn't allow command line arguments at the moment; everything you type in is interpreted as a part of the filename of the process to launch, even if you use quotes.
I've committed a change to fix it, so you can do it if you either rebuild fomm yourself or wait for 0.9.18.