Official Unity 2017.2 is now available

Thanks for the awesome work Unity team.
Hope Unity continues improving.

 

Thanks for your continued hard work ya'll!

 

Where is C# version 6 support?
Will be included in 2017.3?

 

Was already added in 2017.1 as a player setting

 

It was experimental, i mean a full version support.

 

IIRC from various posts that is not happening until in some mid/late 2018.x

 

So, we can't use C# 6 experimental in production?

 

Depends entirely what platforms and features you use. For some the support in 2017.1 is already enough for production.

 

@Jacob_Unity

I have a question. Everything is fine, but where is the smart sprite? I'm waiting for that for two years

 

Thank you for macOS retina!

 

Where can I get the post processing stack that was shown in the Unity 2017.2 demo in Austin? Also where can I get the Volumetric Fog script that was also shown in the demo in Austin? Thanks.

 

Congrats for the release.

I would like to share some findings and some thoughts regarding the FBX Exporter.

I tried it with JoinMidPrototype04x06x01 from the prototyping package that is included with Unity. I wanted to change its pivot and place it at the bottom.
When I import the model in Maya using the importer, the pivot is set wrong (in unity it is at the middle of the model, in Maya at 0,0,0)
If I reset the pivot, the new pivot does not transfer back to unity after export.
Reading the documentation I understand it is so by design - changing the pivot is something that must be done often though.

Having to re-import the package in every new project is boring.

The scaling differences do not resolve by adjusting near and far fields, because this leads to limited precision in Maya viewport - edges seem to float all around, depending on the zoom level. A smaller scale in Maya is necessary to work properly, this is a known problem in Maya.

No support for animation - skinned meshes ( as skinned meshes instead of static ones) - well, more or less geometry - vertex colors - lightmaps export could be done via asset store packages, the hard part is exactly this one, animation.

I hope that you will find this feedback useful, fbx export in its current state is already very useful,
Kind regards.

 

Great stuff guys, tilemap is a fantastic addition.

 

The 'Post Processing' pack is available from the asset store. I believe that the 'Volumetric Fog' asset is part or the 'Adam Interior Environment'. Both assets are free.

There are many additional assets you may be interested in...

Asset Store Link
Unity Essential Assets

 

You guys are awesome.

 

Thanks for the new release and especially for the torrent.

I am almost at the end of my 7 year long development period of my very first super sexy game currently using 5.6.1. And i see on the release notes that terrain trees can cast shadows on the terrain with lightmapper now. This will give my game a significant fps boost.
However, as previously experienced, whenever i upgraded, i had to revise most of my code with most function names change and getting obsolete.
Question is; will i get headaches rewriting most of my code when i upgrade to 2017.2? Considering my editor tools and runtime scripts use nearly 80% of unity classes.

 

Is full iOS 11 and macOS High Sierra coming in the next patch.
Same question for any Andriod 8.0 missing features.
Please Jacob push for better mobile support, especially now Windows Mobile/Tizen/Samsung TV are dead!!

 

I updated to this version and now the android build has some performance problem, i got like 20fps (didn't check the exact number but it's not smooth at all), rolling back to the past version (20017.1.2f1) fixes the problem.


Edit : yeah nvm it's from here : https://forum.unity.com/threads/ugu...s-performance-regression.496849/#post-3251396

 

I went ahead and downloaded via torrent, which took 10minutes, awesome.
First i tried if terrain tree lightmap baking feature Works, well it doesnt.
It gives an error on the console

So, the feature doesnt work or do i need to do something different?

EDIT:
Another thing, when you are baking lightmap and move around in the sceneview, when any tree changes lod(mesh to billboard or otherwise) the lightmapper restarts.(It is not on auto)

EDIT2:
Tried the progressive Lightmapper and it ate my tree prefabs values, removed the leaf material both from terrain instances and the prefab itself...etc.
I feel like Many bugs are here, awaiting.
Who do i yell at?

EDIT3:
Speedtree models do cast shadows on terrain when lightmapped. Treemaker or ambient occlusion trees do not.
As speedtree models do not gain any fps, it makes things worse for my case(which is very generic).
One quick hack is to get a smiliar speedtree model, bake lightmaps then change the tree model to an ambient occluded one and arrange the shadow distance and tree billboard distance same. Then you get baked tree shadows for distant trees.
This offcourse comes with the caveat of spending insane amounts of Money for speedtree models which i wont be using at the end, or monthly payments for speedtree modeller which is only good for nothing.

 

Ok, I hope it comes out this year

PS. Are you planning on creating Unity like Anima2D? That would be great

 

When I enable DisplayP3 and build for iPad Pro 9.7in the display is almost completely messed up and I get this warning in Xcode 9.

Metal: Blending not supported for format 555

 

The most annoying thing I encountered when upgrading from 5 to 2017 was that a lot of code, both mine and purchased assets was using conditional compilation relying on the UNITY_5 macro which obviously isn't present anymore and that made also the script updater fail since that only start after a successful compilation.
You can quickly fix it anyway by redeclaring it globally and then after that change manually each instance of code to support the new 2017 macro.You don't want to leave the UNITY_5 macro declared.

 

Well,i havent checked to upgrade my Project yet. Because the advertised feature of terrain trees is not/partially working as i mentioned on my second post. I wouldnt mind changing my code as it is all mine, no purchased assets.
Anyways ill check the tree shaders and try to make them work first.

 

Hi, anyone else having issues with Canvas buttons not working at Retina resolutions on MacOS (High Sierra)? If I choose a non-retina resolution they operate as expected. They also work in the editor play view at retina resolution. They just don't appear to work full screen at Retina resolutions.

BTW: Thank you for retina support. I appreciate the attention to detail from the Unity Team.

Thanks!

 

I'm just too curious if 2017.2 fixes the memory leak on preview from 2017.1 or not. Does it fixed? @Jacob_Unity

 

A support for 18.5:9 aspect ratio will be included?

 

When will the patch with fixed Tilemap Collider 2D for Androind be available?

 

Should rather use UNITY_5_OR_NEWER.

--Eric

 

Hi Ippokratis, thank you for your feedback!

By default Unity shows the transform tools in the scene viewport at the center of the object and not the pivot.
This button toggles showing the transform tool at the center/pivot of the object:



Here is what I see for JoinMidPrototype04x06x01 with the button set to "Pivot":



For me the pivot appears at the bottom as expected.
Does changing this option fix the problem for you?

One workaround could be copy pasting the folder instead of importing from the asset store.

We're still trying to find the best way to handle large assets that work well with the Maya importer and FBX scene converter.

Animation support will be added in a future release

 

Hi,
Just upgraded yesterday from the last beta of 2017.2.x to 2017.2.0f3 an Android project.
The build process fails due to a bad value inside the AndroidManifest.xml :

CommandInvokationFailure: Failed to re-package resources.
/Users/laurenttournier/Documents/Unity/Android/android-sdk-macosx/build-tools/25.0.2/aapt package --auto-add-overlay -v -f -m -J "gen" -M "AndroidManifest.xml" -S "res" -I "/Users/laurenttournier/Documents/Unity/Android/android-sdk-macosx/platforms/android-21/android.jar" -F bin/resources.ap_

stderr[
AndroidManifest.xml:5: error: Error: String types not allowed (at 'configChanges' with value 'mcc|mnc|locale|touchscreen|keyboard|keyboardHidden|navigation|orientation|screenLayout|uiMode|screenSize|smallestScreenSize|fontScale|layoutDirection|density').

We didn't have any manifest in the plugin/Android folder or elsewhere.
So,
We tried to get the manifest.xml generated by Unity located in the Temp folder and modify it by erasing the "configchanges" value in the xml file, and put it in the plugins/Android folder => same result, error during the build with the same message.
Thanks,

 

I'm having the same exact issue. I have an android project that was building just fine in 2017.1.x, upgraded to 2017.2 and it won't build:

CommandInvokationFailure: Failed to re-package resources.
...\Android\sdk\build-tools\25.0.0\aapt.exe package --auto-add-overlay -v -f -m -J "gen" -M "AndroidManifest.xml" -S "res" -I "...l/Android/sdk\platforms\android-23\android.jar" -F bin/resources.ap_ --extra-packages com.unity3d.player -S "...\Temp\StagingArea\android-libraries\VuforiaWrapper\res"

stderr[
AndroidManifest.xml:5: error: Error: String types not allowed (at 'configChanges' with value 'mcc|mnc|locale|touchscreen|keyboard|keyboardHidden|navigation|orientation|screenLayout|uiMode|screenSize|smallestScreenSize|fontScale|layoutDirection|density').

]
stdout[
Configurations:
(default)

Files:
AndroidManifest.xml
Src: () AndroidManifest.xml

Resource Dirs:
Including resources from package: ...\Android\sdk\platforms\android-23\android.jar
applyFileOverlay for drawable
trying overlaySet Key=app_banner.png
trying overlaySet Key=app_icon.png
applyFileOverlay for layout
applyFileOverlay for anim
applyFileOverlay for animator
applyFileOverlay for interpolator
applyFileOverlay for transition
applyFileOverlay for xml
applyFileOverlay for raw
applyFileOverlay for color
applyFileOverlay for menu
applyFileOverlay for mipmap
Processing image: res\drawable-xhdpi\app_banner.png
Processing image: res\drawable-mdpi\app_icon.png
(processed image res\drawable-mdpi\app_icon.png: 90% size of source)
(processed image res\drawable-xhdpi\app_banner.png: 93% size of source)
(new resource id app_banner from xhdpi-v4\drawable\app_banner.png #generated)
(new resource id app_icon from mdpi-v4\drawable\app_icon.png #generated)
]
exit code: 1
UnityEditor.Android.Command.WaitForProgramToRun (UnityEditor.Utils.Program p, UnityEditor.Android.WaitingForProcessToExit waitingForProcessToExit, System.String errorMsg)
UnityEditor.Android.Command.Run (System.Diagnostics.ProcessStartInfo psi, UnityEditor.Android.WaitingForProcessToExit waitingForProcessToExit, System.String errorMsg)
UnityEditor.Android.PostProcessor.Tasks.TasksCommon.Exec (System.String command, System.String args, System.String workingdir, System.String errorMsg)
UnityEditor.Android.PostProcessor.Tasks.BuildResources.CompileResources (UnityEditor.Android.PostProcessor.PostProcessorContext context)
UnityEditor.Android.PostProcessor.Tasks.BuildResources.Execute (UnityEditor.Android.PostProcessor.PostProcessorContext context)
UnityEditor.Android.PostProcessor.PostProcessRunner.RunAllTasks (UnityEditor.Android.PostProcessor.PostProcessorContext context)
UnityEngine.GUIUtilityrocessEvent(Int32, IntPtr)

 

Update your plugins..

 

Hi @vkovec,

Thanks for the correction regarding the pivot point - you are right.
Maybe it makes more sense to include the fbx export option in Unity Editor instead of using a package.
A possible workaround for the scale problem could be to change the scale as part of the import export, so every package has the scale it likes. Big scale meshes do not work well on Maya.
It is very nice to know that you are planning to add animation later.

Kind regards.

 

@MrEsquire, thanks for your message, but, in our case, I doubt any plugins have different behaviors between the last Release candidate of the 2017.2 and its Release.

 

I have checked out the new Gradle build system for Android and there's an unintended behaviour, or at least I think there is.

When I build an app with Gradle it always has internet access permissions even if the app doesn't use internet. This doesn't happen with the Internal build system - the Internal one seems capable of detecting internet requirements automatically.

 

We are trying to make the scaling as simple as possible (the artists control scaling), but we are open to giving control to scaling for other workflows as long as it just works.

 

Dear unity team. Problem with image quality in lower than native resolution has been fixed. Big thanks! Good job

 

Why change the behavior of the standard shader?
All my standard shader materials have a smoothness of 1 to remove the specular lighting, but with 2017.2 it no longer hides specular highlights... Do I really have to disable the checkbox for highlights on every material used?

Also have a custom tri planar standard shader for my terrain which doesn't provide such a checkbox (Looks like plastic now). How do I remove the highlights in this?

 

Thanks for the new release. Unity team does a great job!

 

That's not the issue. For testing, I tried building an empty project with the same issue with the manifest file

 

clearly it tells u the problem: AndroidManifest.xml:5: error: Error: String types not allowed

 

Hey, I'm using Unity 2017.2. I can't 'apply' physics shapes to the sprite sheet, in the sprite editor. The changes aren't saved and every time I go back to edit the physics shapes, it regenerate automatically the physics shape like it has never been edited before.

The physics shape apply fine to a single sprite but doesn't work on a sprite sheet.

 

Is there an ETA on p1? Since it's been a while since 2017.2 first released will it jump straight to p2?

 

They should really keep people updated, its sad that so many had to make posts on this same question and issue.. what happened to Unity forum admin team

 

When p1 patch is coming?

 

I am interested in when the patch is coming as well, as the tilemap system is beyond buggy.

-InvalidCastExceptions happening in tile setting functions in release builds but not dev builds...
-Clearing of map not updating renderer properly.
-Assertion failure detecting bounds count and tiles being set count not matching when they definitely do match.

It's almost like no one bothered to test using this thing from code.