launching: Fallout3.exe (E:\Games\Steam\steamapps\common\Fallout 3 goty\Fallout3.exe)
clearing large-address-aware flag
recorrecting exe checksum (00E59548 -> 00E59528)
crc = FE5B82AE
hook call addr = 00C05F61
load lib addr = 00D9B0F0
dll = E:\Games\Steam\steamapps\common\Fallout 3 goty\fose_1_7.dll
remote memory = 001D0000
old winmain = 006EE300
Well, I assume it's doing something funky because when I start with FOSE the game runs like it did with no patch. If i start the game with Fallout3.exe the game runs fine.
Problem is I need FOSE to make FWE work. Afaik only older versions of FOSE worked with patcher, but since the game is now at a higher version it also requires the newer FOSE version which disables the flag.
Just like to point out that FOSE will remove the 4GB LAA flag from the game when you run the game via FOSE_Loader.exe. What I mean is that Fallout3.exe will have the flag but when FOSE runs, it will remove it while it is doing it's thing, so whenever you run the game via FOSE you are actually not benefiting from the 4GB LAA patch. Any game instance created by FOSE_Loader.exe will be limited to 2GB of RAM regardless of that 4GB patch you apply.
You can verify this by checking the log files that FOSE generates.
I've yet to find a way to over ride this behavior of FOSE.
I believe this is done because the 4GB patch would change around memory locations causing many existing FOSE plugins to not work and the devs did not want idiots complaining when they ran plugins that depended on the program not being 4GB aware, after they applied the 4GB LAA patch.
So basically the devs just locked any and all mods and users of there product in to having only 2GB of RAM to work with (At most), for the sake of backwards compatibility and less headaches caused by stupid complaints from less... computer literate people.
@BlackRampage - I didn't say anything of that sort. Maybe you read it wrong.
Edited by surg23, 17 November 2013 - 09:41 PM.