Official The road to 2021 - Q&A

With regards to SerializeReference, we are working on stabilization actively and fixes will be backported where it can back to 2019.4. With regards of handling missing types in SerializeReference we wish to offer a more granular handling of those with the possibility of handling a missing type by specifying a new which could handle the type payload, this will be looked at in the 2021 timeframe.

 

We plan to release a public generic spline API as part of our 2021 release (exact timing tbd). This will enable you to create and edit different types of 3D splines in the Unity Editor. The first feature to use that new API will be Cinemachine for setting up camera paths. Other features will use this generic API and follow soon after.

https://blogs.unity3d.com/2020/08/13/the-road-to-2021/#comment-427477

 

Short answer: the best place to submit feedback is via the forum by creating a new thread in the relevant sub-forum and selecting the Feedback prefix.

Have a look at this page for a longer explanation: https://support.unity3d.com/hc/en-us/articles/205692319-How-do-I-submit-feedback-about-Unity-

 

Hey @TheOtherMonarch, UIDM support is in consideration but we don't have a timeline for it yet.

 

Hi @Bastienre4, yes you will be able to create custom nodes with visual scripting. We need to improve our documentation for this but this is something we are working on at the moment.

Regarding the graph API, this is something that will become easier and easier to do over time as we progressively unify our graph-based tools on a common framework.

Laurent

 

Hi @rsodre, yes our public roadmap pages need to be revisited for clarity and consistency. This is on our radar to be addressed. Thanks for pointing it out.

 

@rsodre Thank you for the feedback. re: Better Package tags.

In general, these decisions taking from 2020.1 release and onward were not just about tags/labels but moreso about quality for all of our users of given Unity release. Likewise, it was to help clearly communicate the state of release and receive feedback through the right channels.

You may have already seen similar replies on that original forum post. We are rolling out new tags for 2021 specifically 'pre-release' and "release candidate (RC)" which will replace "preview" to give more clarify on the state of the package's developement. Note: we didn't want to use 'beta' as label to avoid any direct association to the Editor release cycle since a pre-release package can still be available in a non alpha/beta release of Unity.

The Verified label will go away and any package name+version we host on the Unity registry and show as visible by default in a given Unity Editor release will be treated as fully supported.

For Experimental packages (anything not visible by default or enabled with the 'show preview/pre-release' project settings), we do want to keep those non-visible by default. It's not because we want to make it more difficult for users like yourself who want to discover, test and provide feedback on our bleeding edge solution but to help better set expectations and establish the right communication channels where to discover those packages and provide feedback directly to the Unity dev teams. These experimental packages are rapidly evolving and often have breaking changes between version upgrades so it was the safest path for all other users who want a consistent experience for a Unity release.

I hope this helps.

Thanks
Daniel

 

For many Unity users, our communication around DOTS and progress and direction of the Unity architecture has been confusing. We want to help set clear expectations, and this post is intended to help developers understand what that can expect to be using for their projects in production in these upcoming releases. DOTS development continues and is a core component of where we are going, but we also want to make sure you can be successful right now and know what you can rely on for projects in production today.

 

We've built a generic spline API that is not dependent on the environment system. We plan to release the public API in core - not as a package - later in 2021 release (exact timing tbd). This will enable you to create and edit different types of 3D splines in the Unity Editor. The first feature to use that new API will be Cinemachine for setting up camera paths. Other features, like the environment system, will use this generic API and follow soon after.

 

Thanks for the follow-up. I might not be able to unpack everything you're addressing, but let me try.
First, I think that we might be mixing connections / players per session / and connections per session. I'll try my best to be specific below =)

• You say that average target is 300 connection per session. it is absolutely OK for one session but how many sessions can be held on battle server side.
  
  
  • Multitenancy is a different goal from scaling players per session, is likely a future target for our DOTS stack which is great for running multiple worlds simultaneously
    
• We already have around 1K-2K connections (16 connection per session) on old buggy UNET and our bottleneck is network. We event dont yet apply DOTS Jobs and Burst for server so it can handle may be 5-10K players but what about network?
  
  
  • do you mean bandwidth? Not sure I understand the question
    
• Libraries on AssetStore like dotsnet claim support of thousands of connections and looks good for server workload.
  
  
  • well, it's what I mentioned at the beginning, there is a taxonomy challenge . connections vs users vs sessions. We'll check that one though, we're always validating solutions and looking forward to learning more!
    
• New UnityTransport claim support of only 300. May be this is 300 per session? What then total number for one server with hundreds of sessions?
  
  
  • Connections per server vs different from players per session. We’re targeting our solutions in many cases for players per session.

Hope this adds some light!

DavidS

 

Hello everyone!

Thanks for all the great questions - keep them coming! We will continue fielding and approving them over the weekend so our experts can get to them next week.

The thread will stay open until Saturday, August 15th at 10AM PST.

 

We are currently looking into ways that can enable faster iteration while in play mode that can potentially substitute the need for saving during play mode.

 

We’re actively working on defining the solution for our customers for real-time GI, fully understanding how impactful dynamic global illumination is to modern games and many of our customers’ use cases. While we are not on track to provide a replacement in time for 21.1, we are still aiming to share the plans by the end of 2020.

https://www.reddit.com/r/Unity3D/comments/i9meq1/unity_rd_team_2021_roadmap_ama/g1gujxc/

 

Mike Acton here. It's clear the roadmap and expectations for DOTS have been confusing quite a few of our users. We intend to clarify the road to DOTS in a future blog post for everyone.

https://www.reddit.com/r/Unity3D/comments/i9meq1/unity_rd_team_2021_roadmap_ama/g1gn87p/

 

Mike Acton here. You can be confident that you can continue to use monobehaviour and we will continue to support that. There are no plans to completely remove the monobehaviour workflow. That said, if we were to ever consider such a thing in the future, it would be with the understanding that its replacement would need to be something you could love even more.

https://www.reddit.com/r/Unity3D/comments/i9meq1/unity_rd_team_2021_roadmap_ama/g1ghn8i/

 

Hi and thank you so much for your feedback.

This area is still under development. There is currently a lot of design research and exploration being done, while also experimenting with some internal prototypes. Even though we’re making remarkable progress, it’s still too early to share any plans or roadmap.

Cheers

 

Thanks for your feedback.
1- This issues have been greatly improved in latest versions. I tested again with 2019.4 and I didn't even see the "looking for SDK/NDK" message. Be sure to check https://docs.unity3d.com/Manual/android-sdksetup.html
If your issues persist please share on the forum a recording of the build sequence (like an animated gif) and info about your JDK/SDK/NDK configuration (in Preference>External Tools).
2- We'll be looking into this, it sounds like something that could be optimized.
3- This is a good idea. You're correct that automating this via an adb command is a good way to achieve the "deploy last build" task, but we will consider adding this for future update of the Android Logcat utility for the Editor: https://docs.unity3d.com/Packages/com.unity.mobile.android-logcat@1.1/manual/index.html

 

Thanks for the feedback Kreoth. We know about these pains and have plans to make the life of animators easier when working with the animation window. Unfortunately, with our current priorities, we can't say for sure when we will be able to ship these fixes.
Cheers.

 

We will support billboard rendering in URP. Reading the internal notes it looks like it did get fixed and originally resolved as fixed with a pull request, and then closed as due to the tree creator part as will not fix. I'll double check and get the bug notes updated, as I think this is a case of "we fixed the a thing but not every aspect of the thing". If that's not then case then I'll make sure it's reopened and that fixing billboard support is in our prioritized list of bugs.

 

From the Addressables team:

The workflows for Addressables are fairly well locked. We will continue to improve them incrementally as we can, or as bugs force us to, but no drastic changes are on the roadmap for the near future. At some point next year we may have a redesigned system, but if so, we would continue to support the current workflows for a long time.

 

These initiatives are for now two individual teams working towards solving similar but very different outcomes. As DOTS matures we will do our best to align the two teams and focus on bringing a shared common foundation for NetCode in Unity for both DOTS and GameObjects.

 

Hi Jes28, thanks for your patience on this one
I've shared your scenario with several members on the team and our recommendation would be to check if either Enet or Darkrift 2 helps you solve the challenge today. As you know, the new unity networking is in preview, and we've not shared a date when it will be available.
We'd love to hop on a call and learn more about your scenario, if you're open to it, send me your email over the conversation we already have and we can work on the schedule.

Cheers!

DavidS

 

We still have a lot of work ahead of us but we have a dedicated team that is making good progress. We are working on a complete animation solution including animation graphs and state machines and we will happily share more information when closer to public release.

Thanks for asking Sylmerria, cheers!

 

Hey there! We have identified the need for custom culling and SRP culling filtering and we are currently discussing prioritisation for the functionality as we focusing towards the next year. We don't have specific timelines yet, but will update on that as they get firmed up. Regarding the first question, if I understand correctly you are referring to Dynamic Resolution (let me know if I understood it incorrectly). If yes, we support it in HDRP and we're following up with the URP team to prioritize the feature in that pipeline. Having said that currently URP exposes a render scale in the pipeline asset. Overlay UI and post-processing is always rendered at Native Res.

 

Thank you for your question. This is in consideration and definitely on our radar but we don't have a timeline as of yet. We will update everyone when we have a concrete plan.

 

Thank you for your question. Point light shadows is a new feature for URP. Unfortunately we won't be back-porting point light shadows. This is to make sure we do not affect the stability of the older versions of Unity.