Gilibran Posted September 8, 2017 Share Posted September 8, 2017 Looks like you need to update some mods, script extender needs updating and Looksmenu to for the presets to work. Most mods that rely on the SE after the CC update. It can (and honoustly is) be a hassle to setup FO4 with mods but there is no reason it should not work unless your PC does not meet the requirements for FO4. Just like modding Skyrim, start with the basics and read the readme's of every mod you download for dependencies. Modded Fallout 4 works for most people, it's just not plug and play. Link to comment Share on other sites More sharing options...
falloutkid12 Posted September 8, 2017 Share Posted September 8, 2017 Am trying to play the game with the new high-rez addon. There's your problem. Link to comment Share on other sites More sharing options...
0ldDan Posted September 9, 2017 Share Posted September 9, 2017 I can confirm I had never-ending problems with the HD texture pack. Black face is a well known phenomenon and has something to do with the resized spec maps of the face texture (I'm no expert). The best solution is to just not use it and install the texture packs from the Nexus you like instead. In most cases the Nexus re-textures are better quality and lower memory overhead anyway. Thank Atom for the Nexus. Love you guys. Link to comment Share on other sites More sharing options...
AGreatWeight Posted September 9, 2017 Share Posted September 9, 2017 Ah, another 'Bethesda broke my modded game' post - never get's old... Link to comment Share on other sites More sharing options...
reconphil Posted September 10, 2017 Share Posted September 10, 2017 My game will no longer load with any mods. If I go to no mods it will load. I get a Windows Error that says Fallout 4 stopped working. My Papyrus Log is as follows: [09/09/2017 - 10:14:36PM] Papyrus log opened (PC-64)[09/09/2017 - 10:14:36PM] Update budget: 1.200000ms (Extra tasklet budget: 1.200000ms, Load screen budget: 500.000000ms)[09/09/2017 - 10:14:36PM] Memory page: 128 (min) 512 (max) 153600 (max total)[09/09/2017 - 10:14:36PM] Maximum stack depth: 100[09/09/2017 - 10:14:36PM] This is a script log only and does not contain information on any other part of the game, including crashes.[09/09/2017 - 10:14:37PM] Cannot open store for class "CreationClub:BGSFO4018:B018_QuestScript", missing file?[09/09/2017 - 10:14:37PM] Cannot open store for class "CreationClub:BGSFO4019:ccBGSF04019_ArmorScript", missing file?[09/09/2017 - 10:14:37PM] Cannot open store for class "DLC04:DLC04OperatorsRifleAnimationScript", missing file?[09/09/2017 - 10:14:38PM] Cannot open store for class "crpScriptWorkshopMenu", missing file?[09/09/2017 - 10:14:38PM] error: Unable to bind script crpScriptWorkshopMenu to crpQuestGlobal (0900BF09) because their base types do not match[09/09/2017 - 10:14:39PM] Cannot open store for class "ts_holotape_questscript", missing file?[09/09/2017 - 10:14:39PM] Cannot open store for class "NAC:KVW", missing file?[09/09/2017 - 10:14:39PM] Cannot open store for class "NAC:DrugMFX", missing file?[09/09/2017 - 10:14:39PM] Cannot open store for class "BTInt_DRGN_KeyScript", missing file?[09/09/2017 - 10:14:40PM] Cannot open store for class "pgm_wo_damaging_script", missing file?[09/09/2017 - 10:14:40PM] Cannot open store for class "HeatGeneration", missing file? Has anyone else had this problem? Any ideas? Thanks in advance. Link to comment Share on other sites More sharing options...
Reneer Posted September 10, 2017 Share Posted September 10, 2017 You need to read the Papyrus log more closely: [09/09/2017 - 10:14:36PM] This is a script log only and does not contain information on any other part of the game, including crashes. Link to comment Share on other sites More sharing options...
Deleted3082751User Posted September 11, 2017 Share Posted September 11, 2017 (edited) their is many reasons why papyrus logging is disabled by default. 1 of them is the fact that papyrus logging is not made to decipher possible game crashes, 2. papyrus logging can actually make the game crash. and 3. its only potentially useful for authors to see if their scripts are working properly that is all. case in point, papyrus logging is the worse way to determine potential game crashes (because 90% of the log is irrelevant to you). chances are that it is not even scripts that are causing the game to crash, its more likely hardware issues, or very likely actual mods. Edited September 11, 2017 by Guest Link to comment Share on other sites More sharing options...
Recommended Posts