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

MelWeapDnam の定義の誤り #38

Open
valda opened this issue Aug 9, 2012 · 0 comments
Open

MelWeapDnam の定義の誤り #38

valda opened this issue Aug 9, 2012 · 0 comments

Comments

@valda
Copy link
Owner

valda commented Aug 9, 2012

NVNexusから転載: posted @ 12:08, 27 Oct 2011 , edited by moho at 12:09, 27 Oct 2011

There appears to be a bug in 14.4 related to the definitions for Melee weapons. Or at least, FNVEdit was reporting this as a bug since it can't understand the output of Wrye Flash when it's in this order. I'm not ruling out that this may be a bug with FNVEdit, but regardless, to fix Melee weapon definitions:

Go to Mopy/bash/bosh.py and move the two lines:

MelString('VANM','vatsAttackName'),
MelString('NNAM','embeddedWeaponNode'),

from ABOVE the "MelGroup('modelWithMods'," block, to BELOW that group. That combined with the two following lines should look like:

MelString('VANM','vatsAttackName'),
MelString('NNAM','embeddedWeaponNode'),
MelFid('INAM','impactDataset'),
MelFid('WNAM','firstPersonModel'),

This matches the order in FNVEdit and FNVEdit no longer gives errors after this fix. Previously, using Import Names etc. on such weapons would result in a slew of errors in FNVEdit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant