Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TES3Merge v0.5 MissingFieldException #6

Open
abitoftaste opened this issue Jun 4, 2019 · 6 comments
Open

TES3Merge v0.5 MissingFieldException #6

abitoftaste opened this issue Jun 4, 2019 · 6 comments
Labels
bug Something isn't working

Comments

@abitoftaste
Copy link

Eccezione non gestita: System.MissingFieldException: Impossibile trovare il campo 'Utility.Common.TextEncodingCode'.
in TES3Merge.Program.Main(String[] args)

@NullCascade
Copy link
Owner

NullCascade commented Jun 4, 2019

Can you send your complete TES3Merge log file?

Are you sure you installed the entire release? Seems like you may have not updated Utility.dll.

@abitoftaste
Copy link
Author

abitoftaste commented Jun 5, 2019

Oops! sorry my bad I did not overwrite old Utility.dll, Utility.pdb and it crashed before generating the log
Updating the Utility files fixed it.

[EDIT] tes3cmd clean / tes3lint seem to find several duplicated records in generated Merged Objects.esp
[EDIT2]fixed file names in the archive
tes3cmd clean Merged Objects log.zip

@NullCascade
Copy link
Owner

Can you re-run this with record dumping turned on?

@abitoftaste
Copy link
Author

tes3merge.log should be with DumpMergedRecordsToLog = true already in the zip

@NullCascade
Copy link
Owner

Can you give this build a try? I think tes3cmd is wrong to claim it's a duplicate record, because it is overwriting an earlier esp. A bug in tes3cmd cleaning as far as I'm concerned. However, there's also an issue where FNAM subrecords aren't being merged correctly that this should fix:
TES3Merge.zip

@abitoftaste
Copy link
Author

abitoftaste commented Jun 5, 2019

tried the last one
TES3Mergelog.zip

I think tes3cmd considers equal records with the same SCRI subrecords in different order so this could explain why it is stripping them (correctly IMO as they are the same in game)

out2.txt
out.txt

I think there may still be some problem preserving negative quantity in containers
[EDIT] uhm, or may be not in this case as they are changed to positive by the Complete Trade Fix.esp so probably better get then positive

I think the one thing remaining is deciding if it is worth considering equal records with the same type/value of subrecords but in different order (e.g. see also BOOK bk_mixedunittactics)

Untitled 1

@NullCascade NullCascade added the bug Something isn't working label Feb 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants