A Unity ID allows you to buy and/or subscribe to Unity products and services, shop in the Asset Store and participate
in the Unity community.
Separate names with a comma.
Discussion in 'Announcements' started by LeonhardP, Apr 15, 2019.
No previous versions had a way to modify the keys for things like the 3D Viewport fly mode.
I can't see it on 2019.1
Why is there a flash when you press play and stop play (see video ) ?
You can submit the report without attaching the project and ask the QA employee handling the case to provide you with an alternative storage solution where you can upload the project to. If the project is already in the cloud (eg. github), it's also a possibility to give QA access to the repository.
Could you please submit a bug report for that?
Thanks for pointing that out. I'll reach out to the team.
Re: the mobile VR crash, we recently discovered an issue in 2019.1.0b10+ where mobile VR may crash in certain situations. One specific case is with particle systems in the scene and MultiView enabled.
The current workarounds are to either use b9, or to switch to MultiPass. Neither workaround is ideal, but we have a fix in the works that we hope to get in for 2019.1.1.
It's not a bug; it's a design problem. It's well described in the link I added to my post.
Another tutorial had the same problem; you'll have to ask the team to look at all the tutorials.
I know that tutorials are supposed to be made using the versions of Unity they were made with but most of these versions cannot be used nowadays. This doesn't mean that the tutorials must be removed; I made the Stealth (Unity 4.6) entirely with both 2018.3 and 2019.2 beta without any problem.
2019.1.0f2: I created a new project and it appears that I have a package that seems to be empty installed by default. The package is called Unity UI, it has a manifest with a link to the package manager but it's not in the "in project" list, the "all packages" list or the "preview packages" list.
Hi, can you tell me what kind of new project you created? (2D, 3D, Lightweight?)
This was the single most horrible upgrade I've ever been through on any software I ever used
This was so bad that I've spent hours just trying to get this thing to load anything
I get that you want to move forward but the backwards compatibility is so bad that it's actually insane given that you don't offer any good alternatives.
(started with something like 700 errors, got rid of some via reimport: thought I clicked on upgrade?)
- Blender importing is broken
- UNet is obsolete and your new system is indev so I have to move to photon
- DLL link errors of unity's obsolete packages instead of removing them in the upgrade process?
- Argument Exceptions from the editor itself?? How does that provide me with any info on what part of the project triggered this exception?
There are workarounds and it will be fixed in 2019.1.1. https://forum.unity.com/threads/upg...import-broken-workaround.662623/#post-4439128
You can still use UNET in 2019.1 by using the "Multiplayer HLAPI" package.
Can you please provide more information? What packages are causing you problems during upgrade?
Same here, please provide more information.
It was a 3D project.
Can't seem to light bake properly in 2019.1 I keep getting this error - (Using progressive CPU)
Baked lightmap filtering failed during bake. Try disabling the Optix denoiser or lower the Lightmap Size.
Funny thing is even even I select filtering to none and change map size from 2048 to as low as 128 the error is still being thrown up, sometimes it even crashes. The project scene still bakes perfectly in 2018.
Also the prioritize view doesn't work either, its just seems to bake random things. Sometimes the bakes turn from 20 min to 2 hours.
I basically can't bake lighting at all in 2019.1. And it won't accept lighting assets from 2018.3 pasted in. I don't know what to do!
Actually was able to solve it simply by building with Ctrl+B to standalone player. I've no idea why building in the editor itself is problematic but I'll paste here some of the exceptions I get from the editor when they'll pop again.
Maybe something with clean vs. incremental build? or some packages that aren't supported on 2019.1 anymore that integrate with the editor? idk but I literally build to player and only then run it from the editor as a workaround rn.
EDIT: new problem of .blend models
opacity, orientation and whatnot. Moved to blender 2.8.
I don't need to workaround this, you need to patch this embarrasment
In the announcement, this video shows off how LWRP has been customized using renderer features:
Is this available as a sample project anywhere? It would be nice to see how this effect was created.
For me after an upgrade from 2018.3.12 to 2019.1.0f2 it seems UI loading is extremely laggy on iOS devices and in the Editor. No code was changed whatsoever. Hoping this is just some glitch in the layout dirty mechanism that might be fixed in 2019.1.1 ? Did anyone else notice the same?
Please submit a bug-report as described in this document:
It's important that you report these issues together with a reproduction project if you want them to get fixed. If you don't do it, it might be a long time until someone else reports them or until Unity Technologies find them.
After you submitted the bug-report, you receive a confirmation email with a bug-report Case number. Please post the Case number (number only, not the link) in this forum thread for Unity staff to pick up.
Hi, Issue 1137204 has just had its status set to "Fixed in Unity 2019.1". It's still an issue in the current official release 2019.1.0f2.
When is the patch version with that fix expected to be available? It's currently a blocker for us preventing a feature release.
The fix should become available in 2019.1.2 in roughly two weeks.
Thanks! Is there any way to get early access to 2019.1.2 (even if not fully validated), or is there a workaround or patch we can apply to current release? We have our own pending release waiting on this.
same problem here. my old projects with .blend 3D files worked perfectly in unity 2018 but they will be not imported in 2019. even the workaround with Unity-BlenderToFBX.py is not working. hope it will be fixed with the next update!
Unfortunately the build won't be available before release. As for a workaround:
In the Player settings->Resolution and Presentation, make sure the "Allow Fullscreen switch" option is enabled (checked). This should allow the Windows shortcut Alt+Enter to switch between fullscreen and windowed. I believe this setting is on by default.
So, after clicking the Maximize button, the display goes to full screen, press Alt+Enter on the keyboard and it should switch back to a Maximized window.
I know it's been a while, but could I ask you for something else ?
I dug a bit deeper to see what was wrong.
The 30fps lock bug occurs when :
- You run a build from 2019.1
- You run it on Win 10
- You run it in full screen mode
- You have a secondary monitor plugged in (all the tests I ran were with HDMI)
If you have a secondary monitor, would you mind to check if this happens to you too ?
That'd be super nice.
The list of new features looks very interesting!
Building the project takes longer than expected. Even if you have small scene.
How much longer does it take compared to 2018? Is it perhaps only slower on the first build and subsequent builds are faster?
Is there a way I can escalate this? We have a professional product that's being left in limbo as we can't push new releases without this fix - we released as Beta but the feedback is that this is a blocker for certain use-cases. We are aware of the keyboard workaround but I believe that doesn't work for Windows tablets. I meant a patch or code workaround if possible, or if not early access to 2019.1.2.
Linking this here: https://forum.unity.com/threads/image-stretch-change-in-2019-1.668632/
In lastest 2019.1 from today, UI Images are broken. It is impossible to make dynamicly generated UI. :'(
Submitted a bug report with repro project, case #1150937.
I'm the software engineer who's been working on the fix for this bug and was notified of your situation.
I've implemented a workaround to automatically revert the app out of Fullscreen mode. Unfortunately, you cannot put the window in a "maximized" state, since this will again trigger the Fullscreen mode switch, so instead this code will move/resize the window to fill the desktop area.
public class FullscreenCheck : MonoBehaviour
public bool AllowFullscreenMode; // Set this flag if we actually want Fullscreen mode
private IntPtr _hWnd; // Main window handle
private float _timeElapsed; // Accumulates amount of time since last check
private bool _repositionWindow; // Internally flags to reposition main window after switching out of fullscreen
// Start is called before the first frame update
AllowFullscreenMode = false;
_timeElapsed = 0;
_repositionWindow = false;
// This *should* return the handle for Standalone Player's main window
_hWnd = FindWindow("UnityWndClass", null);
// Update is called once per frame
if (AllowFullscreenMode || _hWnd == IntPtr.Zero) return;
_timeElapsed += Time.deltaTime;
// Poll FullScreenMode periodically and not every frame
if (_timeElapsed < 0.25) return;
_timeElapsed = 0;
// Switch back to 'Windowed' mode if we ever find ourselves in Fullscreen
// However the size of the window is generally too large and clipped by edge of the display
if (Screen.fullScreenMode != FullScreenMode.Windowed)
Screen.fullScreenMode = FullScreenMode.Windowed;
// Must wait 1 frame to mode change to settle before adjusting window position and size
_repositionWindow = true;
else if (_repositionWindow)
// Get the monitor the Unity game window is currently on
var monitor = MonitorFromWindow(_hWnd, MONITOR_DEFAULTTONEAREST);
var info = new MONITORINFO();
// Move/resize the window to fit within the WorkArea (usable desktop space) of the current monitor
if (monitor != IntPtr.Zero && GetMonitorInfo(monitor, ref info))
int width = info.WorkArea.Right - info.WorkArea.Left;
int height = info.WorkArea.Bottom - info.WorkArea.Top;
MoveWindow(_hWnd, info.WorkArea.Left, info.WorkArea.Top, width, height, false);
// NOTE: On Windows 10 there will still be a gap between the window and the edge of the screen.
// This is because the frame of a resizeable window (i.e. chrome) is invisible
_repositionWindow = false;
private static extern IntPtr FindWindow(string className, string windowName);
private static extern bool SetWindowPos(IntPtr hWnd, IntPtr hWndInsertAfter, int x, int y, int cx, int cy, uint uFlags);
private static extern bool MoveWindow(IntPtr hWnd, int X, int Y, int nWidth, int nHeight, bool bRepaint);
private const int MONITOR_DEFAULTTONULL = 0;
private const int MONITOR_DEFAULTTOPRIMARY = 1;
private const int MONITOR_DEFAULTTONEAREST = 2;
private static extern IntPtr MonitorFromWindow(IntPtr hwnd, uint dwFlags);
[DllImport("user32.dll", CharSet = CharSet.Auto)]
static extern bool GetMonitorInfo(IntPtr hMonitor, ref MONITORINFO lpmi);
[StructLayout(LayoutKind.Sequential, CharSet = CharSet.Auto)]
internal struct MONITORINFO
public int Size;
public RectStruct Monitor;
public RectStruct WorkArea;
public uint Flags;
public void Init()
this.Size = 40;
public struct RectStruct
public int Left;
public int Top;
public int Right;
public int Bottom;
It's not a perfect solution (see comments in code) and a quite hacky, but it'll keep the app in "Windowed" mode and hopefully unblock you.
I apologize for the inconvenience this bug is causing you.
Thanks. I really appreciate it! I'll get this in a build to test shortly.
To confirm I understand what to expect: this will prevent "fullscreen mode" from being activated but will resize the window to take up full screen if "fullscreen" is attempted? If so that should do the trick. I'll let you know how our testing goes.
Yes, that's what it should do; hopefully it works properly (I only did some basic testing on my dev PC ). If you run into trouble please post issues to this thread, and I'll try to improve the solution.
Initial testing looks good. We are deep diving now. I'm also trying removing the delay, which should mean just a single frame in fullscreen mode, to see if that reduces the perceived flicker.
- I see the gaps around the window border on Win10 (as per your comment in the code)... I think it should be fine like this as a temp solution, and I expect there likely isn't a robust way to know exact pixel size of this invisible chrome?
- The script doesn't seem to have adverse effects on Mac builds (I may add some windows #defines in any case)
Could this bug be related to this one 1147620 ?
It does happen in full screen mode in Win 10.
(When an additional screen is plugged as secondary cloned display, the performances drop dramatically).
I've found this strange issue with physics detection and Maximize on Play / Fullscreen mode.
When in Maximize on Play mode, character controller doesn't affect OnTriggerEnter and OnTriggerStay.
If I disable Maximize on Play / Fullscreen mode, there is more chance that character controller will trigger the event.
I've explain it here but now I've found that Maximize on Play / Fullscreen mode in build affects physics update.
Please, fix this as soon as possible because project is oriented using physics.
The bug I fixed only effects windowing behavior for Windows Standalone player (Win32) and has no relation to Physics performance or other runtime systems.
Please file a separate bug for this issue.
Is 2019.1.1 running behind schedule?
Some error in 2019.1.1
Should I use SRP before new version gets an update ?
ArgumentException: Getting control 7's position in a group with only 7 controls when doing ExecuteCommand
UnityEngine.GUILayoutGroup.GetNext () (at C:/buildslave/unity/build/Modules/IMGUI/LayoutGroup.cs:122)
UnityEngine.GUILayoutUtility.DoGetRect (System.Single minWidth, System.Single maxWidth, System.Single minHeight, System.Single maxHeight, UnityEngine.GUIStyle style, UnityEngine.GUILayoutOption options) (at C:/buildslave/unity/build/Modules/IMGUI/GUILayoutUtility.cs:464)
UnityEngine.GUILayoutUtility.GetRect (System.Single minWidth, System.Single maxWidth, System.Single minHeight, System.Single maxHeight, UnityEngine.GUIStyle style, UnityEngine.GUILayoutOption options) (at C:/buildslave/unity/build/Modules/IMGUI/GUILayoutUtility.cs:453)
UnityEditor.EditorGUILayout.GetControlRect (System.Boolean hasLabel, System.Single height, UnityEngine.GUIStyle style, UnityEngine.GUILayoutOption options) (at C:/buildslave/unity/build/Editor/Mono/EditorGUI.cs:9358)
UnityEditor.EditorGUILayout.IntPopup (UnityEngine.GUIContent label, System.Int32 selectedValue, UnityEngine.GUIContent displayedOptions, System.Int32 optionValues, UnityEngine.GUIStyle style, UnityEngine.GUILayoutOption options) (at C:/buildslave/unity/build/Editor/Mono/EditorGUI.cs:8334)
UnityEditor.EditorGUILayout.IntPopup (UnityEngine.GUIContent label, System.Int32 selectedValue, UnityEngine.GUIContent displayedOptions, System.Int32 optionValues, UnityEngine.GUILayoutOption options) (at C:/buildslave/unity/build/Editor/Mono/EditorGUI.cs:8328)
UnityEditor.MaterialEditor.LightmapEmissionFlagsProperty (System.Int32 indent, System.Boolean enabled, System.Boolean ignoreEmissionColor) (at C:/buildslave/unity/build/Editor/Mono/Inspector/MaterialEditor.cs:1363)
UnityEditor.Experimental.Rendering.HDPipeline.BaseUnlitGUI.DoEmissionArea (UnityEngine.Material material) (at Library/PackageCachefirstname.lastname@example.org/Editor/Material/Unlit/BaseUnlitUI.cs:840)
UnityEditor.Experimental.Rendering.HDPipeline.LitGUI.DoEmissiveGUI (UnityEngine.Material material) (at Library/PackageCacheemail@example.com/Editor/Material/Lit/LitUI.cs:916)
UnityEditor.Experimental.Rendering.HDPipeline.LitGUI.MaterialPropertiesGUI (UnityEngine.Material material) (at Library/PackageCachefirstname.lastname@example.org/Editor/Material/Lit/LitUI.cs:952)
UnityEditor.Experimental.Rendering.HDPipeline.BaseLitGUI.ShaderPropertiesGUI (UnityEngine.Material material) (at Library/PackageCacheemail@example.com/Editor/Material/Lit/BaseLitUI.cs:421)
UnityEditor.Experimental.Rendering.HDPipeline.BaseUnlitGUI.OnGUI (UnityEditor.MaterialEditor materialEditor, UnityEditor.MaterialProperty props) (at Library/PackageCachefirstname.lastname@example.org/Editor/Material/Unlit/BaseUnlitUI.cs:904)
UnityEditor.MaterialEditor.PropertiesGUI () (at C:/buildslave/unity/build/Editor/Mono/Inspector/MaterialEditor.cs:1707)
UnityEditor.MaterialEditor.OnInspectorGUI () (at C:/buildslave/unity/build/Editor/Mono/Inspector/MaterialEditor.cs:476)
UnityEditor.UIElements.InspectorElement+<CreateIMGUIInspectorFromEditor>c__AnonStorey1.<>m__0 () (at C:/buildslave/unity/build/Editor/Mono/Inspector/InspectorElement.cs:445)
2019.1.1f1 unable to recognise namespace "Unity.Entities"
Anyone got a fix? Really want to play with this but annoying how many problems there are even trying to get basic project running. Thanks
Initial thread - same problem keeps coming up again and again.
Have you added the Entities package through the Package Manager?
Do the ECS Samples work for you?
Yes, of course I added it. That's the first thing to check lol. Also searched and tried adding the Performance API code to the manifest (which didn't work).
Yes, the ECS samples work.
However, new project, import Entities, Mathematics, Hybrid Renderer etc does not work.
LMK if anyone has a solution.
After the update impossible to build for Android anymore I get lots of errors anyone have building problems?
Any examples or news about networking? That's the most important thing I was waiting for all this months.
In this simple script, Unity 2019.1 gives me an error that has not occurred in unity 2018.3 where it works perfectly.
do you have any advice for me?
Unity thinks that your children are empty, not parented.
I also had this problem when importing old project into new one with new prefab workflow.
I don't know.
Again a funny bug like this one :
Try to submit a bug report, maybe we will get a patch for 2020 .......
You'd better write a full description instead of making a video.
About my problem I partially resolved it by deselecting all content in hierarchy, and in my case, if you need watching inspector about an object lock the inspector on it, otherwise it returns the error