Announcements

Between mid-October and November, the content on AREA will be relocated to the Autodesk Community M&E Hub and the Autodesk Community Gallery. Learn more HERE.

Timeline range and playback range keeps resetting!

Timeline range and playback range keeps resetting!

Anonymous
Not applicable
6,001 Views
10 Replies
Message 1 of 11

Timeline range and playback range keeps resetting!

Anonymous
Not applicable
Hi, I have a scene that I want to run from frame 0 to frame 95, and I will set it like this every time I open my scene file in maya. I save, I quit, and when I open it up again, it's reset the time-range to 1-48 for the entire scene and 1.25-30 for the playback. It should be noted that I didn't make the scene from scratch, it's an exported scene from Syntheyes.

Is there something I'm missing here?
0 Likes
Accepted solutions (1)
6,002 Views
10 Replies
Replies (10)
Message 2 of 11

Anonymous
Not applicable

3 years later and I'm still having this problem.  Opening a new file doesn't change the start/end time of the animation/playback-range.  So when I first start up Maya, the playback range is set to 1-24, and the animation range is set to 1-48.  If I open a scene, this range stays the same, and I just have to remember what it was that it was set to in this scene before.  Now if I CHANGE it, say to 1-200, then open a new file, it STAYS at 1-200.  Wierd!

 

I was using a PLE version of 2010... or 2011, don't remember which one.  I pretty much gave up on Maya at that point as I was having a tough time learning it, but I'm back to it again, 3 years later...  Now I'm using an educational version of 2014, and the EXACT same problem has manifested itself.

 

I'm hoping this is just some stupid setting I accidentally set, or forgot to un-set...  It seems to remember what frame I had it set to, just not the playback range or animation range.

 

In those 3 years, I've upgraded my computer a few times, but kept the same hard drive (so same OS, same installation of maya PLE 2010 rotting away...)

0 Likes
Message 3 of 11

Anonymous
Not applicable

So... nobody knows what could possibly be causing this or what I could do to resolve this issue?

0 Likes
Message 4 of 11

Anonymous
Not applicable

Windows -> Animation Editors -> Expression Editor.

 

Select Filter -> By Script Node Name.

 

Find the script node named "sceneConfigurationScriptNode",

It's "Execute On" type should be "Scene Configuration (Internal)".

 

If this still not fix your problem, check the script node list,

find out which script node has Execute On "Open/Close",

and script = "playbackOptions -min 1 -max 24 -ast 1 -aet 48".

remove it.

 

 

 

0 Likes
Message 5 of 11

Anonymous
Not applicable

Everything seems to check out there, and there aren't any script nodes that have "execute on:" set to "open/close". 😞

 

I've also noticed that when I open a file, it doesn't remember how I've laid out my windows.  For example, I had two separate windows for left and right eye cameras on my second monitor, and I have to re-make those every time I open up my scene file... in addition to setting the timeline back to what it should be.

0 Likes
Message 6 of 11

Anonymous
Not applicable

Bump, as I REALLY need this fixed...

 

Another thing I noticed is that all my viewport settings seem to carry over if I open a scene.  So if I'm working on one scene and say... I have viewport 2.0 switched on, with AO, motion blur... etc etc, if I open a completely different scene file, it all stays the same, including the timeline as I've said above.

0 Likes
Message 7 of 11

Anonymous
Not applicable
Accepted solution

HOOLLEEEYYY JESUS!  Just found the solution.

 

Open -> ☐ -> Execute Script Nodes (was for some reason disabled by default).

Message 8 of 11

christianbumba
Participant
Participant

I want to confirm this solution. Thanks!

Message 9 of 11

parabhdeep
Enthusiast
Enthusiast

Thanks mate, i stuck for the same

0 Likes
Message 10 of 11

3dusan
Community Visitor
Community Visitor

@Anonymous 
Thank you very much that you posted the solution on your own question.
This same problem was driving me nuts.
Cheers

 

0 Likes
Message 11 of 11

hamsterHamster
Advisor
Advisor

Woah, thanks, surprised.

However, this is double-edged sword, as enabling script execution makes you vulnerable to Maya malicious scripts.


,,,_°(O__O)°_,,,
Maya2019.1 @ Windows10 & GeForce GTX1080Ti

If the post was helpful, click the
 ACCEPT SOLUTION  button, so others might find it much more easily.

0 Likes