Unity 4.1.1 update rolled back, sorry

News & General Discussion
1

We’re investigating a problem with just-released Unity 4.1.1 where user projects that contain precompiled assemblies (like many asset store packages), cause the project to no longer compile in MonoDevelop and VisualStudio.

We are still investigating, but seriously considering reverting the change (assembly signing) that caused this. Because of this we strongly recommend asset store sellers to not yet adjust their packages to be 4.1.1 compatible, as that will render them incompatible with previous Unity versions. Since the only change in 4.1.1 (besides bug fixes) has been one that has caused this problem, and provided no user visible feature, we have temporarily pulled 4.1.1 from the website.

We’ll keep you up to date in this thread. Right now it is looking likely that we’ll soon do a 4.1.2 release where we no longer sign UnityEngine and UnityEditor which would make this problem go away.

Apologies for this inconvenience, stay tuned for news.

2

It’s OK, since asset store sellers stick to 3.5.7. :wink:

However, great to see such a passion on fixing things, especially on weekends… :slight_smile:

3

I assume we can install over the 4.1 version and should be good?

4

Yes, 4.1.0 is good.

5

Thats nice to hear. We believe in Unity. So bugs come in. We understand

6

Better a smooth patch rather than release something half-baked. You can do it guys! :slight_smile:

7

Could the new 4.1.1 fix the problem with UnityScript files not compiling in MonoDevelop?

I’ve tested on several of my developer’s systems and if there is a JS file in the first pass compilation (Standard Assets, Pro Standard Assets, Plugins, etc.) I get the following error when I try to build in MonoDevelop (the version of MD that ships with Unity 4.1):

Namespace ‘UnityEditor’ not found, maybe you forgot to add an assembly reference? (BCE0021)

Fix it, fix it pleeeease! :mrgreen:

8

Had the same issue which got fixed in 4.1.1. Hope it stays that way with 4.1.2.

9

Hi there,

We have built some demo scene for our current project to show, but once we play the .exe file, if we enable the Fullscreen tick on the splash screen, our monitor flashes black and immediately returns to Desktop. However, the game is indeed running, as we can see its process in the Task Manager. Is there anything we are missing, something we must do or code in order to get this working? We are pretty sure that everything in our scripts as well as Player Settings is OK, but we don’t want our final game to be played just windowed. Any ideas?

By the way, we are working with Unity 4.1.1f4, Dx11, and the Build is targeted to PC, Mac Linux Standalone x86 - x64.

10

You should update to 4.1.2: http://unity3d.com/unity/download/

11

Hey!

Just installed 4.1.2. It seems it still has the issue ‘Namespace ‘UnityEditor’ not found, maybe you forgot to add an assembly reference? (BCE0021)’.
Is new information available regarding this? Thanks. :slight_smile:

12

Yes, 4.1.2 seems to suck big time. I upgraded to it and my Android performance while in-game dropped literally to like 50% of the previous frame rate.

Installed back to the older version of Unity 4.0.0 and the Android performance skyrocketed…

13

Yeah, this latest build pops up quite a lot of annoying log erros that comes from Unity itself.

14

Its fine I guess cause unity will find out the bugs and fix them soon so no need to worry :smile:

15

Did you submit a bug report?

16

We still have this issue, is it going to be solved anytime soon? We’re almost finishing our current project. It is weird since the x86 version DOES work. Thanks!

17

Did you submit a bug report?

18

We did, back in the day.

EDIT: So, fullscreen works by DISABLING the Display Resolution Dialog option in Player Settings before building. When unchecking that option, the SplashScreen does not show at all, but instead the game runs directly. Well, at least I already know what was happening :slight_smile: Thanks!