Official Unity 2018.1 is now available

Wohooo!

 

HORAYYYY

 

ECS not found.

 

Both direct and hub downloads are failing in TX, USA right now. Might be a server or CDN issue due to the load.

 

Great work!

 

@Jacob_Unity Can we get an example on how to bake and use the occlusion probe please? There's really no example how to use it :/

 

I was sort of expecting 2018.1f2 to use newer versions of post-processing and render pipelines packages when creating new projects from a template. But the versions it uses for this seem to be a few versions older than what is available to download through the package manager. eg postprocessing 2.0.3-preview instead of 2.0.5-preview and SRP modules 1.1.2-preview rather than 1.1.5-preview.

I have started a thread in the experimental graphics forum to ask for more info about this, but I thought I should post here to let people trying pipelines out via new project template feature that newer versions are available.

Confused about why old 1.1.2 versions ship with 2018.1

 

Thx. Great work and we have reached an important milestone !!

I love your enhanced Release Notes section with embedded pictures an even videos. Lot of efforts put in there.

 

I'm also unable to download using the Hub. Get about 80% threw when it fails. I've tried unchecking all the extra packages and just install the editor, still get the error `Editor Download Failed, Download request timed out after 5 seconds. Closing connections`

 

I couldnt find the "Native multiplatform AR APIs (preview)" in the package manager. How can I use it?

 

I'm having issues with Deferred Rendering on iOS. It doesn't seem to work in 2018.1 but works fine in the 2018.2 Beta. Anyone else having this issue?

 

Is it safe to use for production or starting a new project? the project is not something major but a simple android game

 

With this being 2018.1, does that mean that a 2018.2 beta project can't be loaded in it?

 

Hello I just download the new version. I was trying to test out the High-Definition RP. when I create the project I get a lot of shader errors and a lot of Kernel 'KMain' not found. Any thoughts?

 

Already did that since april, still no response. Ah well, another new feature without any clue how to use it :/

 

also when i open the light weight render i get a lot of shader errors and everything comes up pink

So when I try to open it up on my Surface it works fine... But on my desktop i am getting these errors

 

Thanks, thats what I thought. Didn't realise that the ".2" was a different version, just thought it was the latest beta. Think I might restore a backup prior to managing to get the project to upgrade to ".2", as well as deleting "Unity Hub", which spent hours downloading "2018.1", yet is not showing it as installed.

 

Hi,
Unity Download Assistent isn´t working with OSX 10.9.5...

Cheers,
Michael

 

We do a lot of unit test, so just wanted to show appropriation on least noticed improvement ...

Thank you Unity team (dev,QA) for making Test Runner execution (start and stop) lightning fast in 2018.1
It's now so much more fun doing unit test

 

Question about this bugfix ("[LPPV] Low performance in Scene view on complex scene") it's clearly marked as "Fixed in Unity 2018.1" but light probes proxy volume performance in Scene view are the same (very slow, 1-2 fps on complex scene with tons of objects with LPPVs) + there is no mention of this bugfix in Unity 2018.1 release notes... please, make it in to the next patch release for Unity 2018.1, it's very essential at least for me.

In Unity 2018.b2+ this was fixed and clearly it's working but beta are way too risky to work with...

 

I cannot run Unity ... It keeps telling me something about a link not being valid.... Can't do anything... If i keep clicking it then changes language... Great product, cannot even use it!

 

after moving to 2018.1 version the same project started getting :


trouble writing output: Too many field references to fit in one dex file: 145538; max is 65536.
You may try using multi-dex. If multi-dex is enabled then the list of classes for the main dex list is too large.

 

Is there a tutorial on how to setup the Unity Editor to use the new HD Render Pipeline?

 

A lot of bugs.

- Create Shader graph option is missing in upgraded project from 2017. Copied shader graph file from another project working. I tried all suggestion which I found on forum, still missing option in create menu.
- Shader Graph editor - properties node stuck on mouse cursor on change dropdown type of variable. Only solution close this editor and reopen.
- Upgraded another project from 2017, missing Package Manager menu option. No error.
- On computer with user rights problem with Visual studio. Unity do not recreate sln file and other important stuff. No intelisense, no debugging, no support.
- I have one project and after upgrade to 2018 not working at all. No error in console, scripts runs because I receive debug log, but nothing happen. Everything is acting like everything is fine. Debugging with visual studio impossible, because visual studio can't attach to unity. Just some stupid error without sense and **** off.

How you can call this release version?!

 

@timmunity Any details on when ARFoundation is likely to drop / any expected delays? I have a bunch of work that would really benefit when this is released

 

Nice!

 

This is the most UNSTABLE Unity version has ever existed!!

In my team we get unexpected editor crashes ALL THE TIME for no particular or reproducable reason.
The result is we end up losing all the day's work, scenes etc...

Unity 2018.1.1f1

 

+1

 

Sorry to hear

For me 2018.1 is the most stable version of unity I've used long time. No editor crashes on Mac and only 1 crash on Windows when I was trying to generate font awesome TMP asset with weird settings.. I've been using 2018.1 since beta 10.

I remember that some 5.x versions was very unstable and 2017 was somewhat unstable for me as editor crashed occasionally just after compiling scripts.

 

I haven't filled a bug report as we can't make a reproducible step by step case analysis or say anything about the conditions that may cause this crash....

The only thing I can do to "help" anyone from the Unity team is provide the editor log that shows the system exceptions that occur just before the editor crashes..

 

ok then, we will switch back to the .NET 3.5 runtime to see if that stops the frequent crashes.

Thanks a lot for your help.

 

This solved our frequent crashes.