Unity 5 Beta Insights

On the subject of the == null and != null operators I had a thought. If these were removed perhaps it would make sense to adopt a custom interface like the following:

Code (csharp):

1.  
2. public interface IDestroyable
3.     bool HasDestroyed { get; }
4.     void Destroy();
5. }
6.  

Where Object implements this.

This would be beneficial in situations where interfaces are being used on custom behaviours or scripable objects:

Code (csharp):

1.  
2. public interface ISpaceship : IDestroyable {
3.     void FireLaser();
4. }
5.  
6. public class Spaceship : MonoBehaviour, ISpaceship {
7.     public void FireLaser() {
8.         Debug.Log("Swoosh");
9.     }
10. }
11.  
12. public void HandleFireInput(ISpaceship ship) {
13.     if (ship == null || ship.IsDestroyed)
14.         throw new Exception("Ship was null or destroyed.");
15.  
16.     ship.FireLaser();
17. }
18.  

Just a thought...

 

Since when has Unity been .net though? It's not as if unity's js or Boo is really the same stuff. C# comes from .net, but c# is a language and .net is something optional entirely. Unity uses Mono (and god knows what else coming).

 

Well if everything else is using it I might as well as well for consistency's sake.

 

i not want to read 8 pages of posts, so if have understanded all in unity 5 instead of writing:

Code (CSharp):

1. this.renderer.collider.attachedRigidbody.angularDrag = 0.2f;

we have to write:

Code (CSharp):

1. GetComponent<Renderer>().GetComponent<Collider>().GetComponent<Rigidbody>().angularDrag = 0.2f;

or wather else? Tell me!

 

Yes.

Not sure whats the logic in your example as isn't the rigidbody in the same object anyways(?) so:

Code (CSharp):

1. GetComponent<Rigidbody>().angularDrag = 0.2f;

But if you access something frequently you should/could cache it anyways instead of calling multiple GetComponent everywhere.

 

Nesting GetComponent<> is silly. Just ask for the one you want up front.

Code (CSharp):

1. GetComponent<Rigidbody>().angularDrag = 0.2f;

Gigi

 

if i have a game object attached to an script and i want to modify the first object rigidbody i have to use:

Code (CSharp):

1.  firstobject.GetComponent<Rigidbody>().mass = 100;

or I'm wrong?

 

You are right.

 

ok thanks all!

 

In case you missed it, Unity themselves have now posted about the changes coming in Unity 5 http://bit.ly/1pf5Wog

 

I did say in the post it was a silly long winded example Just to make a point.

 

Modularisation sounds great. I remember an app going over the iOS 20MB OTA download limit (when it was 20, not 100) because an update to Unity added Terrain to iOS. That caused another round of optimisation that would have been avoided with this system. It is very welcome with all the new features coming in Unity 5.

I did have a double take at the wording below. It took a second to realise Lucas was talking about bytes, not finance. Modularisation of buying Unity would be brilliant, but modularisation of builds is also. This has the potential to be my favourite Unity 5 feature.

EDIT: I just did my first build on an iOS project since updating to 4.5 from 4.3. The app estimated size has grown by 1.3 MB to 29.4. I'm really looking forward to modularisation.

 

I hope that, by modularization, it means the .rigidbody shortcut is kept, I don't want to have to GetComponent and make my code really messy!

EDIT: I also wish to continue to make wonders with only two lines of code, so removing shortcuts like .rigidbody would increase the line count somewhat, depending on what you're trying to write. basically, don't alienate us please!

 

AFAIK to achieve proper modularization all those silly shortcuts need to go. Even if code might seem to become larger in lines or generally it also becomes more standard and efficient as people will cache the needed references more than before.

 

the only thing you would have to add is

Code (CSharp):

1. public Rigidbody rigidbody;
2.  
3. void Start() {
4.      rigidbody = GetComponent<Rigidbody>();
5. }

and all your .rigidbody calls work like before. Not messy at all

 

In my opinion x.0 releases should and can contain major changes. If you are not going to make wanted/needed compatibility changes on this type of release we will always be stuck with these stupid decade old issues. X.0 release is when you shouldn't worry about breaking old projects and fix what needs to be fixed. We can update our projects to comply with the changes.

 

Couldn't disagree more. This is why you extend the base class with your GameBehaviour which extends monobehaviour. You can then replicate the unity functionality 1:1 pretty much and everyone is happier. You only need to do that extra typing once, then all your stuff is as it was before - perhaps better.

For instance I have a SCache class which does all the typical caching of components that I need on a regular basis for a sprite with physics.

Typing one line more is never a reason not to do something, come on, that's just bizarre

 

Ok, I will stop... I just found the .rigidbody shortcut more convenient...

 

Yes, that is agreed. I also wouldn't mind a faster runtime library... but with Xamarin being so difficult with Unity, from what I heard, mono is probably going to stay the way it is. Also sorry that it's off-topic, but...

 

It's not anything to do with Mono. As for "stay the way it is," no.

--Eric

 

Any idea when the preorder people get accesso the beta? I preordered a long time ago and would really like to show a client something i ahve done before except in web gl.

 

Just found another interesting article by accident: http://staraban.com/en/unity-5-beta-overview-migration-to-new-unity-version/

 

Yes I want Beta! HaHa so looking forward to it, preordered and all that. Going to Unite Melbourne next week, see (some) of y'all there. Cheers

 

Beta 1 is the version that leaked?... well that's unfortunate...

 

"several days ago" in august...

All other versions up to b9 were leaked too, obviously.

 

Public beta is out: http://unity3d.com/unity/beta/5.0/

 

oh F*** yes. Pardon my language lol

 

And a sense of humor

 

Hi! You can now start/continue discussions in our dedicated forum for the 5.0 beta
http://forum.unity3d.com/forums/unity-5-pre-order-beta.72/

 

It's not a public beta, it's for pre-order customers and Unity Pro subscribers.

 

its not public but can we have some feedback from users on low end platforms like mobile for example ?
Can we expect to run new lighting or new standard shader with decent perfs?

 

I expect feedback from users will show up in the 5.0 beta forum: http://forum.unity3d.com/forums/unity-5-pre-order-beta.72/

You can always go ahead and post questions there already to find out information before you start using 5.0

 

The "public" part was more referring to the link itself instead of who can actually activate it as they were talking about leaked files above

 

I love the removal of the .component accessors, I used to override those non-cached innocent looking little devils with the new keyword which checks if the cache is null and the returns the component (if available)).

Code (CSharp):

1.  
2.  
3. public Rigidbody _rigidbody = null;
4. public new Rigidbody rigidbody { get { if(_rigidbody == null) _rigidbody = base.rigidbody; return _rigidbody;}}
5.  
6.  

No more of that thank you very much

The awake, start, custom setup / init way of setting your own reference also works nicely, but sometimes you just want to protect your self from accidental code completion idiocy.