ESP Error for an ESM

[KeltecRFB]

Mod Orginzer is detecting an .esp file when it should be detecting an .ESM file and making it bold.  What causes these errors?

 

14:43:22 [C] failed to parse esp file C:\Program Files (x86)\Steam\SteamApps\common\Fallout New Vegas\Mod Organizer\mods\PANZER\PANZER.esm: sub-record incomplete

 

15:05:58 [C] failed to parse esp file C:\Program Files (x86)\Steam\SteamAp4ps\common\Fallout New Vegas\Mod Organizer\mods\destruction\Destruction.esm: sub-record incomplete

 

Thank you!

Edited January 30, 2015 by KeltecRFB

[GrantSP]

No, don't worry about the screenshots. I had no idea there were that many in that mod. I'm only chasing wild leads here, nothing concrete that I'm working to at the moment.

 

Okay, I've found the mod(s) on Nexus. I'm assuming this is the FO3 version. Is the error from the esm in the hotfix or the main download?

I can't load it into xEdit but I may be able to examine the structure by other means and see if there is anything fishy about this mod.

 

EDIT:

Okay can you give me just one screenshot? Have it show the last of the masters and the first of the ONAMs please.

Edited February 3, 2015 by GrantSP

[KeltecRFB]

Here you go, do you want me to post Panzer's too although I am going to guess that if we can fix Destruction, we probably can fix Panzer too since Destruction is in Panzer.  In addition, is this enough information or do you need more ONAMs?

 

[spoiler=Attachment]

 

Edited February 3, 2015 by KeltecRFB

[GrantSP]

hmm... I was hoping to see something odd in the first line or two. Examining it with a hex-editor shows it to be a little different to other esm's just after the masters are listed.

 

I really can't offer much more. My best idea would be MO's file checks for what constitutes an esp/esm are more stringent than those in xEdit and it baulks at this 'sub-record', whatever that may be.

 

I don't think you've posted this as an official bug report just yet have you, probably a good time to do so know. Provide links to as much of this thread as needed and Tannin can add it to the other tasks he has laid out before him.

 

Sorry I couldn't offer anything more than this.

[zilav]

MO incorrectly parses TES4 plugin header record. Nothing there to be more or less "stringent".

[KeltecRFB]

  On 2/3/2015 at 2:16 PM, zilav said:

MO incorrectly parses TES4 plugin header record. Nothing there to be more or less "stringent".

Is this what is effecting Panzer and Destruction ESM to be recognize as such?

 

@GrantSP, thank you ... https://issue.tannin.eu/tbg/modorganizer/issues/997

Edited February 3, 2015 by KeltecRFB

[GrantSP]

  On 2/3/2015 at 2:16 PM, zilav said:

MO incorrectly parses TES4 plugin header record. Nothing there to be more or less "stringent".

The sub-record in question shows in a hex editor, the only tool I had that would open it since I lacked all the masters, as XXXX. I've not seen this in any of the other esms on my machine. I have no idea what that flag means, but I'm assuming MO either doesn't know what it is or is saying that it shouldn't be there, both options might be termed 'stringent' or 'inadequate' depending on which side of the fence you come from. My terminology isn't meant to imply fault in either tool, but I can see that it may in fact look like I'm saying xEdit is missing something. My bad!

 

Checking @Tannin's comment on the Bug Genie report, he says this, the sub-record: XXXX, is to convey "oversized". I guess it means there will need to be a tweak in the code for MO's next iteration.

[KeltecRFB]

No worries GrantSP, you did your best and like always appreciate your support.  Besides, that is how you learn.