GillisParrish

[2021-06-20 11:33:08.299 W] QWindowsWindow::setGeometry: Unable to set geometry 1920x1176+0+34 (frame: 1942x1232-11-11) on QWidgetWindow/"MainWindowWindow" on "\\.\DISPLAY1". Resulting geometry: 1920x986+0+34 (frame: 1942x1042-11-11) margins: 11, 45, 11, 11 minimum size: 636x588 MINMAXINFO maxSize=0,0 maxpos=0,0 mintrack=1294,1232 maxtrack=0,0)

nope,not working.I f*#@ing hate this bullshit...so sick and tired of this delicate ass game.

but it's been working fine for like 2 months.I uninstalled several mods,it started freezing mostly when entering a town,so I reinstalled the mods I uninstalled now my wife is gonna be pissed,and right after I figured out how to port oldrim mods,and make patches.

So when I try to launch through MO2 it doesn't start.The first time I tried to launch it through MO2 it gave me some error message about DX12,which I have - but now it doesn't open at all.Any ideas?

bump.

No,I use the community supported NMM,and I have had similar problem to that.Some mods add ini,also which don't change in accordance with the Fallout ini's....but I got that figured out.I have uninstalled the C++ packages,reinstalled those and it still crashes.BEX 64 is a stack overflow issue I believe,but I do not know how to track down what is causing it.My settings were working fine til the latest round of SS updates,so I ran all those back ...and the MF still crashes.

Honestly,I'm about to start offering payment for someone to fix it,not just the BEX64 error,but how to fix load order,mod conflicts,and merge plugins.So tired of Fallout4 being such a pain in the ass to keep running.

I have disabled DEP(which is what the "bcdedit.exe" command is)and yes it only happens with FO4.

sizes match.

all those .dll are present.

done that too

yes I have that installed.

So,this error has periodically popped up for years,and has resulted in many times just putting the game down for months at a time. What is it?How do I fix it permanently? I have heard it is caused by not having a certain DirectX update installed.The Bethesda site refers you directly to the MS website to download and install the correct version,which I have multiple times,ran back the DirectX to the version they suggest will fix the problem - it does not. I have heard it is a DEP problem,proceed to the settings,add an exception,but you can't add properties to 64 bit programs,but you can disable DEP altogether(which is what I have done) - it does not work. I have heard it is caused by multiple scripts calling for the same .dll("MSVCR110.dll").So, I changed the Papyrus settings in the various .ini's,in accordance with a post from KingGath himself - it does not work. If this is the problem how does one go about tracking it down,because a slight variation on "it is multiple scripts tripping all over each other" is,that it is cause by 3rd party software calling for the MSVCR110.dll,while F4SE is calling on it for game stuff. I have heard go to an interior cell(like the bunker in Sanctuary)and sleep for a week - it does not work. And of course I have heard every mod downloaded is the culprit,that mod is cancer,that mod is a nightmare but generally I don't think that is the case,but in this case SS,SSC,WSF,and WS+ all required updating,and that is basically when my game became unplayable.Assuming these updates have multiple scripts running(more then oh...2 days ago)how would one go about fixing that?Too much update at one time for F4SE,causing scripting conflicts?IDK.I am about fed up with it,like I said I have been battling this beast for years,and it will go away for months and I'll think that last edit in the .ini's did it or that patch seems to have got it,but here it is 2020 and I'm still fighting this motherf...problem. Any insight would be appreciated.

I got it figired out,mods with INI's,that don't check the main INI's,to update.

sO,NOW TRYING...LOL,JUST CAME FROM THE cOMMONWEALTH...So,anyways I was trying to figure out how best to get that set of commands to all go through,without having to worry about it;every time I start the game or fast travel,or whatever.I deleted the "sStartingConsoleCommand" command and everything in it's line,also checked my prefs,and custom to make sure it wasn't anywhere...but when I pull up the console it still shows that the commands activated,well some of them anyway...that was the problem to begin with I added commands to the line that weren't triggering.My question - is where the hell is it getting the (NERVE!!!) commands from?Is it not running from the INI files in my Fallout 4 folder?Have I been editing the wrong files for years?At least since I put in the "sStartingConsoleCommand",like 3 years?Do "sStartingConsoleCommand" lines get "baked in"?

"sStartingConsoleCommand=SetGS iTerminalDisplayRate 1200; SetGS iRemoveExcessDeadComplexCount 50; SetGS iRemoveExcessDeadCount 50; SetGS iRemoveExcessDeadComplexTotalActorCount 65; SetGS iRemoveExcessDeadTotalActorCount 50; tgm; tg; tt; tfow; gr off; cl off; sucsm 40; SetGS fworkshopwiremaxlength 2200; SetGS fSandboxCylinderTop 576; SetGS fSandboxCylinderBottom -576; fov 90;" It's directions,command,integer,apostrophe,space,repeat...right?

Still waiting on a fix.