Unity 4.3 has more bugs and problems then any other version…I think they posted it too soon…i deleted an asset and it froze…had to retry with loading assets…monodevelope doesn’t work right…errors right off the bat, without loading any assets…I’ll just stick to 4.2 until it works right…
Nah, I tested it a lot and it’s generally more solid than 4.2. If you find a specific bug, use the bug reporter.
–Eric
Eric, with all respect, but declaring all fine just because you havent found any problems doesnt make the problems go a way. It just shows that either Unity was not willing to fix the bugs for the sake of a rushed release, or the current Beta tester becomes a bit blind already. No offence. That`s the way it is with betatesting. After a while you refuse to see the baddies. I´ve seen this happen quite often, and it happens to me too.
4.3 has in fact quite a few obvious problems from what i can see here. And this after the very first actions. I have just upgraded yesterday and am busy with confirming and writing four Bugreports already where the beta testers should have stumbled across. Well, at least for two of them.
Holding alt+doubleclick doesnt bring up the project wizard anymore, but the properties of the shortcut. 4.2 works fine that way. So its definitely not me doing something wrong here nor a system thing. 4.3 behaves different than 4.2. Something has changed.
I have run the reimport of my project three times now. The first two times unity simply froze. Dear Developers, silent freeze is a very very bad thing! The baddie is an older blend file that imported just fine in 4.2.
One of my animations does not reimport, telling me something about needed muscles … . Not that this animation did not import proper in 4.2. This one is reimporting the whole project again to find out which one that was. Because i have just read the warning, and haven`t really followed it then, being busy with the other quirks. Fingers crossed …
The worst one is that Unity 4.3 runs my game visibly slower than 4.2. A showstopper bug, because lower performance is a no go. The fps went down from 60fps to 40fps with the same scene and same setup and same action. This one will surely keep me busy for a pretty while. I have to find out if it is the editor only, or if the exe shows this behaviour too. And when possible i have to find which asset is affected.
So this day is definitely lost with just trying to reproduce what is wrong, preparing test cases, and writing bug reports. And that`s not really productive. I do the job now that should be done by the Betatesters. They have the benefits of being a betatester, i have the work.
And i am sure that half of my reports gets ignored again as usual. My reportlist is half and half. Half fixed, half ignored and open since eons. I have open bug reports from version 2.6. Not even declined, which is something i could live with. On the other hand, I have declined bugs that were very obvious and well documented. Which is equal bad than being ignored. But anyways. I will not report them again.
Really, why should i report bugs at all?
EDIT, okay, the alt+doubleclick issue was my own stupidity. Works fine when the icon resides in the taskbar. One less to worry …
About performance, I think each Unity version from 3.4, has been slightly slower in general terms…
this performance loss is a real huge issue 
Yeah I’ve seen at least a %50 drop in performance in the Standalone Windows Build. In the Editor it is fine.
I haven’t encountered any other ‘bugs’ though but this performance issue is a Showstopper and needs to be addressed quickly.
I too remember this happend a couple of times.
This said I hope once they fix the current obvious isues we won’t have to experience that couple of FPS downgrade again.
Isn’t it a standard Windows functionality? Alt+double-click or Alt+Enter always open the property window. I usually launch Unity from its icon on my taskbar, but when I do it from the desktop I have to press Alt right after I have double-clicked the icon.
As always please use the bug reporter with example project/screenshots/videos of your “bugs”. Posting your problem here on the forum does very little to solve issues.
On its way already 
I disagree a bit at the no use part though. It helps us users to talk about the not fixed bugs. And sometimes you need somebody to help with confirming a bug. That`s of course no substitute for submitting a bug report.
As edited above, T´was me being stupid here. It still works as thought 
No, the point is that 4.3 doesn’t really have more bugs than usual and wasn’t a rushed release. I never said or implied that it was perfect (“generally more solid” means that it’s not totally solid, because it isn’t). I’m quite aware that there are bugs I never encountered simply because I don’t use all the features if nothing else, but the flip side is that just because you encounter bugs, doesn’t mean everything is broken and it’s a rushed release. Perspective please.
Which two? I didn’t encounter any of that. The worst I found was that 4.3 doesn’t seem entirely stable when working on upgraded projects. I recently updated a 2.6 project to 4.3 (which went surprisingly well actually), but while working on it, I kept getting harmless but annoying GUI error messages printed randomly. Being random, I wasn’t able to make a reproducible bug report case. I tried reimporting assets but that didn’t help. I had an upgraded 4.x project where it froze once when saving a scene. Again, random. It seems well-behaved with new projects though.
As far as alt-doubleclicking goes, I find it’s simpler if you have the project wizard turned on in the preferences. Then you don’t have to worry about it.
–Eric
That’s probably one of the worst bugs I can think of and definitely prevents me from updating to 4.3.
Okay, then i have misunderstood you. Apologies. It was nevertheless the impression that i got from your sentence.
The fps drop is something obvious and common from what i can see. And the blend file issue. They were so obvious that they jumped directly into my face. But yeah, i have a golden hand to stumble across the bugs first.
I didn’t see any fps drop here. All my .blend files imported fine.
Also, I can’t believe I didn’t think of this before, but I just tried deleting the Library folder and having Unity rebuild it with the ex-2.6 project, which so far seems to have cleared up those spurious error messages I was having. So I’d probably recommend doing that for upgraded projects.
–Eric
Going to have to disagree with you. This is the first update in which I’ve suffered from, not 1, but two HUGE, bugs (Occlusion culling and quartered performance). Never had a problem like this before.
Yeah, obviously you didn`t stumble across the issues. And i wonder why
I cannot blame you as a personal tester for not finding the issues. I know bug hunting too well for that, and respect the work of you betatesters. And when a bug does not happen to you then it does not happen to you. Some bugs will always make it through, no matter how hard you test. But when the average Betatester does not longer stumble acrioss the average bugs that can be found by the average user in the first moments, then it`s time to rethink the betatesting strategy at Unity side i would say. This usually means it´s ime for some new testers that represents the average user a bit better.
Its not uncommon that a project lasts a few years. Mine is two and a half years old now. Means you always have to consider old material when you change something like the Blender importer*. At least the fps drop issue shouldnt be able to pass through. There are quite a few users now who experiences this problem. And it`s a showstopper issue.
*I havent Blender connected with the *.blend file. Maybe thats my issue at all. It should not import blend files. I wasn`t even aware that i have a blend file in the hierarchy up to this point. But previous versions upgraded just fine, without a silent crash. So something has changed.
Manually editing a project file when upgrading? Are you serious? This may fix some issues, but is a sign that something goes wrong with the upgrade process.
The fps drop seems to be a Windows thing so I had no way of knowing about that. I doubt the percentage of beta testers using Windows/Mac is all that different from average users though. As to why the Windows users didn’t find it, maybe it’s not actually as common a problem as it may seem. Or maybe they never made builds?
Deleting caches is hardly an unusual thing to do. Obviously it ideally would upgrade without having to do that (if indeed that actually had any effect and it’s not some placebo), but there’s no need to act like it’s some weird horrifying thing.
–Eric
Thats what i have meant with i cannot blame you personally. Too much variables. And when you work on Mac then you cannot find a Windows bug. But thats what i mean with having a look at the whole betatesting team then. Because the betatesting team is also made of Windows users. And theres obviously a gap. Or the fps bug wouldnt have passed.
There is no button in Unity to do that. So i have to disagree here. The user shouldnt be forced to edit a project file manually through the explorer. But yeah, its just my opinion. Maybe we will find the button to clear the cache in the next Unity version
I agree completelly with Tiles.
The Unity team has to reconsider the beta testing program for the next updates. I hope they release the 4.3.1 (with the bug fixes) any time soon.
Actually, I think messing with project folders outside the Unity Editor is an unusual thing to do. For example it’s not recommended to move around assets with the Explorer/Finder (http://docs.unity3d.com/Documentation/Manual/ImportingAssets.html). I don’t see any (official) documentation that tells it’s safe to remove the Library folder manually.