Forum rules - please read before posting.

ConstantIDs changed on version control merge

magamistmagamist
in Technical Q&A
My team has been having a lot of issues with ConstantIDs and version control. In particular, whenever we use UniMerge to merge scenes, it seems that everything's ConstantID changes but the references stay the same. For example, an action might enable Hotspot1 with ConstantID 123456, and when we merge, it says it can't find 123456 because Hotspot1 now has ConstantID 5152351. On the other hand, the public variable references from regular Unity scripts are not broken on merge. 

Any ideas for how to keep ConstantIDs from changing like this?

Comments

  • magamistmagamist
    If UniMerge is the problem, and you have a compatible way to merge, we aren't tied down to it. We use UVC (which uses svn) for version control and UniMerge for scene merging.
  • magamistmagamist
    Figured it out - UniMerge puts a copy of each scene in the same hierarchy, which causes a duplication of IDs and makes the version in the "mine" column always generate new IDs.
  • ChrisIceBoxChrisIceBox
    You can set change the Set value in the Constant ID inspector from Automatic to Manual - that will cause it to only ever take the value you set it (and retain the one it already has until you do).
  • magamistmagamist
    What happens if you end up with two with the same?
  • ChrisIceBoxChrisIceBox
    AC will never assign a Constant ID number twice in the same scene, even if the first is manually set.  If two have been intentionally set as the same, then AC will just work with the first one it finds - though there's no way to choose which order it looks.
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links

Categories

Welcome to the official forum for Adventure Creator.