Skip to main content
A
alexandrarudd
Participant
February 13, 2019
Answered

Accidentally put trigger + cycle layers on same layer- is my project destroyed?

  • February 13, 2019
  • 5 replies
  • 454 views

I was trying to make different hands for my puppet to cycle through, and at first I thought I was supposed to make it a key trigger. After making the triggers, I noticed it wasn't working and when I pushed the key to trigger the new hands, it stayed the same. Then I remembered that I was supposed to make put the "cycle layers" behavior on the layer, not make it a trigger. Without thinking, I added the "cycle layers" behavior to the hands group before deleting the triggers. This caused the program to go absolutely beserk. Now it says my file is corrupted and won't open the project. Is there any way I can fix this, or is all of my work gone for good? It took me a long time to get the rig just right, I would hate to have to do everything all over again. Please help!

This topic is closed to new replies. Start a new post to keep the conversation going.
Correct answer DanTull

For those following along at home: after inspecting a copy of the project, I recognized the error message indicated there was a malformed reference file. These are little files that point to history states in the project for use in history panel bookmarks (an automatic one in this case). Deleting that file got the project back to good.

For reference, the error message is:
libgit2 error -1(4/Corrupted loose reference file: refs/tags/v161/recent/95) returned from git_tag_create(&tagOid, repoP->mRawRepoP, snapshotID.c_str(), target.p, signatureP.get(), message.c_str(), bAllowOverwrite)


In this case, the file to delete was (Ch Data/repo.noindex/refs/tags/v161/recent/95). These files just contain ids that point to records in the project database, so deleting an invalid one does not lose any data.

I'm going to investigate a bit further why this minor damage actually prevents the project from being opened, but will share this diagnosis/remedy in case it saves somebody else some grief.

Dan Tull

P.S. Thanks as always to Alan for putting up the signal flare so I spotted this one sooner rather than later!

5 replies

DanTull
Adobe Employee
DanTullCorrect answer
Adobe Employee
February 14, 2019

For those following along at home: after inspecting a copy of the project, I recognized the error message indicated there was a malformed reference file. These are little files that point to history states in the project for use in history panel bookmarks (an automatic one in this case). Deleting that file got the project back to good.

For reference, the error message is:
libgit2 error -1(4/Corrupted loose reference file: refs/tags/v161/recent/95) returned from git_tag_create(&tagOid, repoP->mRawRepoP, snapshotID.c_str(), target.p, signatureP.get(), message.c_str(), bAllowOverwrite)


In this case, the file to delete was (Ch Data/repo.noindex/refs/tags/v161/recent/95). These files just contain ids that point to records in the project database, so deleting an invalid one does not lose any data.

I'm going to investigate a bit further why this minor damage actually prevents the project from being opened, but will share this diagnosis/remedy in case it saves somebody else some grief.

Dan Tull

P.S. Thanks as always to Alan for putting up the signal flare so I spotted this one sooner rather than later!

DanTull
Adobe Employee
DanTull
Adobe Employee
February 14, 2019

Small update: I was able to reproduce this issue from scratch by artificially creating a malformed bookmark file. I don't know the failure that created it exactly (my guess is a transient error while writing the file), but it shouldn't be hard to make this condition less fatal at least.

DT

alank99101739
alank99101739
Legend
February 14, 2019

Can you try the “Undo” button? Otherwise I would try customer support or ask someone like dtull-adobe​ (Hopefully that is Dan Tull - he got renamed?)

DanTull
Adobe Employee
DanTull
Adobe Employee
February 14, 2019

Even if undo gets you out of trouble, I'd be somewhat curious to inspect the project to try to understand the bug.

If undo doesn't work, maybe I can recover an earlier state from the project. If you can zip it up and use a private message to send me a link, I'll take a look.

DT

A
alexandraruddAuthor
Participant
February 14, 2019

I wish I could, but I can't undo because my project won't even open in CA anymore. I will send you the project though, it's worth a shot!

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices