2.0 Woes

Unity Engine
1

I’m having several show-stopper issues with Unity 2:

  1. Many, possibly all, my models appear to have changed scale. (They are from Cheetah 3D.)

  2. Some objects seem to have lost their collision properties (stuff just falls through one of my terrain meshes)

  3. An animated figure that had been modified in Unity (e.g. had a part deleted) losing their link to the “prefab” (i.e. the original model) in at least one case became wildly distorted in Unity 2.

I really think the installer should warn you that it’s replacing the old version or better yet provide an alternative. I forgot to rename my Unity folder on my laptop, so now I need to reinstall it (for the second time).

Going back to Unity 1.6.1 (again) for now.

2

This may sound silly, but did you update your standard / pro resources after opening the project? That sometimes makes problems go away for me.

That and copy your old projects to a new 2.0 project folder, that way you will still have your old projects in case you have problems.

3

It sounds like you just had problems with updating your projects to 2.0. I don’t really know if this is a bug or not, because all of my projects were built with 2.0 alphas/betas. However, if this is case, you’re projects won’t load back into 1.6.1 that you are “going back to.”

4
  1. Yes, I imported standard assets.
  1. Not being compatible with existing files qualifies as a bug in my book.

It looks to me like any internally stored models (that are no longer attached to a “prefab” external file) get totally borked, but external models are reimported and are fine except that scales change.

  1. I have thorough backups.

  2. I had the same issues with the alphas, tried to report the problems (including submitting files) and got no response. I assumed folks were busy.

5

Sorry, I should been a little more clear. I meant, “I cannot confirm this bug for you, because all my builds were in alphas/betas.” Just wanted to make sure that you knew that 1.6.1 projects that get imported into 2.0 won’t go back.

6

It seemed that very few folks actually were importing old projects into 2.0 during the testing period (based on the mailing list). Not a very good way to test, but understandable.

7

Log a bug and post a project folder if you don’t mind. Sorry for the slow response but with Unite and the release and the website update, we’re all a bit strapped for time and spare bandwidth… We’ll get on it as soon as we can.

Question: you stated that you imported the Standard Assets, was that meant as “I REimported the standard assets after having opened my project in 2.0” (so they over-write the pre-existing standard assets)? Just want to be sure I’m understanding what’s happening on your end (please include notes to that effect in any bug you log too, thanks).

8

Yes, exactly, I reimported Standard Assets via the Assets menu after updating.

Note that I had the same exact problem in 2.0a10.

I was trying to reinstall 1.6.1 in an effort to build some simple 1.6.1 projects (the project in question is ~200MB) and then see if I could replicate the issues using the simplest possible inputs when I updated to 2.0.x in order to provide useful replicable bugs – but as you’ve seen in my other thread, I’m hosed there too.

I might note that (since Unity uses external apps to import models) I tried reinstalling C3D (different versions) and deleting every other version.

9

(Case 13625) Many of my meshes are not rendering in Unity
(Case 13624) I tried to import a raw terrain

10

In this screenshot we see an imported ball (from C3D) and its spherical collider. In Unity 1.6.1 these two were the same size.

50099--1840--$picture_2_179.png

11

For what it’s worth, I imported several old projects for some of the alphas and betas and never had a problem, but didn’t see any need to say so. Generally only problems were mentioned, so if people were having problems with importing old projects I’m sure they would have said so.

–Eric

12

It’s possible I’m doing something uniquely or unusually bad.

Please excuse my venting.

One thing seems consistent:

If I created an animated model in Cheetah 3D, imported it, then modified it in Unity so that its link to the “prefab” (i.e. the original model) was broken, then the model is seriously borked.

I realise that I probably shouldn’t do this from a project maintenance point of view, but I can and did, and it should work properly.

However, I’m seeing minor issues all over the place – maybe I was the only 2.0a10 user who modeled mainly with Cheetah 3D. In any event, I couldn’t complain on the mailing list because I was never set up on it properly (which I also tried to have fixed with no luck). I didn’t post anything here because I was under informal NDA. I don’t know if anyone else was in a similar position, but while I love Unity, and Unity 2 is very impressive, this is not release quality software.

Other Issues:

Unity 2 overwrites Unity 1.6.1 by default. This is just annoying.

Clicking the red X when an error occurs sometimes doesn’t work. Eventually it starts working and seems to work consistently.

I’m not getting anything out of Input(“Mouse ScrollWheel”). It used to work fine in 1.6.1. It works when I map keys to it (making it a key/mouse thing, vs. a mouse thing exclusively).

When I load some of the example projects I get odd error message too, so it’s not just my code.

I haven’t encountered a LOT more problems because, frankly, getting this far is like banging my head against a wall. Instead of getting to play with new features it seems like every single little thing is broken in some subtle way. (Next I need to figure out why my bullets explode on being fired, when they used to work.)

Again, this is all somewhat stupid. It’s bad to change versions of dev tools mid-project, and the sensible thing to do would be to switch back to 1.6.1, which I can’t do because Unity 2.0 overwrote it and reinstalling 1.6.1 doesn’t work (see my other thread).

I would having nothing against this version of Unity being called Unity 2.0 Public Beta and paying for a license if it didn’t install over Unity 1.6.1 by default.

BTW: I think that to restore 1.6.1 I need to copy a working installation across from another machine. This is pretty dire.

It also makes me wonder if when I upgrade to Unity 2.0 Pro I can have a Unity 1.6 Pro license to work with, because I have serious doubts that porting to Unity 2.0 will be viable.

13

Thanks for the bug numbers above, I’m soon off to read those and do that poking here…

Part A: Why aren’t you installing 1.6.2? Can you verify that it’s really 1.6.1 you’re installing?

Part B: It’s entirely possible to have both 1.x and 2.0 on the same machine*, many people have done it including myself sitting here today with absolutely no issues. I’m definitely puzzled as to why your experience has been so bad…

*Point taken on the issue with the 2.0 installer over-writing your 1.x install.

14

We also imported all of our projects from 1.6 into 2.0 (various alphas), and all needed tweaks (some more than others) but nothing broke in any of our projects.

With so much under the hood thats changed in 2.0, having to tweak and even re-make certain things after moving a project from 1.6 to 2.0 is a gimme.

15

Good point re 1.6.1 (and yes, it’s 1.6.1) – it’s the installer I happened to have lying around – I guess my laptop wasn’t quite up-to-date. (I’m in a hotel with a slow connection, which is making this more frustrating.)

So it’s possible it’s a 1.6.1 thing, although the Unity 2 installer’s behavior is still terrible.

Is there a URL to download 1.6.2 still?

I’m seeing tons of breakage. Some of it explicit (as in the environment refuses to accept certain commands any more…). That’s fine. It’s the way content is being hosed in non-obvious ways that’s more troubling, because it means I might not spot everything.

It looks like I might have to go through every scene in my project and manually rescale every object. A few minor tweaks?

I really don’t see this as any kind of excuse.

I might observe that I was a Macromedia Director developer from 3.0 through to 9 (was that MX? I forget … I never bought the last release). In general, Director didn’t screw up any content when you upgraded, although it was often open season on your code.

Similarly, I’ve been a RealBasic developer since pre 1.0, and again haven’t had this level of difficulty working with old projects. (RealBasic is usually forwards AND backwards compatible, within reason.) Pretty much the only issue you tend to have with old code is namespace-based (oops, there’s now an internal object or function with the same name as one of yours).

Oh (and sorry, I’m venting again) I don’t see Unity 2 as being as radically different under the hood from Unity 1.x as Director 8.5 was than Director 8, or RealBasic 2006 than RealBasic. Again, far fewer issues.

16

I’m sure everyone here feels your frustration, podperson.

It’s worth keeping in mind as you vent, that noone else seems to be having these issues. Your original theory was that it was because the project conversion wasn’t tested much by the beta testers, but it seems that’s not the case. I’m sure the gang will be glad to eat crow if a whole bunch of people report similar problems, but so far it hasn’t happened.

In general, neither does Unity apparently, though it’s maybe too early to say for sure. Just try not to overgeneralize In your frustration.

It’s bad enough that one person (you) are having so many problems with the conversion. I suggest sending your original project in with a bug report explaining a few obvious things that the conversion breaks, so that OTEE can try to repro. If they can’t, then worse comes to worse they send you back the converted project. :slight_smile:

{quote]
When I load some of the example projects I get odd error message too, so it’s not just my code.
[/quote]
What’s the error? This symptom alone seems pretty odd.

Wish I could help more :frowning:

Good luck…

17

Yay Google.

I found this: http://unity3d.com/unity/unity.dmg (1.6.2)

18

50166--1841--$picture_3_235.png

19

Unity 1.6.2 installed and launches. So it may have been the old 10.4.9 bug biting me. That’s a relief.

I also tried to set up some very simple test cases to replicate the problems I’ve been having with simple documents … so far no good. Unity 2.0f6 seems to handle them all properly. So the problem is non-trivial :-/ or it’s some kind of data corruption in my project.

20

As has been mentioned before a lot of people converted projects during the alpha process and it worked just fine.

Now your project doesn’t and thats not good, so we need to fix that.

If you submit a project folder or if you have submitted it already, then please just send me the case number and i’ll prioritize the issue. Please make sure that in the bug report there are specific steps on what is wrong after the conversion. The project folder you send in should be one, which hasn’t been opened in Unity 2.0 yet.