Issue I. Script Synchronization between Unity3d & MonoDevelop
When following Ben’s lectures, which demonstrate using Unity3d on the Apple I noticed some disparities between the results on the Apple and their corresponding results with a PC when syncing up scripts between MonoDevelop and an associated game object.
I first noticed these disparities when creating new text-buttons with which we were to associate game objects with publicly declared variables.
However, even when doing everything correctly, when the script declaring those variables is attached to the game object, most often the publicly declared variables will not show up as an additional property to the game object when they should. This however, was not the case with the Apple based version of Unity3d.
This type of disparity can only be rectified by ensuring that newly updated scripts are completely in sync with the Unity3d interface. Thus, the scripts must be first be removed from their associations with their game objects (where this issue is appearing), then recompiled, and re-associated with the game object.
Or one can go to the Assets panel at the bottom of the Unity3d interface in the PC version. Here there is an option to sync the MonoDevelop resources (scripts) to the Unity3d project, which appears to work just as well.
However, in either case you should always ensure that your scripts solution is always recompiled cleanly before correcting the issue just described.
II. Importing an image and not seeing the sprite properties discussed in the corresponding lecture.
When importing an image to be used within a scene you may notice that your import’s results do not reflect the same properties in the Inspector being shown in the lectures. Again, it appears that the Apple systems will do more analysis for you than that of a PC.
In this case, your image should be defined as a sprite in your Inspector panel. if it is not, simply go to the Texture-Type drop-down listing and select the Sprite item. Once selected, you should now see all of the relevant properties that correspond to the lecture.
These issues may not appear in the Unity3d 5.x versions…