Cannot Edit or Delete Expressions

Cannot Edit or Delete Expressions

timdan
Advocate Advocate
2,120 Views
3 Replies
Message 1 of 4

Cannot Edit or Delete Expressions

timdan
Advocate
Advocate

I've searched the forums, and the totality of the internet (probably exaggerating), and cannot find a solution to this. When I try to edit an expression that already exists, nothing happens. When I click to create a new expression, nothing happens. I do not get an error as most other posts of written about where' EEexprEdTextEditor = 0. This is not the case for me. I'm also not on a Mac (currently running Win 10, and Maya 2017 u4).

 

I need a solution that does not involve deleting my prefs. Can't do it. Too much of our pipeline revolves around those, and I cannot afford to delete them every time something silly like this happens. 

 

Please help.

 

Thanks,

 - Tim

+ timdan

-
http://www.timdan.com
0 Likes
Accepted solutions (1)
2,121 Views
3 Replies
Replies (3)
Message 2 of 4

timdan
Advocate
Advocate
Accepted solution

Ok... so I deleted windowPrefs out of the prefs folder, and that did the trick. Didn't have to dump the whole folder, and my expression editor is up and running.

 

Good talk. 😛

+ timdan

-
http://www.timdan.com
0 Likes
Message 3 of 4

sean.heasley
Alumni
Alumni

Hi @timdan

 

Does this happen in specific scenes or on a new empty scene as well?

 

Also, if you go to edit an expression does anything appear in the history?

 

Finally, is updating to update 5 may help but will this throw off your pipeline?

 

 Edit: Just saw your new post. good talk indeed 😛

 

 

0 Likes
Message 4 of 4

timdan
Advocate
Advocate

Hey @sean.heasley,

 

For what it's worth, it happened in new files and old files. What showed up in the history was just the call to load the editor:

expressionEditor EE "[objectShape]" "[value]";

But nothing would actually happen. No errors or anything.

Lastly, I've been considering update 5, but we did some testing with our animators, and they had some serious issues with the sluggishness of playback, so we've been hesitant to move forward with it. 

 

Thanks for following up, though!

+ timdan

-
http://www.timdan.com