wfandrews Posted May 29, 2014 Share Posted May 29, 2014 When I ran FNVEdit to clean my files I followed the instructions in the manual that I downloaded from the same page as the FNVEdit download. After I had completed cleaning all the DLC files I attempted to start FNV, it went to the start screen but did not load a menu. I started Windows Task Manager and found that FNV was not responding. I went back to FNVEdit and chose run with everything checked, in the log which came up in the right side screen I scrolled down and found that GRA was completly messed up, nothing but errors. I unistalled FNV and reinstalled, it then started fine. I went back to FNVEdit applied filter to Honest Hearts and checked ITM and "conflict status inherited by parent" I did not run this but closed FNVEdit. After doing so my game would not start, I went back and checked my files in FNVEdit and once again found that the GRA esm was completely FUBAR. It seems that by the mere act of applying the filter in FNVEdit it screws up my game.. What, if anything, am I doing wrong? I would really like to clean my DLC files; I had no problem with the previous version of FNVEit.. As a side note could someone explain why they took a relatively simple process like clicking on "apply filter for cleaning" and made it more complicated to produce the same result? Need some help here. thanks, Bill Downloaded older FNVEdit from download page and still did not see "apply filter for cleaning" I am sure that the one I had before downloading the newest one had that line. Anyone know where I can dowload that file? Link to comment Share on other sites More sharing options...
sumquy Posted June 12, 2014 Share Posted June 12, 2014 this exact same thing is happening to me. anyone have a fix? Link to comment Share on other sites More sharing options...
RoyBatterian Posted June 12, 2014 Share Posted June 12, 2014 (edited) It's not a good idea to clean the DLC's in New Vegas because many many mods were made before people started to do that like they do with Skyrim, and they expect the dirty files. However if you find a legit bug in FNVEdit you should post about it in the FNVEdit thread. Edited June 12, 2014 by RoyBatterian Link to comment Share on other sites More sharing options...
sumquy Posted June 12, 2014 Share Posted June 12, 2014 mmm. maybe i could have been clearer. i didn't "clean" any files. it took me 3 reinstalls to figure out where the problem was coming from. what happens is, i intsall game, do various other changes like the 4gb aware, load up all my mods and sort the load order with boss. at this point we are still good. i can load games and start a new one. then i start fnvedit to create a merge patch. the next time i start game it goes to intro scenematics and program is "not responding". the text menu never comes up, it just sits there on the ranger with the gun screen. after i created the merge patch, i just left it alone. i didn't try to resolve any left over conflicts or anything, because i wanted to see if it would still start correctly and it did not. one odd thing that i did notice was that when i told it to save the merge patch after creating it it also had two of the dlc marked as updated too. i think it was honest hearts and dead money, but not sure. maybe i should not have let it update them too? the version of fnvedit i was using was 3.0.10, at the time most recent, but i see a new version went up last week. another strange behavior of this version is when i converted the file to master update and run it, it errors with "master update is only available for fo3". i have the latest version of fnvedit now and will do ANOTHER reinstall later today to see if it does not cause the problem, but unknown at this time if it is specific to that version or an issue with all versions. Link to comment Share on other sites More sharing options...
sumquy Posted June 13, 2014 Share Posted June 13, 2014 so i really hate it when i find the one person out their on the internet with the same problem as me...but the thread is old and abandonded with no solution. this appears to be a problem with fnvedit 3.0.10. i can relaibly reproduce the symptoms described above by creating a merge patch using this version.the fix is to update to a newer version of fnvedit. as of right now 3.0.32 is the most recent and does not cause this bug. Link to comment Share on other sites More sharing options...
Recommended Posts