Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
"If I open Maya and then go to file > open, Maya prompts me to save the empty scene it created when it opened. It also auto-saves blank scenes if I leave it open for a while. "
As Maya starts, it starts without loading plugins. At this point, it has its own idea what a 'fresh new scene' is and that whatever state it's in now, is an empty state (clearly).. So at this point if you would do File > Open, Maya wont give you the Save dialog when you're in an empty scene. However, then plugins get loaded and add their own default nodes to the scene. As soon as that happens, Maya flags the scene as "Dirty". In which case, if you try to do a File > Open, you get the Save scene dialog even though your scene is "empty".
Seeing as everyone needs to load some kind of plugin in Maya (even default ones), you will always get this.
Unless Autodesk comes up with a way that forces developers to register "onNewScene" created nodes with some kind of "clean slate" manager.
I'll finish all my render settings, then save, then I'll start a batch render, and then go to open a different scene file, and I'll get a "save changes to scene?" dialog. No changes were made since last save; I just selected Render > Batch Render
or similarly,
I'll finish editing a model, then save, then export a file (most often as an obj), and then go to open a different scene file, and I'll get the same "save changes to scene?" window. Again, no changes were made since last save, I just selected File > Export.
Save scene, tumble camera (default perspective camera), then go to open a difference scene file, and again, "save changes to scene?" dialog.
No changes were made to the scene, other than the persp camera's position... which I guess technically is a change to the scene, but can changes to the default persp camera's translation/rotation be ignored by Maya as a "change" to the scene?
Maya sees those cameras as part of the scene, so any changes to them will make the scene 'dirty'. Many 3d packages see the 'viewport cameras' as part of the UI. You can't actually animate them and you won't see them in an outliner equivalent. So any changes to them won't make the scene dirty. You have to actually create a new camera to do work. That's just not how Maya works.
PS: To be honest, I have a set of patches for native Maya MEL scripts, and this request is completely disabled in my Maya. You don't need to know if you have any changes or not in your scene, just press Ctrl-S when you need, and that's it. (and set incremental save option for 'File-Save'). This dialog is completely redundant for professional work imho.
Top voted as one of two most annoying every-day-issues of Maya
- it looks like a simple script could be a solution, already provided by your users for you
- "under review"
- again 5 months time
- today checking Maya 2019 update1
No change.
What's going on in your heads, Autodesk? Among all your experienced tool developers not anyone who could spend 1 hour to end this? That's IMHO also a desaster from a "PR" point of view.
You don't need satisfaction surveys, if you yet don't listen to this here. At least someone could explain, what's going on.
One of our regular regression tests involves checking various situations to ensure that "empty scenes" don't trigger the "Do you want to save" prompt, so rest assured that this issue never leaves our radar. The problem with simplistic approaches such as this script is that while they work well for some users there are many others for whom they would not work well. One of our primary credos is "Though shalt not lose data" so if the answer to the empty scene question is ambiguous, we have to ask; a small annoyance is trumped by a data loss if you exit without saving critical information.
We do provide a method for clearing the file modification state which you can hook into any custom plug-in code that creates or modifies nodes (assuming you know that it's a non-destructive change of course). The command used to check for an unmodified file can also be used to set the file to be unmodified, regardless of its current state.
The sense is to get rid of stressful warnings with an really empty scene.
This happens right when you open Maya. You want to open your project and the software is so "unsmart" to prompt you, to decide, if you want to keep the empty scene, which is 5 seconds old and you never worked with.
Maya could at least know, when it created a scene itself without anybody having touched it.
(Seems indeed strange, that it's so hard to implement it, but I am no programmer to judge about that.).
(Apologies for the delay - I've been on vacation the past 2 weeks.) I dug a bit deeper into this and found that our internal regression test that looks for the empty scene save request only runs by itself on startup, so it is never checking for things created by plug-ins that load later, as @_wOLVERINe_ described. For example the "mtoa" plug-in is known to create changes in the scene when loaded. Unfortunately Maya itself cannot tell the difference between a change that really is required when you save the scene and one which is not; it relies on the plug-in to adjust the change state when appropriate. There should still be a potential for ensuring the state is clean on startup, after file-new, and after file-open though, even if they load or unload plug-ins. Thanks for bringing this up as an issue!
Though plugins may be doing their own things to 'change the environment' of the scene... perhaps a 'brute force' approach might help. IE, if scene has no geometry (or whatever the user might consider relevant), don't ask for confirmation. Perhaps an option for users to indicate what conditions need to be 'unmet' to avoid the dialog, similar to the way users can specify what is shown in a panel.
ajoss13's suggestion is certainly helpful, though it would need to be set up manually for each new Maya version. Also, some users, like myself aren't that familiar with MEL, so this approach might not be implemented as often as could be beneficial to users.
