Scene assets corruption.

Sometimes there's a weird bug that I see (a rare one, fortunately). My assets in scene get corrupted: their values change to something like 0.111111
And that ruins the whole scene. I can't find what causes that because it's always sudden. I open editor — and here it is, 0.1111 mess. The only thing I found in common was that only values with decimal fractions got corrupted integer values were ok. E.g. if you had value of 10.0 then it would be ok, but 10.5 would be something like 10.11111, 11.1111 or 0.11111
I tried several times to get latest commit and reproduce my actions to get it again but no luck. Can't even figure out what's wrong, and that's annoying. Sometimes it's really serious when I forget to commit changes in the evening and when I open editor in the morning I see all my yesterday work ruined, and that's driving me crazy.

Is it just me or anyone else got this problem, too? It doesn't happen often but it does happen.

 

We have had similar issues with repeating 1's showing up in values for positions, float fields, etc on some workstations. I think the best luck we have had with addressing it is re-importing the entire project on afflicted machines.

 

Glad to hear that I'm not the only one. The bug is rare but annoying and sometimes can be very desctructive.

 

Also having this issue here. I'm currently in the process of figuring out repro steps. I would say with our team, it's not that rare, but is rare with unity users.

 

Same here; lots of ".11111112" in various fields. Some sprite pivots, some transform positions, some navmesh settings - it's all over the place. The decimal point shifts around - sometimes it'll be 1 or 11 to the left of it. We first noticed the problem because sprite heights and pivot positions got changed, which makes it quite obvious when it's happening!

The only way to recover is to shut down Unity, revert any files that got saved with this corrupted data, and restart.

I've poked around with Visual Studio's debugger and verified that in memory, before and after asset processing, the fields are correct, and for the fields I was looking at (sprite pivots and heights) the Unity Editor was showing the correct values too. On running the game though, and on saving the assets and viewing the file contents, that's when the .11111s appear.

I'm using Unity 5.2.2p4 64 bit, on Windows 10 64 bit. This is affecting others on the team with the same setup. Interestingly, others on the team using Mac aren't seeing this corruption at all.

It's happening very often; every day for the past week it's happened on a few machines.

 

Looks like it's fixed in 5.3! http://answers.unity3d.com/comments/1102919/view.html

 

Excellent! Thanks for the link!