Feedback wanted - Your feeling about 2019.2 in its current state (b7)

What is the "old behaviour" that's being guaranteed here? Is there built-in Unity shortcuts that shouldn't execute in play mode?

Shouldn't those have to play nice like the rest of us have to and

Code (csharp):

1. if (Application.isPlaying) return;

+

 

new scene (def. on windows Ctrl+N) won't execute in playmode
and I only *wish* build (def. Ctrl+B on windows) *wouldn't* execute in play mode -
that mainly due to mistyping ctrl+v, but there are probably more actions which shouldn't be/aren't permitted in play mode

 

Not sure if this is helpful to anyone and is just my experience but the only stable version of Unity 2019.2 i was able to eek out is 2.0a13, everything else just takes hours to clear the errors and bugs out of, whoever is release manager for Unity should probably do regular build tests using defaults in their various HUB configurations because Hub/PM don't seem to be working as intended. (basis of tests is clean installs in a fresh directory, not existing projects, i should expect 100% of these to work or they shouldn't be exposed by default).

The Progressive CPU/GPU lightmapper also appears to work well in this version. Issues with other Unity 2019.2 versions range from Unity default setup including conflicts with itself (PP2), Unity selecting bizarre directories to drop configs (PP2.17) which results in permission issues, Unity pre-emptively enabling options based on incomplete info resulting in PM errors (Rider plugin auto-enable as a Package but it's a fresh project, Rider hasn't been opened yet). Sadly the Asset store issue is universal, there's not a single version of Unity that can mitigate the CEF / editor freeze issue, so it takes a few hours to get a single Asset from the store if you have over 1000 Assets, but once it has cleared it's internal meltdown you can download normally until it throws it's fit again. Hopefully once UT reach a "feature complete" stage of their current Khanate style expansionism they'll go back and fix the magic so it no longer causes pain, painless magic is best magic!

 

Hi @LeonhardP. Can you get someone to look at Case 1140018? It has been confirmed by Nvidia that it's Unity editor bug.

 

Please go back and fix it.

There's no way to make an HDRP asset? I have imported the HDRP package but the instructions:
Create an HDRP Asset by selecting Assets > Create > Rendering > High Definition Render Pipeline Asset.
Are either out of date or the apps broken.

There is no such thing as Assets > Create > Rendering
in the menu.

Uber frustrating! unity gets out the door way more buggy than I remember it. I can handle fixing my own code flaws and fixing stuff that gets deprecated but Im fed up with trying to fix in-engine bugs and figuring our why menu links are completely missing.

That's a no from me

EDIT: I can't do any work until someone explains to me whats wrong.
Please don't take too long!!!!!!!

 

Create an HDRP Asset by selecting Assets > Create > Rendering > High Definition Render Pipeline Asset.

OK Unity, sure, whatever you say

 

All that really indicates is that the HDRP package is not working for your project - if it was working then you would see that menu option.

Are there errors in your console? How did you import the HDRP package? Using package manager? Which version of HDRP?

Try removing it and adding it again. Also you could try starting a fresh Unity project using the HDRP template, so you can see how it is all supposed to show up and work.

 

Why are you using the alpha version then?

If you're frustrated because of these things, use the LTS version (2018.4). Or maybe the tech release (2019.1).
But certainly not the 2019.2.0a7 when the question was about 2019.2.0b7.

And check which HDRP package is compatible with the engine version you end up with.

 

One thing that I do like about 2019.2 is that for us at least, it crashes a lot less.
Although I think that most of our crashes are due to firebase.

 

For some time i have just hit the update release button when Unity told me to. 2019 destroyed my project folder that has been with me for a year. it wont even open back in 2o18 now. I have already been told that i should back up before opening in a new release. Guess Ill know better next time. If any one has any advice for somone who would just like to recover the project in an earlier 2018 version, please let me know...