Deleted32001180User

@JimmyRJump - Thanks for the pep talk. Good information all of it. Sometimes I don't see the forest for the trees. =P NOW....I'm going to give those who are having some issues a tip. Please check your device manager and update your Network Adapter driver if you haven't already. Mine is a Realtek PCIe and since the latest Windows 10 Update did NOT update it, you can do it yourself. For some strange reason, DESPITE always playing my games including Fallout 4 with Steam in offline mode, it fixed MY game CTDs & freezing & loud buzzing sounds completely. GO figure. =P

Every since Bethesda decided to include their ridiculously useless Creation Club mods for sale and have updated the game to accomodate their greed it has caused nothing but trouble for the playing & FREE modding community. Fallout 4 is the ONLY game that I've tried to play with this feature and I'm getting constant CTDs & freezes. I play Skyrim with no problem and I play Oblivion with no problem and I play Fallout New Vegas with NO problem. I've updated all my drivers and checked and rechecked everything that could be causing the problem which did NOT occur at all until these recent game updates. SO.....IMHO, Fallout 4 is broken and unplayable. I do NOT recommend buying it or downloading it or even wasting time talking about it. Nuff said.

Every since Bethesda decided to include their ridiculously useless Creation Club mods for sale and have updated the game to accomodate their greed it has caused nothing but trouble for the playing & FREE modding community. Fallout 4 is the ONLY game that I've tried to play with this feature and I'm getting constant CTDs & freezes. I play Skyrim with no problem and I play Oblivion with no problem and I play Fallout New Vegas with NO problem. I've updated all my drivers and checked and rechecked everything that could be causing the problem which did NOT occur at all until these recent game updates. SO.....IMHO, Fallout 4 is broken and unplayable. I do NOT recommend buying it or downloading it or even wasting time talking about it. Nuff said.

Patience is a virtue. Wish I fooking had some. =P Hope the Silverlock crew isn't on vacation this week because F04 is now a useless collection of files on my computer. =P

Well.....the romance is over and Magnolia won't bed me anymore. There is a mod that uses a ton of scripts to allow me to consummate the relationship again BUT......the change in dialogue is conditioned by only ONE variable. I've already hacked the dialogue conditions to get the option to return BUT, that just added another mod to my load order. What I want to do is use Magnolia's normal negative response to CHANGE it back. That would be a simple script fragment I would think but my Papyrus sux. The quest is DialogueGoodneighbor (00033582) and the variable that gets changed from ZERO to ONE is ::MagnoliaRelationshipOver_var. I was also thinking I could change it back with the console using "CallQuestFunction <Quest> <function> <parameters>, so that I'm not even messing with the quest but I'm not 100% sure how to do that. SO....any advice on either using the console or how to script fix this very simple change in one variable so I can avoid a script heavy mod that basically does the same thing? EDIT - OK...anyone who wants to change the variable back to allow continued dates with Magnolia and doesn't want to add a script heavy mod to their load order can use the console: setpqv 00033582 MagnoliaRelationshipOver_var 0

Ditto.