It seems like Unity 2.6 was more stable compared to 3.1 (f4). Having a lot of freezes lately. What do you guys think?
P.S. An irc channel for unity would be good. 
Iām sticking with 2.6.1 for the foreseeable future. Iām pretty disappointed with 3.x.
As for an IRC chat, check this out: http://www.unifycommunity.com/wiki/index.php?title=IRC
For me, 3.1 is no more or less stable than 2.6 was. Itās substantially improved in so many ways that I wouldnāt really want to use 2.6 at this point.
āEric
@Eric - I wish I could say the same. 
Perhaps the differrence between us is that youāre on a Mac and develop mostly for handhelds and Iām on a PC developing for high end Windows stand alones. I havenāt really used my Mac for Unity development much, since I upgraded from Tiger to Snow Leopard it runs Unity games like a snail. All the major āimprovementsā in 3.x have come at the cost of something else. Of everything that Unity 3.x has brought over 2.6.1, the only thing I can see a benefit to are the physics engine updates, but even those are only partially exposed. Yeah, Iām pretty disappointed.
Iām on windows too (win7 64bit) and the stability didnāt drop further (as if more than 10 -15 crashes an hour was possible)
that being said, I donāt work with terrains which I know from experience that they help you down the toilett
I use the latest version with Windows 7 and have had no crashes or freezes yet. I like it a lot better than 2.6. 
then you are either lucky or have not the 64bit version or have not enough speed on the parallel end for www calls to get the dreaded thread context error and killing unity with a single blow (or you are āinsaneā and donāt protect your system - though unity is on my exclusion list and should not be tracked by my security software)
I canāt say unity never crashed on me once or twice, but itās pretty darn stable! both 2.6 and 3.x !! ā¦ 3.x brought a couple of things that I was waiting for! Maybe to some it didnāt improve āas muchā as they expected, but itās definitely an improvement!
Iām on a mac, using the 32 bit version, and havent had any problems at all.
Mac never had the problems that unity 2.6 and the async / www threading introduced actually ā¦ so yeah there you are on the lucky side (at least in this respect, there are other problems with prefabs messing themself up if you donāt store scenes along them and alike that can cause you going nuts)
It depends, not really surprising huh?! I think it makes sense sticking to a older version if you have a concrete project youāre already running successfully or if you just know what to expect with a specific version and there show up major showstoppers with the latest version or if itās a payed job and no one pays you for porting/testing, ā¦
Beside of such issues, using the latest version mostly makes more sense as things only move on and beside of new problems a new version normally also introduces enhancements. So it really depends on your specific situation, you have issues in 2.6.1 here and with 3.1 there. For starting a new project, playing around or having no concrete project, i recommend using the latest version.
Windows 7 Enterprise, 64-bit edition for me. Using both Microsoftās built in firewall, router firewall, and dsl modem firewall. Only time Iāve had problems is my own scripts going into an infinite loop (And md5 not generating the same hash as php does, but thatās been a problem). They really should have the engine run as a separate thread from the engine controls, that way you can break out of infinite loops without ending the task.
Iāve had no random crashes from 3.1, but I had them quite often with 2.6. I would guess that had something to do with the 64-bit architecture.
I also have my project going through drop box and use it on multiple computers, including the 32 bit XP Pro Iām typing this on. Iāve had no crashes on this as well. I am also going to state that both systems have ATI video cards. Maybe thatās why?
Iāve been mostly developing for the desktop this year.
Running Snow Leopard here, no issues (except for a bug in the 5870 drivers that makes large meshes over a certain number of vertices/triangles run stupidly slow). Upgrade to 10.6.5 if you havenāt already.
The only thing I can think of is not having shadows for point/spot lights in forward rendering, but honestly very few people ever used those, nor did they work great in the first place (for point lights anyway). That doesnāt help those few who were using those of course, but objectively speaking, all the new language/editor/sound/physics features outweigh that by a large amount.
āEric
Yup, did that and lost image effects after I did. If I recall, you got a brand new shiny Mac Pro, so could be why everything is working so nicely. 
Except when youāre one of those few people who use point lights. Cāest moi. Without them everything else is worthless eyecandy.
Unity 2.6 had a mood about it that 3.1 does not and vice versa.
I must say that Iāve had about 2wice as many crashes with 3x that with the 2x version. However, Iām still satisfied with 3x because it seems to be way more efficient, as Unity 2x used bake my mother board to a crisp.
Maybeā¦no problem with image effects in 2.6.1 and 10.6.5 here. What graphics card do you have?
āEric
Same olā X1600 in my MBP. As soon as I updated from 3.0 to 3.1, poof! went the image effects.
I think weāre talking about different thingsā¦I mentioned upgrading the OS to 10.6.5. However, I have no issues with image effects in 3.1 either. The X1600 is getting rather long in the tooth, but it should still handle those, of course. Especially if it did before.
āEric
still using 2.6.1, wanna finish first project in it first, then move to what will be available and buy a license
confessions of a sleepy mind: colour driven taumel enjoys v3 more, huah!