F4 unmodded crash at startup.

[Playstation1_Hagrid]

I do play modded, just finished remodding the game to just start it up, get too the main menu aaand... crash. Booted up vanilla through steam and im still having the same issue. it gets too the main menu and just crashes too my desktop. i know about weapon debris, and yes its turned off. didnt have a problem before this next gen update bs. so whats going on? What can i do? i read people talking about installing c++, dont really get how a programming software could help a game run at all.

Just a side note, i dont have the mods installed directly to the game files, i run them through vortex, so base f4 shouldnt be trying to launch with them.

p.s.s. im running a ryzen 7, 4070 super, 32 gb of ram. os is windows 11. if that helps at all

p.s.s.s. tried turning off godrays as well since apparently that causes the game too crash as well. didnt work.

[Kaldaien]

Consider yourself lucky. I can't even get to the first splash screen without it crashing. Creates a window then does an integer divide by zero and immediately crashes.

[Hiro]

Originally posted by Playstation1_Hagrid:

i read people talking about installing c++, dont really get how a programming software could help a game run at all.

They are not talking about SDK (software development kit).
They are talking about the C++ runtime libraries.
Ask Steam to verify the game, the libraries should be re-installed for you, if the game depends on them.

--
Make sure to update the GPU drivers (or reinstall them with DDU).
On the launcher, select the lowest quality you possibly can for everything and check if the game still crashes.

[Hiro]

Originally posted by Kaldaien:

Consider yourself lucky. I can't even get to the first splash screen without it crashing. Creates a window then does an integer divide by zero and immediately crashes.

Hahahaha, and the bootlickers on this board have the audacity of saying that the update does not have problems.

The window position is stored on the "<home>\\My Games\\Fallout4\\Fallout4Custom.ini" file.
Try to delete that file.

[Kaldaien]

Originally posted by Hiro:

Originally posted by Kaldaien:

Consider yourself lucky. I can't even get to the first splash screen without it crashing. Creates a window then does an integer divide by zero and immediately crashes.

Hahahaha, and the bootlickers on this board have the audacity of saying that the update does not have problems.

The window position is stored on the "<home>\\My Games\\Fallout4\\Fallout4Custom.ini" file.
Try to delete that file.

Doesn't seem to have helped :-\

Luckily I am the author of Special K.

[SpecialK.System]
EnableCrashSuppression=true

That works, surprisingly. Whatever the game was trying to divide by zero wasn't particularly important and it can continue running if I ignore the exception :) I feel sorry for anyone else with this problem, as they won't be able to even diagnose it, much less workaround it.

[sdack]

https://steamcommunity.com/sharedfiles/filedetails/?id=3241230342

[x]

Check drivers and whatever software (control panel or something) that the GPU needs.
A few months ago my computer wouldn't run a game (I think it was Death Strading Director's Cut that I had played a year or two before) and I checked drivers and it seemed up to date. But I went on the AMD website and there was a new GPU control panel or whatever they call it. And the driver wouldn't update past a certain point with the old software. The software was new and not an update from the previous one. Unistalled, installed the correct software, updated drivers and all was well.

[Kazuma]

Originally posted by Kaldaien:

I am the author of Special K.

Interesting software!
Just tried to use it here (PoP!_OS and Steam Flatpak), re-named the file to dxgi.dll and it did indeed load into the game.

Unfortunately I got a myriad errors about xinput (was tanking FPS) and errors about DXVK not implementing some function and using an old code path.

[Dragonzord]

It really sucks how Bethesda is moving away from facilitating mods in their games. If the Helldivers 2 fiasco is any indication, people simply need to speak up about these unilateral updates.

Maybe the team can create some sort-of bumper warning, keep players on older versions if necessary.

[sdack]

Originally posted by MoaM:

It really sucks how Bethesda is moving away from facilitating mods in their games.

I have the old and the new version on my PC. Why is this so hard to do for some? When you can install mods and get them to work together, then how hard is it to keep two copies of the game around? You kids always complain about the game maker for the smallest inconveniences. Yet you create problems for yourself with modding but do not have a problem fixing mod conflicts and running with hundreds if not a thousand mods.

[Playstation1_Hagrid]

Originally posted by sdack:

Originally posted by MoaM:

It really sucks how Bethesda is moving away from facilitating mods in their games.

I have the old and the new version on my PC. Why is this so hard to do for some? When you can install mods and get them to work together, then how hard is it to keep two copies of the game around? You kids always complain about the game maker for the smallest inconveniences. Yet you create problems for yourself with modding but do not have a problem fixing mod conflicts and running with hundreds if not a thousand mods.

i mean, steam auto updates with no option to disable it. ive already bought the game twice one for ps4 and the steam version. as far as im aware there is no way too rollback an update through steam.

[Playstation1_Hagrid]

Originally posted by sdack:

Avoid installing the update onto a modded game. Do a clean reinstall of the game, make sure you have no left-overs from the previous version, and build a new, clean modding list.

Use this checklist to see whether you missed a spot:

• Meet the minimum hardware requirements, verify game files using the Steam client, and update Windows and drivers.
  
  
• Clear the Steam folder of Fallout 4, i.e. C:\Program Files (x86)\Steam\steamapps\common\Fallout 4\, clear the AppData\Local\Fallout4\ folder, and remove any .ini files from Documents\My Games\Fallout4\ before doing a reinstall. Be sure there is nothing left over from previous installations, no mods, no old load orders, and no old settings.
  
  
• Run on the dedicated GPU, not the integrated GPU.
  
  
• Set the refresh rate to 60Hz or 120Hz. Limit the frame rate to 60fps.
  
  
• Disable High DPI Scaling in Windows and set it back to 100%, or, use the Compatibility tab to the file properties of Fallout4.exe and Fallout4Launcher.exe, and set an override for High DPI Scaling by using the "Application"-setting.
  
  
• Disable video recording and streaming overlays, exit any unnecessary background programs and check the system tray for unnecessary tools and apps. Turn off animated wallpapers, unplug any unnecessary devices, and so forth.
  
  
• Disable weapon debris when you have an Nvidia card.

tried alot of this. moniter runs at 60 hrtz, ive deleted the game and reinstalled, ive deleted said specific file and had steam recreate it. drivers are up to date. if i can run games like cyberpunk at max graphic settings with no hangup specs arent the issue. as i also previously stated, the game ran perfect before the update. i.e loaded into saves, and fully into the game. thank for some of the other tips though, ill look into them.

[loganhuyy2]

Originally posted by Kaldaien:

Originally posted by Hiro:

Hahahaha, and the bootlickers on this board have the audacity of saying that the update does not have problems.

The window position is stored on the "<home>\\My Games\\Fallout4\\Fallout4Custom.ini" file.
Try to delete that file.

Doesn't seem to have helped :-\

Luckily I am the author of Special K.

[SpecialK.System]
EnableCrashSuppression=true

That works, surprisingly. Whatever the game was trying to divide by zero wasn't particularly important and it can continue running if I ignore the exception :) I feel sorry for anyone else with this problem, as they won't be able to even diagnose it, much less workaround it.

i believe I'm having the exact same problem, could you possibly tell me how to change the setting you did. I have vs code if that's required. I have also installed special K. off your steam profile.

[Kaldaien]

Originally posted by loganhuyy2:

Originally posted by Kaldaien:

Doesn't seem to have helped :-\

Luckily I am the author of Special K.

[SpecialK.System]
EnableCrashSuppression=true

That works, surprisingly. Whatever the game was trying to divide by zero wasn't particularly important and it can continue running if I ignore the exception :) I feel sorry for anyone else with this problem, as they won't be able to even diagnose it, much less workaround it.

i believe I'm having the exact same problem, could you possibly tell me how to change the setting you did. I have vs code if that's required. I have also installed special K. off your steam profile.

You probably don't have the same problem.
I later learned that corrupted files in my profile directory were to blame.

But that would go in SpecialK.ini for the current game.