-
Notifications
You must be signed in to change notification settings - Fork 461
build!: upgrade baseline Unity version from 2019.4 LTS to 2020.3 LTS #644
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -19,7 +19,7 @@ This is the initial experimental Unity MLAPI Package, v0.1.0. | |
|
|
||
| - Added message batching to handle consecutive RPC requests sent to the same client. `RpcBatcher` sends batches based on requests from the `RpcQueueProcessing`, by batch size threshold or immediately. | ||
| - [GitHub 494](https://github.com/Unity-Technologies/com.unity.multiplayer.mlapi/pull/494): Added a constraint to allow one `NetworkObject` per `GameObject`, set through the `DisallowMultipleComponent` attribute. | ||
| - Integrated MLAPI with the Unity Profiler for versions 2020.2 and later: | ||
| - Integrated MLAPI with the Unity Profiler for versions 2020.3 and later: | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I believe it should've been 2020.3 LTS instead of 2020.2 already — what you guys think? @lkrell @JesseOlmer |
||
|
|
||
| - Added new profiler modules for MLAPI that report important network data. | ||
| - Attached the profiler to a remote player to view network data over the wire. | ||
|
|
@@ -85,7 +85,7 @@ With a new release of MLAPI in Unity, some features have been removed: | |
| * Removed "hail handshake", including `NetworkManager` implementation and `NetworkConstants` entries. | ||
| * Modified `RpcQueue` and `RpcBatcher` internals to remove encryption and authentication from reading and writing. | ||
|
|
||
| * Removed the previous MLAPI Profiler editor window from Unity versions 2020.2 and later. | ||
| * Removed the previous MLAPI Profiler editor window from Unity versions 2020.3 and later. | ||
| * Removed previous MLAPI Convenience and Performance RPC APIs with the new standard RPC API. See [RFC #1](https://github.com/Unity-Technologies/com.unity.multiplayer.rfcs/blob/master/text/0001-std-rpc-api.md) for details. | ||
| * [GitHub 520](https://github.com/Unity-Technologies/com.unity.multiplayer.mlapi/pull/520): Removed the MLAPI Installer. | ||
|
|
||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -12,8 +12,8 @@ | |
| using Unity.CompilationPipeline.Common.ILPostProcessing; | ||
| using UnityEngine; | ||
|
|
||
| #if !UNITY_2019_4_OR_NEWER | ||
| #error MLAPI requires Unity 2019.4 or newer | ||
| #if !UNITY_2020_3_OR_NEWER | ||
| #error MLAPI requires Unity 2020.3 or newer | ||
|
Comment on lines
-15
to
+16
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this would cause a hard compile error on build immediately if somebody were to put MLAPI into a project older than 2020.3 such as 2020.1, 2019.4 etc. should we keep this or should we rely on package manager, package.json and other things constraining people to get MLAPI on older versions? @mattwalsh-unity @JesseOlmer @seanstolberg-unity |
||
| #endif | ||
|
|
||
| namespace MLAPI.Editor.CodeGen | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -8,7 +8,7 @@ namespace UnityEditor | |
| { | ||
| public class MLAPIProfiler : EditorWindow | ||
| { | ||
| #if !UNITY_2020_2_OR_NEWER | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. At this point, should this just be removed as a whole? Since we were keeping the MLAPIProfiler for version under 2020.2 but 2019.4+. Or for now we keep it like this and remove it whole for 1.0?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. we aren't fully decided to make 2020.3 LTS baseline version requirement permanent yet. we might consider jumping back to 2019.4 LTS if we get some fixes around ILPP issues we're having — so it's still TBD, that's why I'm still keeping pre-2020.3 blocks around :) |
||
| #if !UNITY_2020_3_OR_NEWER | ||
| [MenuItem("Window/MLAPI Profiler")] | ||
| public static void ShowWindow() | ||
| { | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure whether or not to kick 2019.4 out from Yamato CI/CD since we have plans to potentially downgrade back to 2019.4 in the future