This page lists any changes in 2017.1 which might affect existing projects when you upgrade from earlier versions of Unity.
For example:
Changes in data format which may require re-baking.
Changes to the meaning or behavior of any existing functions, parameters or component values.
Deprecation of any function or feature. (Alternatives are suggested.)
UnityWebRequestTexture.GetTexture() nonReadable parameter change
This convenience API had a bug where nonReadable worked the opposite way then it should, that is setting it to true would result in a readable texture and vice versa. Now this has been corrected and parameter works the way it’s documented. Note, that if you create DownloadHandlerTexture directly, you are not affected.
Particle SystemA component that simulates fluid entities such as liquids, clouds and flames by generating and animating large numbers of small 2D images in the scene. More info
See in Glossary Stretched BillboardA textured 2D object that rotates as it, or the Camera, moves so that it always faces the Camera. See Billboard RendererRenders Billboard Assets, either from a pre-made Asset (exported from SpeedTree) or from a custom-created file that you create using a script at runtime or from a custom editor, for example. More info
See in Glossary
See in Glossary Pivot parameter change
X axis pivots are now accurate on Stretched Billboards. You may need to reconfigure your pivot settings on affected projects.
Y axis pivots are also accurate now and Unity automatically reconfigures these pivots when you upgrade your project.
ShaderA small script that contains the mathematical calculations and algorithms for calculating the Color of each pixel rendered, based on the lighting input and the Material configuration. More info
See in Glossary macro UNITY_APPLY_DITHER_CROSSFADE change
The macro was used for implementing the screendoor dithering effect for LODA system for building multiplayer capabilities for Unity games. It is built on top of the lower level transport real-time communication layer, and handles many of the common tasks that are required for multiplayer games. More info
See in Glossary cross-fading objects in the fragment shaderThe “per-pixel” part of shader code, performed every pixel that an object occupies on-screen. The fragment shader part is usually used to calculate and output the color of each pixel. More info
See in Glossary. Previously you would need to pass the entire fragment IN structure to it. Now you only need to pass the screen position vector to it.
Remember that since 2017.1 the new dithercrossfade
option is added for #pragma surface
directive which can automatically generate the dithering code.
* 2018–04–12 Page amended with no editorial review
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Is something described here not working as you expect it to? It might be a Known Issue. Please check with the Issue Tracker at issuetracker.unity3d.com.
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thanks for helping to make the Unity documentation better!