[RELz/BETA/WIPz] FNVEdit

Post » Tue Feb 01, 2011 4:19 pm

Fatal error when running FNVEdit after latest patch..
Fatal: Could not open registry key: \SOFTWARE\Bethesda Softworks\FalloutNV\


That is caused by the load order of FalloutNV.esm being altered, as others have stated.

The FalloutNV.esm being editable by FNVEdit is not. I think there may be some manner of checksum in FNVEdit that identifies the proper FalloutNV.esm and then bars alterations to it. Since it has been altered by the patch, it doesn't match and is considered "just another ESM" by Edit.
User avatar
Cody Banks
 
Posts: 3393
Joined: Thu Nov 22, 2007 9:30 am

Post » Tue Feb 01, 2011 2:03 pm

I really have no idea whether it is bad or not, but generally you never modify the original ESM files at all.

You can ask Steam to verify the files and see if it replaces FalloutNV.esm with an original again.

Or, re-name "falloutNV.esm" to "falloutNV.esm.bak" or something like that, ask Steam to verify the files and the v1.2.314 version should download.

I made the mistake of saving it when looking at the changes, but there should be a backup saved by FNVEdit itself (in the Data folder) that you can copy back to get the original file. It will have a unique name something like "FalloutNV.esm.backup.2010_12_14_01_57_50".
User avatar
Kate Murrell
 
Posts: 3537
Joined: Mon Oct 16, 2006 4:02 am

Post » Tue Feb 01, 2011 11:51 pm

Of saving new FalloutNV.ESM: There were two duplicate groups which FNVEdit merges , aptly, with their originals.

[00:06] Background Loader: [FalloutNV_New.ESM] Warning: File contains duplicated top level group: GRUP Top "AMEF"[00:06] Background Loader: [FalloutNV_New.ESM] Merged 3 record from duplicated group: GRUP Top "AMEF"[00:06] Background Loader: [FalloutNV_New.ESM] Warning: File contains duplicated top level group: GRUP Top "RCPE"[00:06] Background Loader: [FalloutNV_New.ESM] Merged 1 record from duplicated group: GRUP Top "RCPE"


This, most likely, won't harm anything. If there were duplicate CELL or WRLD groups, this behavior could be problematic, but all other groups can be directly and safely edited by FNVEdit.



When FNVEdit fixes the above, a backup will be created. I'd suggest just keeping the backup handy, but playing with the fixed file. If anything goes wrong, which I doubt it will, one can delete FalloutNV.ESM, then rename the backup to save time/skip Steam replacement.
User avatar
Sheila Reyes
 
Posts: 3386
Joined: Thu Dec 28, 2006 7:40 am

Post » Tue Feb 01, 2011 1:58 pm

Ok, whew. Thanks everyone!
User avatar
Albert Wesker
 
Posts: 3499
Joined: Fri May 11, 2007 11:17 pm

Post » Tue Feb 01, 2011 10:56 am

Good call, thanks JustinOther. :)

I shall do just that!

I also commented in the GECK powerup section of Nexus to let PurplePigeon know that the new 1.2 binary breaks the script compiler warnings - we'll have to wait for a new version I suspect.

Miax
User avatar
Sudah mati ini Keparat
 
Posts: 3605
Joined: Mon Jul 23, 2007 6:14 pm

Post » Tue Feb 01, 2011 4:21 pm

Of saving new FalloutNV.ESM: There were two duplicate groups which FNVEdit merges , aptly, with their originals.
Ah, that explains a lot about why it's doing it. I was confused because it was marking it as edited without me doing anything with it at all.

Wonder how Bethesda/Obsidian ended up with duplicated groups? I'd be curious about what the three records and the one record that are merged actually are.
User avatar
Del Arte
 
Posts: 3543
Joined: Tue Aug 01, 2006 8:40 pm

Post » Tue Feb 01, 2011 11:25 pm

I also commented in the GECK powerup section of Nexus to let PurplePigeon know that the new 1.2 binary breaks the script compiler warnings - we'll have to wait for a new version I suspect.
Or, even better, they've a new GECK in store for us. There's at least one new scripting finction, GetContainerInventoryCount, which the current GECK doesn't recognize. Hopefully, it will have the missing debug stuff all on its own.
Ah, that explains a lot about why it's doing it. I was confused because it was marking it as edited without me doing anything with it at all.
Generally, *Edit won't directly edit the [00] file, but it appears duplicate groups are automatically merged. By the same token, empty GRUPs like the COBJ (Constructible Object) are removed. None of the three edits FNVEdit will make to a new ESM should harm anything.
Wonder how Bethesda/Obsidian ended up with duplicated groups?
I'd bet 200 caps and a bottle of whiskey they didn't use FNVEdit.
I'd be curious about what the three records and the one record that are merged actually are.
Below is everything new obtained via loading the old ESM and using FNVEdit's "Compare to..." and selecting the new. The RCPE and AMEF records which FNVEdit wants to relocate are at the bottom of the list.
Spoiler
[00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:08] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:09] Background Loader: [00:10] Background Loader: [00:10] Background Loader: [00:10] Background Loader: [00:10] Background Loader: [00:10] Background Loader: [00:10] Background Loader: [00:10] Background Loader: [00:10] Background Loader: [00:10] Background Loader: [00:10] Background Loader: [00:10] Background Loader: [00:10] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: [00:11] Background Loader: 

User avatar
Tarka
 
Posts: 3430
Joined: Sun Jun 10, 2007 9:22 pm

Post » Tue Feb 01, 2011 5:03 pm

Minor error in FNVEdit (this is with FalloutNV v1.2.0.314 and current FNVEdit v3.0.15):

When displaying weapons records, there is a "Reload Anim" entry (on the Art tab and Mods tab in the GECK).

FNVEdit displays the wrong entry if the entry should be ReloadW, ReloadX, ReloadY or ReloadZ.

ReloadW is displayed as ReloadT, ReloadX is displayed as ReloadU, ReloadY is displayed as ReloadV and ReloadZ is displayed as ReloadW.

This is probably because ReloadT, ReloadU and ReloadV do not exist causing the displayed entry to be displaced (alphabetically) upwards by 3 positions. I think this is just a simple index error in FNVEdit or you are using a list inside the program in which there is a ReloadT, U and V.
User avatar
matt
 
Posts: 3267
Joined: Wed May 30, 2007 10:17 am

Post » Tue Feb 01, 2011 11:48 pm

I keep getting address violations when trying to merge mods... it's very annoying... any idea what's wrong?
User avatar
Trey Johnson
 
Posts: 3295
Joined: Thu Oct 11, 2007 7:00 pm

Post » Tue Feb 01, 2011 11:53 am

Nevermind... apparently FNVEdit needs over 2gb of clean memory to merge 2 files of a few megabytes.
User avatar
Beast Attire
 
Posts: 3456
Joined: Tue Oct 09, 2007 5:33 am

Post » Wed Feb 02, 2011 12:33 am

I have a feature request: to be able to export and import FNVEdit entries as a text file.
User avatar
kirsty williams
 
Posts: 3509
Joined: Sun Oct 08, 2006 5:56 am

Post » Tue Feb 01, 2011 1:22 pm

Nevermind... apparently FNVEdit needs over 2gb of clean memory to merge 2 files of a few megabytes.

Really?! It took 2gb of memory on your computer?

For most users I have found and have reported ~200 megs of use (my current copy loaded is at 173 megs). So either your system is very non-standard, your doing something wrong or mis-reporting your memory use as FNVEdit does not take 2gb of memory - ever. I have used the tool for thousands of hours now on XP 32-bit and Win7 64-bit systems, and have never seen this behavior before.

I'm glad you got it working at least, but thats alot of memory for one app. :)

Miax
User avatar
Tamara Dost
 
Posts: 3445
Joined: Mon Mar 12, 2007 12:20 pm

Post » Tue Feb 01, 2011 9:32 pm

Really?! It took 2gb of memory on your computer?

For most users I have found and have reported ~200 megs of use (my current copy loaded is at 173 megs). So either your system is very non-standard, your doing something wrong or mis-reporting your memory use as FNVEdit does not take 2gb of memory - ever. I have used the tool for thousands of hours now on XP 32-bit and Win7 64-bit systems, and have never seen this behavior before.

I'm glad you got it working at least, but thats alot of memory for one app. :)

Miax


well that's how it was. i was trying everything to get the files to merge properly, but there were tons of errors. finally i did a reboot and then did it, as i figured it might be a memory issue but i didn't think of it before because the files were so small. FNVEdit ate over 2gb of memory, but the merge was without any problems.

The files merged were something like 1 mb and 5mb (esp only), the latter was an esp containing a heightmap for an island in a new world space that I made in the F3 GECK because the NV heightmap editor doesn't work for me (and for everyone else i spoke to about it). That's why I had to merge it. Maybe it happened because heightmaps are complex or something... but I doubt it... it's just a few mb's of data being copied to another file right?
User avatar
Tanika O'Connell
 
Posts: 3412
Joined: Fri Jan 26, 2007 1:34 am

Post » Tue Feb 01, 2011 5:19 pm

well that's how it was. i was trying everything to get the files to merge properly, but there were tons of errors. finally i did a reboot and then did it, as i figured it might be a memory issue but i didn't think of it before because the files were so small. FNVEdit ate over 2gb of memory, but the merge was without any problems.

The files merged were something like 1 mb and 5mb (esp only), the latter was an esp containing a heightmap for an island in a new world space that I made in the F3 GECK because the NV heightmap editor doesn't work for me (and for everyone else i spoke to about it). That's why I had to merge it. Maybe it happened because heightmaps are complex or something... but I doubt it... it's just a few mb's of data being copied to another file right?

Interesting, I have not tried to merge heightmaps before - it is certainly possible for it to chew up the ram if it thinks it needs to in order to complete the operation. If it has to load the NVWasteland references, your then dealing with a much larger set of records than just the plug-ins. Again I can't say for sure, but its a first for me!

Glad it worked. ;)

Miax
User avatar
Amanda Leis
 
Posts: 3518
Joined: Sun Dec 24, 2006 1:57 am

Post » Tue Feb 01, 2011 10:35 am

the world space i copied had no links whatsoever to NVWasteland. Not even a door, not a parent either.
User avatar
Amie Mccubbing
 
Posts: 3497
Joined: Thu Aug 31, 2006 11:33 pm

Post » Tue Feb 01, 2011 7:34 pm

I've uploaded version 3.0.16 to http://www.newvegasnexus.com/downloads/file.php?id=34703.

- FalloutNV.esm not marked as modified if duplicated groups have been merged
- fixed crash when looking at base effect records
- "unsaved changes" dialog should no longer appear if detail view is in edit mode
User avatar
Kirsty Collins
 
Posts: 3441
Joined: Tue Sep 19, 2006 11:54 pm

Post » Tue Feb 01, 2011 8:51 pm

- "unsaved changes" dialog should no longer appear if detail view is in edit mode

Thankyouthankyouthankyou!
User avatar
Cassie Boyle
 
Posts: 3468
Joined: Sun Nov 05, 2006 9:33 am

Post » Tue Feb 01, 2011 3:58 pm

Thankyouthankyouthankyou!

I haven't really tested it, let me know if you see any problems.
User avatar
Frank Firefly
 
Posts: 3429
Joined: Sun Aug 19, 2007 9:34 am

Post » Tue Feb 01, 2011 2:50 pm

I haven't really tested it, let me know if you see any problems.

Don't see any problems in the version 3.0.16
- FalloutNV.esm not marked as modified if duplicated groups have been merged

Working
- "unsaved changes" dialog should no longer appear if detail view is in edit mode

Working

Version 3.0.13 syncs up the engine with the most current version of TES4Edit, TES4LODGen and FNVEdit.
- fixed in-place editor to properly cover the complete field and have it's text align exactly with the text normally displayed

This glitch is back again :(
User avatar
Louise Dennis
 
Posts: 3489
Joined: Fri Mar 02, 2007 9:23 pm

Post » Tue Feb 01, 2011 7:01 pm

I'm having an issue with FNVEdit I hope someone can help me with. I'm using the excellent training manual by Miaximus with version 3.0.16 and WinXP. Whenever I try to create the automatic merged patch following the instructions in the manual a merged patch is created with just a header and no records even though multiple conflicts are detected with the filter. I then have to manually assign my esm/esp's as masters and override each conflicting record individually into the merged patch. Obviously this has become very cumbersome when updating/adding mods or changing load order with approximately 60 esm/esp's currently installed.

Has anyone run across anything similar who could help me with what I may be doing wrong?
User avatar
Nick Tyler
 
Posts: 3437
Joined: Thu Aug 30, 2007 8:57 am

Post » Tue Feb 01, 2011 9:43 pm

Ooh, I am not the only one!

I think I am exactly in the same boat.

I am using this : http://www.newvegasnexus.com/downloads/file.php?id=38413, which is excellent by the way. Thank you!

If I run the filter on the list of my mods, I am getting a whole bunch of conflicts detected (red background!).

If I then attempt to automatically run a merged patch, FNVE only generates a small file, with maybe one or two (rather insignificant, race related) records in it.

I am probably also doing a newbie mistake here, but I really wish it could be helped. Manually patching is becoming a bit of a chore after a while :(


I'm having an issue with FNVEdit I hope someone can help me with. I'm using the excellent training manual by Miaximus with version 3.0.16 and WinXP. Whenever I try to create the automatic merged patch following the instructions in the manual a merged patch is created with just a header and no records even though multiple conflicts are detected with the filter. I then have to manually assign my esm/esp's as masters and override each conflicting record individually into the merged patch. Obviously this has become very cumbersome when updating/adding mods or changing load order with approximately 60 esm/esp's currently installed.

Has anyone run across anything similar who could help me with what I may be doing wrong?

User avatar
Eoh
 
Posts: 3378
Joined: Sun Mar 18, 2007 6:03 pm

Post » Wed Feb 02, 2011 12:31 am

I have the same issue with the automatic merged patch creation as the above posters.
User avatar
lisa nuttall
 
Posts: 3277
Joined: Tue Jun 20, 2006 1:33 pm

Post » Tue Feb 01, 2011 8:39 pm

I've uploaded version 3.0.19 to http://www.newvegasnexus.com/downloads/file.php?id=34703.

This version includes updated record definitions to better support DeadMoney.esm
User avatar
Jodie Bardgett
 
Posts: 3491
Joined: Sat Jul 29, 2006 9:38 pm

Post » Tue Feb 01, 2011 11:41 am

good to see prominent names again! sure would be glad if you guys did more than update but you have our thanks! :goodjob:
User avatar
Lily Evans
 
Posts: 3401
Joined: Thu Aug 31, 2006 11:10 am

Post » Wed Feb 02, 2011 12:09 am

I've uploaded version 3.0.19 to http://www.newvegasnexus.com/downloads/file.php?id=34703.

This version includes updated record definitions to better support DeadMoney.esm


Any idea why I'm suddenly getting Access Violations whenever I try to apply a filter to see conflicts?

I do have a bashed patch, 0 that I'm trying to load also.

The message looks like:
Access violation at address 00405BA4 in modules 'FNVEdit.exr'. Read of address 002fffe6

Been fighting with this for about a week trying to figure out what changed.

EDIT:

Taking the Bashed Patch, 0 out of the list allows the filter to work correctly with no crashes. If I revert back to the 3.0.15 version it works fine also.

This is on Win 7 64 bit with 6gigs of memory.
User avatar
x_JeNnY_x
 
Posts: 3493
Joined: Wed Jul 05, 2006 3:52 pm

PreviousNext

Return to Fallout: New Vegas