Closed GoogleCodeExporter closed 9 years ago
Original comment by danielhmpdx16@gmail.com
on 28 Sep 2012 at 12:14
This is when that error occurs:
You have PluginA.esp and PluginB.esp loaded in FNVEdit
PluginA is a master of PluginB
PluginB has a Weapon Mod reference placed in a cell
right-click on the weapon mod reference, then 'change FormID'.
Change the formID so that it's mod index becomes that of PluginA. This
'Injects' the record into PluginA.
The next step is to right-click on the injected reference (on PluginB) and
'copy with override' into PluginA. This is when the error occurs.
Original comment by rickerhk...@gmail.com
on 2 Oct 2012 at 2:41
As the original author of the report and ESP, let me explain this in a clearer
way:
What steps will reproduce the problem?
1. With FNVEdit load any CELL record (for example WestsidePawnShopInterior
"Miguel's Pawn Shop" [CELL:000F0820]
2. Right-click and select "Add - REFR Placed Object". Take the default FormID.
This will create a NULL Reference placed object in the cell.
3. Go to the Name - Base record (which currently is NULL) and edit its value by
replacing the NULL with a weapon mod kit (for example
ModNVLaserRifleBeamSplitter "Laser Rifle Beam Splitter" [IMOD:0010C86A])
What is the expected output?
FNVEdit should let you place the weapon mod kit in the cell
What do you see instead?
FNVEdit throws an exception that says "Found an IMOD reference, expected: ACTI,
ALCH, AMMO, ..." and so on
What version of the product are you using? On what operating system?
FNVEdit
Original comment by geobo...@gmail.com
on 4 Oct 2012 at 8:13
Please note that FNVEdit simply doesn't accept having a weapon mod kit (IMOD)
into a CELL or a WORLD space. It is possible to drop a weapon mod kit into a
CELL using the GECK, to save it into an ESP, to load that ESP and, if you check
the ESP for errors, FNVEdit will warn you that the cell contains an IMOD where
it shouldn't.
The solution IMO is to just add the IMOD type to the list of references that
can be placed in the world.
Original comment by geobo...@gmail.com
on 4 Oct 2012 at 8:14
Original comment by danielhmpdx16@gmail.com
on 5 Oct 2012 at 1:58
Original issue reported on code.google.com by
danielhmpdx16@gmail.com
on 27 Sep 2012 at 8:44