Asset Seraliziation setting to: force text
- giorgiodeluca
- Topic Author
- Offline
- New Member
Less
More
- Posts: 17
- Thank you received: 0
6 years 11 months ago #2707
by giorgiodeluca
Asset Seraliziation setting to: force text was created by giorgiodeluca
hi,
if you set Asset Serialization setting to force text in the project setting / editor
(required to use unity with SourceTree for version management)
when I add I2 Localization 2.8.2 a5.unitypackage gives me error: Binary to YAML conversion: type SInt64 is unsupported
thanks
if you set Asset Serialization setting to force text in the project setting / editor
(required to use unity with SourceTree for version management)
when I add I2 Localization 2.8.2 a5.unitypackage gives me error: Binary to YAML conversion: type SInt64 is unsupported
thanks
Please Log in or Create an account to join the conversation.
6 years 10 months ago #2721
by meganlfox
Replied by meganlfox on topic Asset Seraliziation setting to: force text
We've got the same issue. We have Asset Serialization set to Force Text (it's a requirement of Unity Teams, but it's also just needed to make Unity be ok in source control), and as a result, I2 Localization is dropping the error:
"Binary to YAML conversion: type SInt64 is unsupported"
when we import the plugin from the asset store. I have no idea if it's still safe to use anyways, but I seriously doubt it?
"Binary to YAML conversion: type SInt64 is unsupported"
when we import the plugin from the asset store. I have no idea if it's still safe to use anyways, but I seriously doubt it?
Please Log in or Create an account to join the conversation.
6 years 10 months ago - 6 years 10 months ago #2722
by meganlfox
Replied by meganlfox on topic Asset Seraliziation setting to: force text
AH HAH!
If you don't import Examples, this error won't appear. Which means the error relates to an asset in the examples, not anything in the main library.
So you can just click the checkbox besides the Examples folder to not import them with the rest, that will remove the error, and presumably the main library is then perfectly safe to integrate into your source control / project / etc. I'm uncertain what specific asset in Examples isn't importing correctly, though. Hopefully it isn't the localization db or something - I'm going to dig a bit deeper.
EDIT: It's the scene files in Examples/Scenes. Disable that folder, everything imports fine. I'm going to guess the dev had Unity set up in a way that generated scenes which now can't be converted to text assets.
If you don't import Examples, this error won't appear. Which means the error relates to an asset in the examples, not anything in the main library.
So you can just click the checkbox besides the Examples folder to not import them with the rest, that will remove the error, and presumably the main library is then perfectly safe to integrate into your source control / project / etc. I'm uncertain what specific asset in Examples isn't importing correctly, though. Hopefully it isn't the localization db or something - I'm going to dig a bit deeper.
EDIT: It's the scene files in Examples/Scenes. Disable that folder, everything imports fine. I'm going to guess the dev had Unity set up in a way that generated scenes which now can't be converted to text assets.
Last edit: 6 years 10 months ago by meganlfox.
Please Log in or Create an account to join the conversation.
Time to create page: 0.129 seconds