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

Shogun 2 schemas out of date/missing values #3

Open
ComradeCheekiBreeki opened this issue Apr 9, 2023 · 1 comment
Open

Shogun 2 schemas out of date/missing values #3

ComradeCheekiBreeki opened this issue Apr 9, 2023 · 1 comment

Comments

@ComradeCheekiBreeki
Copy link

ComradeCheekiBreeki commented Apr 9, 2023

Shogun 2 schemas appear to be missing database information compared to the Assembly Kit files and how they appear in DAVE. Other values do exist in the schema but are recorded under incorrect or different names, or their default values vary (like some boolean values having a default of 0 rather than false).

As an example, loading the units table in DAVE there are quite few differences from the schema provided with RPFM. The fitness and era columns are missing, the pdlc column is missing (though it is blank in every base-game unit) and upkeep_cost is labeled as unkeep. The vo_actor_numbers value is also labeled as having a default value of None when according to DAVE it should be "0". There are similarly strange issues in the unit_stats_land table, where (what I assume are supposed to be) dismounted_loose_formation_* values are called loose_loose_formation_* in the schema. fatigue_resistant is called fatigue_resistance, is_immune_to_attrition is called is_inmune_to_attrition, etc. On top of all this, almost every table I've loaded in RPFM has a different and much more nonsensical column order.

Although I can't be certain, I noticed the game hard-crashing at load with database info that previously seemed to work fine in TWEAK which is not something I've ever seen Shogun 2 do, and I suspect it may be because of this (the dumps record a division by zero error).

@ComradeCheekiBreeki
Copy link
Author

ComradeCheekiBreeki commented Apr 9, 2023

Update: The divide-by-zero error turned out to be decidedly not caused by the schema, it was my own stupidity. I am still leaving the issue up as the other problems still remain, though I'm back to being unclear on whether or not they have any real effect (beyond being very confusing).

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