Skip to main content
I
ismom60389185
Participant
February 28, 2019
Question

Multiple errors when attempting to click into scene

  • February 28, 2019
  • 4 replies
  • 1377 views

Hi, I'm currently working on a windows 10 pc and I've been unable to advance work on my project because I frequently encounter the following two errors:

1.- The following error codes:

          Error code:(container.js:343)

          Error code:(engine.js:747)

          Error code:(bootstrap.js:3)

The first part of the error message is usually different but the error codes are the same.

2.- This other error that says something along the lines of "Error parsing properties list from file C...CharacterAnimator/2.0/WorkspacesV11/SavedWorkspaces/UserWorkspace_1.xml" or other file numbers,

The errors prevent the scene from loading, I can acces the rig screen but I'm unable to see the changes I make because I can't watch the scene.

I would greatly appreciate all your help! Thanks in advance!

    This topic has been closed for replies.

    4 replies

    J
    Jacqueline5E39
    Participating Frequently
    January 26, 2021

    Did you work it out?

    M
    mustafam68824692
    Participating Frequently
    March 2, 2019

    I was having same problem but I eliminated it by copying the project file to another place.

    alank99101739
    alank99101739
    Legend
    February 28, 2019

    Weird! I would try reaching out to DanTull​

    alank99101739
    alank99101739
    Legend
    February 28, 2019

    I recall some errors like this were caused by pins being added to a layer but outside the mesh for that layer. It was a bug to get the error, but the fix was just to move the handles/pins back over the mesh. Not sure if the same problem, but worth checking - just run through the layers and check and handles/draggers/pins etc on each layer Are inside the yellow mesh boundary.

    I
    ismom60389185Author
    Participant
    February 28, 2019

    I've followedyour advice and checked to see if there were any pins outside of the mesh but I couldnt find any.

    Just to make sure I didnt have any stray pins I erased the lateral views of my character on my .ai file and it worked momentarily, Character Animator was able to load the scene and I was even able to import an audio file and lip sync it. But then, when I tried to correct the visemes, Character Animator crashed and since then I have been able to intermitently work on it but I still get the workplace crash or the other error codes every 15 mins or so.

    This is the latest error message I've got:

    It was working normally and then while adjusting the visemes it crashed and gave me that error.

    I've also tried the alt  +  refresh scene to no avail.

    Sometimes restarting the application helps but it only works 50% of the time on the workspace errors, not on the container, engine or bootstrap codes.

    DanTull
    Adobe Employee
    DanTull
    Adobe Employee
    February 28, 2019

    Since these are affecting both files in the project (the temp.noindex folder holds various files that are loaded when displaying the scene) as well as the workspace file, it seems like there's a problem with accessing the disk reliably.

    One possible cause if these errors are intermittent is that there's a disk indexer, file synchronizer, or virus scanner that's competing with Character Animator when trying to access the files. We have retry logic in some places to try to reduce fragility in the face of such interference, but it does give up eventually.

    Another thing that comes to mind is that in some environments Documents and Roaming data are synchronized or on a file server, which could boost the odds of hiccups when trying to read/write those files.

    This is just an initial guess.

    There's a process monitor tool from Microsoft that can help show file access activity which might help to confirm/deny this hypothesis, but it produces a firehose of data that can be laborious and complex to interpret. One smaller scale answer is to have task manager up sorted by either CPU or disk access activity when you do an option refresh and see which other processes are popping up when there's a lot of busywork going on. That might provide clues if this really is a contention issue.

    DT

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