You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, there are limitations to what can be done with traffic colors. These are:
The color allocation amount Allocmust be kept the same. Even if Bundle Manager can read files with a different allocation amount, the game can't handle it.
The number of colors Num_RandomTrafficColours can be decreased so long as the allocation amount remains the same, but can't be increased unless it's below the allocation amount for some reason.
The problem boils down to the AttribSys editor introduced in #16 being written for too specific a target—it edits the values in a vehicle file and nothing more; the vault is not treated as the database it is. The end result is that any change to the file structure (say, adding a color or two) causes said file to become unusable, even if the bin data is perfectly valid, because none of the associated references in the vault have been updated.
The only reasonable solution to this is a complete rewrite of the AttribSys editor using something like VaultLib, though that particular library would have to be fixed as it doesn't currently work correctly with Paradise vaults. Hacked solutions specific to the colors issue are technically possible but not even close to being worthwhile.
Realistically, I don't expect to resolve this issue. It's more likely that BM's editor will be rendered obsolete by another tool.
The text was updated successfully, but these errors were encountered:
Currently, there are limitations to what can be done with traffic colors. These are:
Alloc
must be kept the same. Even if Bundle Manager can read files with a different allocation amount, the game can't handle it.Num_RandomTrafficColours
can be decreased so long as the allocation amount remains the same, but can't be increased unless it's below the allocation amount for some reason.The problem boils down to the AttribSys editor introduced in #16 being written for too specific a target—it edits the values in a vehicle file and nothing more; the vault is not treated as the database it is. The end result is that any change to the file structure (say, adding a color or two) causes said file to become unusable, even if the bin data is perfectly valid, because none of the associated references in the vault have been updated.
The only reasonable solution to this is a complete rewrite of the AttribSys editor using something like VaultLib, though that particular library would have to be fixed as it doesn't currently work correctly with Paradise vaults. Hacked solutions specific to the colors issue are technically possible but not even close to being worthwhile.
Realistically, I don't expect to resolve this issue. It's more likely that BM's editor will be rendered obsolete by another tool.
The text was updated successfully, but these errors were encountered: