Closed ssbucarlos closed 2 years ago
Setting the max_anisotropy
to 0
is no longer supported. The issue is that this used to just be an integer field. Valid values for max_anisotropy
are the enum variants One
, Two
, Four
, Eight
, Sixteen
. At the graphics API level, anisotropic filtering can be 1x (regular filtering) up to some device defined limit (usually at least 16x).
From my testing, 0 just gets set to 1x. Values below 2 don't appear in any in game numatb files. For ssbh_data_py, just set max_anisotropy
to None
to disable anisotropic filtering.
How should i go about modifying this .numatb to support the new max_anisotropy value? I tried loading up this outputted fighter with the bad .numatb in crossmod and re-exporting a new .numatb from it and that didnt do the trick, same error after export. Even after changing the max_anisotropy values in all the samplers, so im not too sure how to go about fixing this numatb.
Open it in an older ssbh_lib_json and change the 0's to 1 or 2. MatLab may also work.
That did the trick, thank you!
c00.zip Newest ssbh_lib_json.exe and ssbh_data_json.exe cant parse this and its also not parsable with ssbh_data_py as a result. Previous versions of ssbh_lib_json can parse it. Works in game. The error is