Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice

Some things not working after upgrade to 4.5

Discussion in 'Editor & General Support' started by guillopuyol, Jun 4, 2014.

  1. guillopuyol

    guillopuyol

    Joined:
    Jul 16, 2013
    Posts:
    10
    I upgraded a project to 4.5 and I've found several things don't work...

    CombineChildren throws a bunch of errors...

    Some of my models were sharing an animation... now a few of them won't animate at all.

    I can live without meshcombine, but why is it making my models not animate??
     
  2. guillopuyol

    guillopuyol

    Joined:
    Jul 16, 2013
    Posts:
    10
    Has anyone experienced this? I'm confused on why without any changes on my code or settings, now the objects won't animate... There are no errors on the console (aside from those thrown by the CombineChildren script).
     
  3. Graham-Dunnett

    Graham-Dunnett

    Unity Technologies

    Joined:
    Jun 2, 2009
    Posts:
    4,287
    It's hard to give any advice without more information from you.
     
  4. guillopuyol

    guillopuyol

    Joined:
    Jul 16, 2013
    Posts:
    10
    Graham, thanks for getting back to me. There's not a lot of additional info to give. The project worked before upgrading now it doesn't. The animation is a legacy animation shared between several objects, some work some don't.

    If there's any specifics that would help you help me, please let me know... I NEED to figure this out ASAP
     
  5. guillopuyol

    guillopuyol

    Joined:
    Jul 16, 2013
    Posts:
    10
    Ok... For some reason during import, some objects Static Batching property was clicked ON... so they were behaving as Static.