Unity Future .NET Development Status

Can we use MS' own JSON in Unity 2021.2 Beta?

 

We can, if these dependencies work in 2021.2

Microsoft.Bcl.AsyncInterfaces
System.Buffers
System.Memory
System.Numerics.Vectors
System.Runtime.CompilerServices.Unsafe
System.Text.Encodings.Web
System.Threading.Tasks.Extensions

 

I guess not then

 

I said so because I didn't have time to test it myself, sorry if my words confused you.

 

System.Runtime.CompilerServices.Unsafe is not included in my case. Unable to use messagepack unless i download the dependency binary and put it in the plugins folder

 

Hello! Sorry if it's been discussed already, but I see that .net 6 has new infrastructure for more advanced hot reload. JetBrains Rider has rolled out support in its EAP and Visual Studio will have it as well. Will it ever be possible to take advantage of this in Unity? Being able to make a code change in some function and seeing changes in-game in less than a second without recompiling or domain reload would be an actual gamebreaker, iteration speed alone would raise by several orders of magnitude. Game development is so much about guesswork, a lot of the time you don't know how the code is gonna feel until you try it.

 

Hot reload also doesn't break whole project during gameplay. It seems to me that it's very different usecase than domain reload. Both should be supported just like in Unreal (recompile and live coding).

 

Is there not a way to auto convert existing code project to the new code? like unity does with the script updater

 

I understand that I know nothing about hosting mono or .net Core in native app but.

Why full kill and deallocate all managed host memory and create new one from scratch (instead of domain reload) is not an option?

 

Hi, @JoshPeterson
is there any chanse to get C#10 in 2021.3?
It will be released on 9th of November that just 2 weeks after Unity 2021.2 release.
Most of features in this release are just syntax sugar and some of them could be quite useful.
And according to my tests most of them works in Unity 20212

 

unlikely

 

but still, everything is possible

 

Does 2021.2.0 support source generators? I could not find it in the release notes.

 

It does.

 

A more abt answer would be: it does... but you gotta set it up yourself with external libraries and messing about in your configuration. Go to page 6 to read more about it, and let me know if you understand what they're talking about XP

 

Note: @neucc (of UniRx fame) has an implementation of MessagePack for Unity ready to go.

 

As far as i can tell the default interface isnt working.
on the one hand i dont get error in the interface itself, but when a class implements the interface it thinks the default implementation doesn't exist

 

sure, on it

 

i have never submited a bug report before... how do i do it? cant seem to find where to submit

 

Have you ever heard of Google? Try: "how to submit bug report unity".

 

I have heard of Google, thank you. I hope your day is as pleasant as you are.

 

it's not a bug.
it's how Default Interface Methods works.

classes do not inherit default implementation.
DIM available only when you work with object of interface type

So in your code you need to change OnClick to something like this

Code (CSharp):

1. public void OnClick()
2. {
3.     ((ISingleClickable)this). OnBla() ;
4. }

or just do not abuse DIM for thinks like this

 

oh thx that worked
why do would call this abuse though, isnt this the point of DIM?

 

DIMs are intended to allow interfaces to be extended later without breaking existing implementations of them.

 

Point of interface in general is you can use interface as type of argument and variable instead of specific class or struct, especially with generic. That is the topmost functionality of interface

DIM is just a feature that try to make that functionality more useful, what I see you really want to do is extension method

 

In your case, an abstract class would actually make more sense, and you would have behaved as you would expect. The reason why DII works so is because you can implement several interfaces, and as potentially the same method could have a default implementation several times, so you have to specify which interface you are using. And if the class doesn't implement the interface, naturally you have an error. In the .NET world, interface-only development is often used, which means that many APIs only work with the interfaces and never with the implementation themselves, so the problem does not exist.

 

i honestly just wanted to try to use this functionality to have multiple inherence which i understand is kind of hacking the purpose of this feature. With multiple inheritance i can create a composition of functionality and avoid some of the issues the single inheritance causes.

 

Just wanted to chime in and say I am stoked to see such transparency !
This thread made my day.

I hope Unity can incorporate this into all its development.

 

If DOTS had this transparency it would be amazing, as it doesn't, it seems like everything is dead and lost.

 

PHP also only has single inheritance, but has a solution with traits, whose content is simply copied into the target class during parsing. (However, if used incorrectly, this can quickly lead to problems).

Default interface implementation as a replacement for traits is a bit safer, but if you use it you have to know how default implementation works, especially when properties come into play. For example, if you have two interfaces that have the same property, they are two different implementations, a class that uses these two interfaces and also implements the property, then there is the property 3 times. The default implementation would only ever use their own default implementation.

 

@JoshPeterson @xoofx https://github.com/dotnet/runtime/issues/61231 this just came to the .NET 7 roadmap. I know that it's very early, and .NET 6 is nowhere near being finished with Unity, but theoretically could NativeAOT come to Unity as a replacement for IL2CPP?

 

Worth saying that NativeAOT can be used in Unity by simply compiling library for a platform. Very useful for stuff not supported in IL2CPP like System.Process.

 

That's really a good thing. I wish microsoft would just making C# project that will automatically integrate unity as a library soon

 

https://github.com/Unity-Technologies/runtime

 

@JoshPeterson does this mean that work has started to move to .NET 6?

 

CoreCLR as a JIT meaning RyuJIT? Meaning we get recompiling hot methods, inlining virtual calls, etc? That might be the single greatest improvement to performance that Unity could make right now.

Every user script, all the "glue" setup for ECS/Burst that's done in managed, dependency injection/interface-first OOP, every editor extension on the asset store, UI Toolkit and UGUI, tweens, coroutines, and all the "death by a thousand cuts" when you have tons of miscellaneous scripts running in your game...

If this is really happening I'm flabbergasted.

 

Does this also mean C# 9 or possibly 10 support?