Instanced albedo and emissives for precomputed lighting
Additive scene lighting warnings
Shader Graph (Preview)
High Definition Render Pipeline (HDRP) support
Vertex position
Master node settings
Property reference names and exposed state
Editable paths for graphs
Is Front Face node
Gradient nodes
Texture3D and Texture2D Array
Texture 2D LOD node
Show Generated Code
Vulkan support for Editor on Windows and Linux (experimental) Texture Mipmap Streaming C# Animation Jobs Particle System improvements
2D
Pixel Perfect Camera (Preview package)
2D Sprite Renderer Sort by Pivot Point
2D Hexagonal Tilemaps
SVG Importer (Preview package)
New 2D APIs
Editor - General
Support for using .java and .cpp source files as plugins in a Unity project
Standard Assets depreciation
Unity Hub
Cinematics
Camera Physical Properties
Recorder 1.0
Core Engine
Removal of the old RakNet-based networking feature
Addressable Asset System (Preview)
High-DPI monitor support
C# Job System, Entity Component System and Burst Compiler
Entity Component System (ECS)
Burst Compiler
IL2CPP-Managed Debugger Scripting runtime improvements in Unity 2018.2 ARM64-bit support for Android APK splitting by architecture Google Play Instant Games Plugin C# Platform Certificate Store Synchronization End of support for UnityScript Visual Studio Code Debugger Extension
XR
HoloLens Holographic Remoting
Remember to back up your projects before downloading the latest version of Unity. If you encounter any issues, please let us know by submitting a bug report so it can reach our developers. Future patch releases for fixes will be found here.
Thanks again to all the users who helped with testing and giving us feedback on 2018.2 while it was in beta! Notice that weāve locked the 2018.2 beta forum, so please create your new threads in the appropriate sections of the Forum.
Hello!
I ran into a problem. Unity 2018.2, working with a laptop, has stopped correctly scaling the editorās interface, now I have all the items increased, because of this it is not convenient to work. In previous versions, everything was fine. Is it possible to somehow adapt the interface manually?
ā¦/Unity/cache/packages/packages.unity.com/com.unity.postprocessing@2.0.7-preview/PostProcessing/Runtime/PostProcessLayer.cs(9,39): error CS1070: The type `UnityEngine.XR.XRSettingsā has been forwarded to an assembly that is not referenced. Enable the built in package āVRā in the Package Manager window to fix this error.
First: I dont install postprocessin into project so it is bug by itself
Second: PostProcess must not have dependency over vr module so it is bug too
Third: It must be not possible to disable package that other packages depend upon
Fourth: Unity 2018.2 bug reporter dont opens so I can not report this bug in correct way.
Hereās to another Unity Release! Thank you guys for all your hard work at making this one of the best engines out there. Thereās still some bugs and problems to fix, but I canāt wait for the newer versions of Unity to come and some of the new features, such as ECS, Nested Prefabs, Burst, and many more!
Seems like it adds the TMPro package when upgrading a project.
But this creates issues when a project already has the paid version of TMPro, which is incompatible with the package IIRC (otherwise I would have switched to the package long ago, since the paid version is a constant headache when it comes to moving to newer version of Unity). Having both versions creates compile errors as one would expect.
Which shouldnāt be a big deal. One might think that you could just open up the package manager and remove the TMPro package. One would be wrong. Initial compile errors seemingly need to be resolved before the package manager becomes visible. Since packages can cause compile errors, this seems like a generally unwise implementation.
Tried manually editing packages/manifest.json to remove TMPro package, but that didnāt work either. Iāll try removing the paid version, then the package, then placing the paid version againā¦ and hopefully that should workā¦ but in general the package manager should always be available to avoid scenarios like this.
In the beta version of this release I was able to use the Package Manager to remove the new version of TMPro so as to not conflict with my old one, and I believe that Package Manager was available under the Windows menu. I am not seeing it there now. Unity: Has the Package Manager been removed, or is it located somewhere different?
In the meantime @hurleybird Iāll try editing manifest.json, and thanks for the suggestion.
Forgot to look into it, wasnāt expecting it, but after updating I happened to hit the spacebar to start a Timeline playing, and what do I hear? Audio track preview!
My experience is that preview 12 of the IncrementalCompiler package just doesnāt work on 2018.2.0, so Iām guessing thatās your issue. Because of the āCanāt open package manager before compile errors are resolvedā oversight, youāll need to edit package/manifest.json manually. Either to point to a different version of the IncrementalCompiler, or just remove the reference to it and load a different version via the Package Manager if you want. Preview 11 seems to work fine for me.
Maybe youāve resolve this already, but Iāve found with a couple of projects after upgrading to 2018.2 that the Package Manager was missing from the Windows menu if there was a compiler error (in my case specifically code that depended on the legacy particle system) but when I exited and restarted the Editor with the same project, the Package Manager option was back.
I think thatās the case with compile errors that arenāt related to a package, while compile errors related to packages block the Package Manager entirely and need to be resolved outside of Unity.
Very stable and bugless so far but one major editor regression: now windows must be clicked for maximize shortcut toggle to work, which means no maximize shortcut in the game view while playing. I logged a bug for that one 1061824
Also environment lighting snaps back to skybox when press play. (1061833) this one might be an HD SRP bug
Just ran into an issue in 2018.2ās Timeline with cross-fading audio clips, or doing any kind of ease-in / ease-out on audio clips. Found that if there is an object assigned in the trackās field, crossfade and ease-in and ease-out donāt work. But in a track with no audio source assigned, the crossfade and ease-in and -out do work.
A little distressing because we ran into a crossfade issue before, and the fix at the time was to update to Unity 2018.1.3f1. Perhaps this was fixed before and broke again?
Submitted a bug, fingers crossed.
UPDATE: Turns out it is indeed a bug and Unity is working on it.
I think you guys should not announce this things if they are still in preview mode or in an unstable state, I mean the feature is far from stable and put it in a release make you think that itās ready for use, which is not the case, I think you should manage the communication in a very different way, half finished features should not be part of a release announcement.
Thank you guys for all your hard work at making this one of the best engines out there. Thereās still some bugs and problems to fix, but I canāt wait for the newer versions of Unity to come and some of the new features, such as ECS, Nested Prefabs, Burst, and many more!