For people like me who spent an age trying to figure out how to get this to work:
Extract the initial FO3Plugin v 1.whatever to some sorta file. Open that file.
Don't use the FO3Plugin shortcut. The Winrar file is what you want to use. For people who have their s#*! set up like I do, double-clicking won't run the program but will bring up that little Winrar window, which is probably what led to the confusion on installing. To get the program to work ensure you have Java then right-click the .jar file (which shows up as a winrar file) and go to "Open with" and choose "Java(TM) Platform SE Binary" (or something along those lines. I'm just going with what shows on my pc).
Hopefully this will help someone! (And on the off-chance the creator sees this, thanks for the resource! Once I finally figure out how to work it it was really helpful :) )
Long story short, I'm using mods in PlayStation 3, I need to merge mods because it can only load 3 extra esp files. I don't have a PC, only a raspberry pi, which runs Linux Debian and have Java 8.
When I tried running the jar I got this error:
Exception during program initialization
Java.io.io.exception: cannot run program "reg": error=2, file or directory not found.
A full picture of the error (as its too long to type it): https://imgur.com/a/aEFOBwc
Prime example of a good program with really bad coding in the UI department there is no menu option to do this. So far the only way to reset the application is to delete its config files in your application data folder
Open a new explorer window and type this into the address bar
When I merge two different ESP and one is over writing the values of the other, FO3 Edit will state that it is going to attach a 'z' to the end of a new entry.
An example being that I am trying to take the 12-15 XFO 84b .esp's and make my own merged entry. So there was an original entry and I want it to overwrite that entry with the value from the second ESP. But instead of a merge I now have the following:
SPEL record: WearingDown (0100080F) - Wearing Down (the weapon durability wear down rate) SPEL record: WearingDownZ (01A62760) - Wearing Down (the merged value, but notice the different hex address and the 'z' at the end)
What does the Z mean? Is that FO3Edit's mechanism for showing that it is going to overwrite the old entry? Did it leave the original value alone and create a second entry that will not over write the first?
My guess is that FO3 cannot over-write a value with an identical entry from another ESP with a different value?
After much pain and suffering, I finally got this program working in Windows 7 x64. Mind you, this is how it worked for me. Your Mileage May Vary. :^)
1. At first, the program wouldn't pick up the path to the javaw.exe file C:\WINDOWS\System32. *Remembering that I'd installed 64Bit Java, I redirected the program to look for it in the: C:\Program Files\Java\jre\bin file. So the path to javaw was set to: C:\Program Files\Java\jre\bin\javaw.exe. Problem solved.
2. The second problem I faced was the program not finding the plugins. *Huh?* o.O *This was resolved by following the guidelines in the ReadMe for setting the path which was accomplished with: -DFallout.plugin.path=C:\Program Files\Bethesda Softworks\Fallout 3\Data. * One would think this would take effect right away... It didn't. After a few choice words and a little patience, I restarted the program and voila!... It worked.
Ultimately, the Properties of the FO3Plugin shortcut looked like this:
Start In [ C:\Program Files\Bethesda Softworks\Fallout 3\Plugin Editor ] *This is where I extracted the program file.
# Caveat: Yes, I installed the game in the traditional 32 bit Program Files path. Why? A. I remembered a lesson learned from installing Oblivion in the: Program Files(x86) directory and having my modified plugins (which were still referencing the traditional path) not work. B. I think the C:\Program Files(x86) path is lame and causes more problems than it resolves. Having said this, I do allow all other 32bit apps to install to that directory because frankly, a 32 bit program will either work/or not in a 64bit environment. I use the traditional path primarily for games.
In any event, I hope my experience helps some of the others out there having problems with getting this program to work and like many others, I give it a health endorsement. So long as it works. ;^)
91 comments
Extract the initial FO3Plugin v 1.whatever to some sorta file. Open that file.
Don't use the FO3Plugin shortcut. The Winrar file is what you want to use. For people who have their s#*! set up like I do, double-clicking won't run the program but will bring up that little Winrar window, which is probably what led to the confusion on installing. To get the program to work ensure you have Java then right-click the .jar file (which shows up as a winrar file) and go to "Open with" and choose "Java(TM) Platform SE Binary" (or something along those lines. I'm just going with what shows on my pc).
Hopefully this will help someone! (And on the off-chance the creator sees this, thanks for the resource! Once I finally figure out how to work it it was really helpful :) )
I get a Plugin error saying this application doesn't support version 1.3.4 .esp files.
Bummer
Long story short, I'm using mods in PlayStation 3, I need to merge mods because it can only load 3 extra esp files.
I don't have a PC, only a raspberry pi, which runs Linux Debian and have Java 8.
When I tried running the jar I got this error:
Exception during program initialization
Java.io.io.exception: cannot run program "reg": error=2, file or directory not found.
A full picture of the error (as its too long to type it): https://imgur.com/a/aEFOBwc
The one in the readme is very difficult to understand.
Open a new explorer window and type this into the address bar
%appdata%\ScripterRon
delete FO3Plugin.properties
relaunch the application
An example being that I am trying to take the 12-15 XFO 84b .esp's and make my own merged entry. So there was an original entry and I want it to overwrite that entry with the value from the second ESP. But instead of a merge I now have the following:
SPEL record: WearingDown (0100080F) - Wearing Down (the weapon durability wear down rate)
SPEL record: WearingDownZ (01A62760) - Wearing Down (the merged value, but notice the different hex address and the 'z' at the end)
What does the Z mean? Is that FO3Edit's mechanism for showing that it is going to overwrite the old entry? Did it leave the original value alone and create a second entry that will not over write the first?
My guess is that FO3 cannot over-write a value with an identical entry from another ESP with a different value?
Thoughts or suggestions appreciated.
-Koinonos
1. At first, the program wouldn't pick up the path to the javaw.exe file C:\WINDOWS\System32.
*Remembering that I'd installed 64Bit Java, I redirected the program to look for it in the: C:\Program Files\Java\jre\bin file. So the path to javaw was set to: C:\Program Files\Java\jre\bin\javaw.exe. Problem solved.
2. The second problem I faced was the program not finding the plugins. *Huh?* o.O
*This was resolved by following the guidelines in the ReadMe for setting the path which was accomplished with: -DFallout.plugin.path=C:\Program Files\Bethesda Softworks\Fallout 3\Data.
* One would think this would take effect right away... It didn't. After a few choice words and a little patience, I restarted the program and voila!... It worked.
Ultimately, the Properties of the FO3Plugin shortcut looked like this:
Target [ C:\Program Files\Java\jre6\bin\javaw.exe -Xmx1024m -DFallout.plugin.path=C:\Program Files\Bethesda Softworks\Fallout 3\Data -jar FO3Plugin.jar ]
Start In [ C:\Program Files\Bethesda Softworks\Fallout 3\Plugin Editor ] *This is where I extracted the program file.
# Caveat: Yes, I installed the game in the traditional 32 bit Program Files path. Why?
A. I remembered a lesson learned from installing Oblivion in the: Program Files(x86) directory and having my modified plugins (which were still referencing the traditional path) not work.
B. I think the C:\Program Files(x86) path is lame and causes more problems than it resolves. Having said this, I do allow all other 32bit apps to install to that directory because frankly, a 32 bit program will either work/or not in a 64bit environment. I use the traditional path primarily for games.
In any event, I hope my experience helps some of the others out there having problems with getting this program to work and like many others, I give it a health endorsement. So long as it works. ;^)