I noticed something weird today with JellySprites Have been working on a project for some months now where we ended up using JellySprites for our main character We have been working in Unity Free all the time But a week or so ago I started the Pro trail just to check it out Today we moved the project from Github to Bitbucket and after I cloned it down from Bitbucket and opened the project in Unity Pro, JellySprites behaved quite significantly different. First I thought that there were some weird bugs in my old file, I started doing the changes needed to get the size of it and behaviour close to what it was before. When the rest of the group noticed, they didn't feel comfortable (we have a presentation of it tomorrow) about the big change and told me to change it back. First I just told them I couldn't 'cause I had no idea how it happened, but after they kept on nagging for a while I got one theory, it could have something to do with Unity Pro So I cloned the project again into a new location, ended my Unity Pro trail and then opened the project, and tadda! back to what we were used to So the one thing worth noticing here is that what ever the different is, it is something that is generated when opening the project when missing certain files that is not uploaded with Git Have you any idea what the difference here is? I took a backup of the folder with the project were the Unity Pro JellySprite is so that we can look into it later, for now I have rolled back to what we had before .gitignore file: http://pastebin.com/6pu2B67A Edit: Something more came up that might be relevant We all started the project while using the Unity 4.6 beta (wanted the GUI stuff) Though one person in the group didn't get that note and just downloaded 4.5 I just remembered that when she opend the project, the JellySprite was much bigger then on ours. I just told her to download 4.6 not thinking that 4.6 could be the problem and not 4.5 If it is a bug with Unity 4.6 it isn't in the Pro version, but is still in the Free version as I could fix the 'problem' be just re-cloning and the open in the Free version Isn't that a bit odd?