<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Maya 2018 stability? in Maya Forum</title>
    <link>https://forums.autodesk.com/t5/maya-forum/maya-2018-stability/m-p/7289199#M51746</link>
    <description>&lt;P&gt;I'm thinking about moving over a team of Artists to 2018 from 2016, does anyone have any suggestions or issues or learning curves when they switched over? Are there enough new features for it to be a good idea for us to switch?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 10 Aug 2017 00:11:03 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2017-08-10T00:11:03Z</dc:date>
    <item>
      <title>Maya 2018 stability?</title>
      <link>https://forums.autodesk.com/t5/maya-forum/maya-2018-stability/m-p/7289199#M51746</link>
      <description>&lt;P&gt;I'm thinking about moving over a team of Artists to 2018 from 2016, does anyone have any suggestions or issues or learning curves when they switched over? Are there enough new features for it to be a good idea for us to switch?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Aug 2017 00:11:03 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/maya-forum/maya-2018-stability/m-p/7289199#M51746</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-08-10T00:11:03Z</dc:date>
    </item>
    <item>
      <title>Re: Maya 2018 stability?</title>
      <link>https://forums.autodesk.com/t5/maya-forum/maya-2018-stability/m-p/7289503#M51747</link>
      <description>&lt;P&gt;I've found 2018 to be pretty stable. I haven't been able to put it through some bigger paces yet, but I'm pretty sure I'm going to migrate from 2016.5. I've discovered a few bugs, but I'm not sure if they are Linux specific and support was able to reproduce so I might see a fix in U1.&lt;BR /&gt;&lt;BR /&gt;The 2018 release has all of the features you saw in 2017 (which is a LOT), plus a few extras that will enhance your workflow. This release cycle is focused on stability and workflow, so you're not likely to see a bunch of big ticket features, but smaller more subtler things that will enhance the way you work. Honestly, stability is all I'm asking for after that crazy 2017 cycle &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Aug 2017 05:00:01 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/maya-forum/maya-2018-stability/m-p/7289503#M51747</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2017-08-10T05:00:01Z</dc:date>
    </item>
    <item>
      <title>Re: Maya 2018 stability?</title>
      <link>https://forums.autodesk.com/t5/maya-forum/maya-2018-stability/m-p/7499428#M51748</link>
      <description>&lt;P&gt;This end, it’s throwing up *a lot* of cycleCheck errors on character rigs that work fine under 2017. As far as I can tell, there are no real evaluation cycles, and the issue is resolved in some cases by splitting or unifying compound connections.&lt;/P&gt;</description>
      <pubDate>Sat, 28 Oct 2017 23:55:02 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/maya-forum/maya-2018-stability/m-p/7499428#M51748</guid>
      <dc:creator>kimonmatara</dc:creator>
      <dc:date>2017-10-28T23:55:02Z</dc:date>
    </item>
  </channel>
</rss>

