4.6.1 Broke Prefab Saving and Model Scaling

I can't think of why there wouldn't be many many threads about this unless it was only affecting our project, but the weird bit is that we have two projects running separately and they are both having the issue.

No one on my team that has upgraded to 4.6.1 can save prefabs anymore (i.e. the changes don't show up in Git at all) and neither can they change the Scale option in the model import settings for a .FBX. It's locked to 0.01 (not greyed out, but just reverts immediately after defocusing the float field).

Is anyone else having this issue or know of a workaround? I'm concerned that Unity won't release a patch fix for it if we're the only ones experiencing this.

 

We are having the same issues but it also affects scenes saving. It worked just fine in 4.6.

 

Gaaaaaa... seriously? Just stopped the 4.6.1 download...

@vaclav_b : I assume you meant it worked fine in 4.6.0.1 (not 4.6.1)?

 

I have the same issue in 4.6.1
Project was warking perfectly in 4.5.5p5 but now i can't save any changes.

 

Yeah I Edited my post.

Also I think I found the culprit, seems like ex2d is causing the issues for us.

 

I submitted a bug just now using the built-in reporting tool, but it didn't spit out a bug number. Would it already be in the Issue Tracker for me to find?

Edit:// Got an email. This link: http://fogbugz.unity3d.com/default.asp?655598_tm5kulk14mcekrb1. Bug number is 655598? I think.

 

We have the same problems, except we can save prefabs. The import settings can't be changed at all, and the scene saving doesn't work. Other older projects work normal in 4.6.1

 

We got the same problem within our project.

 

I don't see the bug in the issue tracker - what's the right way to follow this and get support for it?

 

This is not a Unity bug. This happens because UT fix OnWillSaveAssets method. This means that before you can declare it with Void return type and it will save all assets, now it should return paths that should be saved. So if you have this method that have viod return type or this method returns null Unity will not save your assets. To fix it just look for this method and fix it like that:

Code (csharp):

1.  
2. static string[] OnWillSaveAssets(string[] paths) //Should return string[]
3.   {
4.   //your code here
5.   return paths; // return filepaths that should be saved
6.   }
7.  

this behaviour detected form 4.6.0p1 and you can see in release notes:

• (638865) - Editor: Fixed AssetModificationProcessor.OnWillSaveAssets checking out files that were not Saved and OnWillDeleteAssets always marking assets for delete.

 

Hm, my underlying tools framework may be using something like that. I'm not seeing any references to that specific function in our project; do you know if there are other functions that perform something similar?

 

So possible that this function used inside some dll that you are use, its time to check for updates

 

@PrefabEvolution was on the money. Fabric was using the old version of that function and causing our asset saving to break.

Fabric's developer has been contacted and they are releasing a patch very soon.

 

This happenns because Unity doesn't verify method signature when calling methods like this. In docs this method declarad with string[] return type and guys that use this method with wrong signature now fails, but it would be better if Unity can check method signature before calling method and throw an error.

Or you probably should use explicit method declaration regardles to unpredicable reflection method invocations

 

I mean that you should do that long time ago, so that guys who don't want to do things proper or read docs should get a lot of warning messages in console. You probably should expose thing like that in different way. In this example user have very big error prone. If you can make AssetModificationProcessor abstract with methods that user can override, you will force them to do it right. And on invocation you just instantiate all classes that derived from AssetModificationProcessor cache them at some list and invoke method directly without any reflection that 5 times slower than direct virtual method call.

 

Just:

Code (csharp):

1.  
2. foreach(var assetModificationProcessor in assetModificationProcessors)
3. paths = assetModificationProcessor.OnWillSaveAssets(paths) ?? paths;
4.  

 

I had the same problem few days ago (on 12th of December) updating from 4.6.0 to 4.6.1p1.
I was not able to save any scene or prefabs changes.
This is the bug number: 655637

 

nonetheless, thanks for finding the reason. we could fix it in our project.

 

The last patch resolved the problem for us, but my bug number is still open and I don't know if there is a way to close it by myself.

 

So can we expect that in 4.6.1p3 (Jan. 8th?)

 

I am very thankful for this thread, it was killing us. I just switched the code to return the same string and everything worked.

 

Ouch that's painful. Looks like the latest patch (p3) fixes the saving issues (scenes and prefabs -- neither were saving for me, though for scenes save as to a new file was working, and for prefabs creating a new one worked, but that got confusing really quickly).