Manage scene states dialogue - please fix it!

[tim.atkinsonNHY4C]

Hi,

I realise this has been raised before, however so far i see no fix yet.

Is there a script to run this dialogue?

I would like to use the 3ds max batch render, and turn on/off layers per shot. (different sun set ups by layer)

I used to create scene states, and just enable layers (although it did screw up if i added a new layer!)

I have looked into state sets, which do turn on and off layers, but the batch render dialogue only has an option for scene states.

I don't have full admin login, and it's not an option for me.

I tried running max as admin, it seems to lose the mapped network drives, and anyway, it didn't work.

I tried creating a link via the quad menu for the scene state dialogue, didn't work.

I am setting this up for others, who don't have plugins such as RPM, and I don't think they will understand Prism.

although they are stills, i don't want to animate sun positions, as i may have motion blur elements, and generally don't want to complicate the scene.

Can you please give me a fix for the manage scene states dialogue?

Many thanks!

Tim

[tim.atkinsonNHY4C]

Hi,

I realise this has been raised before, however so far i see no fix yet.

Is there a script to run this dialogue?

I would like to use the 3ds max batch render, and turn on/off layers per shot. (different sun set ups by layer)

I used to create scene states, and just enable layers (although it did screw up if i added a new layer!)

I have looked into state sets, which do turn on and off layers, but the batch render dialogue only has an option for scene states.

I don't have full admin login, and it's not an option for me.

I tried running max as admin, it seems to lose the mapped network drives, and anyway, it didn't work.

I tried creating a link via the quad menu for the scene state dialogue, didn't work.

I am setting this up for others, who don't have plugins such as RPM, and I don't think they will understand Prism.

although they are stills, i don't want to animate sun positions, as i may have motion blur elements, and generally don't want to complicate the scene.

Can you please give me a fix for the manage scene states dialogue?

Many thanks!

Tim

[Swordslayer]

Which one, the new state sets? Then it would be:

(dotNetClass "Autodesk.Max.StateSets.Plugin").Instance.ShowMainFrame()

[Swordslayer]

Which one, the new state sets? Then it would be:

(dotNetClass "Autodesk.Max.StateSets.Plugin").Instance.ShowMainFrame()

[tim.atkinsonNHY4C]

Thanks for your help, but i am looking for the manage scene states dialogue. not the state sets dialogue.

[tim.atkinsonNHY4C]

Thanks for your help, but i am looking for the manage scene states dialogue. not the state sets dialogue.

[Swordslayer]

That one is simpler, turn on macrorecorder and open it and it will you show you the command:

actionMan.executeAction -1682387772 "4112"

[Swordslayer]

That one is simpler, turn on macrorecorder and open it and it will you show you the command:

actionMan.executeAction -1682387772 "4112"

[tim.atkinsonNHY4C]

Thank you for your help,

Can you please expand on your answer?

Are you saying that this command, run as a script, will open the Manage Scene States dialogue box?

I ran it, nothing happened, i made a script and ran that, nothing happened,

Have you been successful in opening this dialogue in 3Ds max 2018?

thanks

Tim

[tim.atkinsonNHY4C]

Thank you for your help,

Can you please expand on your answer?

Are you saying that this command, run as a script, will open the Manage Scene States dialogue box?

I ran it, nothing happened, i made a script and ran that, nothing happened,

Have you been successful in opening this dialogue in 3Ds max 2018?

thanks

Tim

[Swordslayer]

Yes, it should toggle the dialog i.e. show it if it's closed and vice versa. I can only test on 2019 and 2020 and on both it works as expected, but as I said before, you can turn on macro recorder, open it via UI and see the command it recorded.

[Swordslayer]

Yes, it should toggle the dialog i.e. show it if it's closed and vice versa. I can only test on 2019 and 2020 and on both it works as expected, but as I said before, you can turn on macro recorder, open it via UI and see the command it recorded.

[kgokhangurbuz]

Hello @tim.atkinsonNHY4C ;

I know that this is a long lasting problem in 3ds max and users make it work in different ways.

here's a link with various replies for this issue:

https://forums.autodesk.com/t5/3ds-max-forum/3dsmax-scene-states-not-showing-up/td-p/7380106

As for me, it works like this:

-I open 3ds max, it doesnt work

-I close 3ds max and re-run it in administrator mode, it doesnt work

-I close Administrator 3ds max and re-run 3ds max (regularly) and it works (strange enough, right?)

I also tried what @Swordslayer (hi, by the way) suggested. It does not work in 2017 and 2018 but 2019 and 2020 versions.

[kgokhangurbuz]

Hello @tim.atkinsonNHY4C ;

I know that this is a long lasting problem in 3ds max and users make it work in different ways.

here's a link with various replies for this issue:

https://forums.autodesk.com/t5/3ds-max-forum/3dsmax-scene-states-not-showing-up/td-p/7380106

As for me, it works like this:

-I open 3ds max, it doesnt work

-I close 3ds max and re-run it in administrator mode, it doesnt work

-I close Administrator 3ds max and re-run 3ds max (regularly) and it works (strange enough, right?)

I also tried what @Swordslayer (hi, by the way) suggested. It does not work in 2017 and 2018 but 2019 and 2020 versions.

[tim.atkinsonNHY4C]

Hi all,

we fixed the issue by renaming the max ENU folder, essentially returning max to defaults. then run the dialogue, and it opens. We set max to run as admin by default too.

I will have to build up my scripts toolbar, as there was probably something in there causing the issue. this was mentioned in the forum, but i was trying to avoid it, because of my toolbar/forest pack links etc. I found this fourm page; https://forums.autodesk.com/t5/3ds-max-forum/manage-scene-states-stops-working-when-i-install-vray/t...

which did help, sorry i didn't find it earlier, probably didn't help creating a new one!

thanks for your help. I am now able to save scene states and use them in conjunction with the max batch renderer. 

Regards, Tim

[tim.atkinsonNHY4C]

Hi all,

we fixed the issue by renaming the max ENU folder, essentially returning max to defaults. then run the dialogue, and it opens. We set max to run as admin by default too.

I will have to build up my scripts toolbar, as there was probably something in there causing the issue. this was mentioned in the forum, but i was trying to avoid it, because of my toolbar/forest pack links etc. I found this fourm page; https://forums.autodesk.com/t5/3ds-max-forum/manage-scene-states-stops-working-when-i-install-vray/t...

which did help, sorry i didn't find it earlier, probably didn't help creating a new one!

thanks for your help. I am now able to save scene states and use them in conjunction with the max batch renderer. 

Regards, Tim

[MMDMedia]

Hi,

Just encountered this issue today with Max 2017. Never had this problem before but it appeared just at the least convenient time, after referring to this thread and many others around we tried nearly every fix including - Remaking ini files, deleting ENU folder, uninstalling renderers, resetting workspaces and UI, running as admin, trying on different users. We're not sure if our problem is the same as others, but we found a workaround so I figured it be worth sharing.

Some explanation of our setup.

• Did have 3Dconnexion mouse briefly installed on this computer years ago, but was uninstalled and corresponding max drivers removed at least a year ago (and scene states had worked since then)
• Never had Vray on this machine (identified as a culprit in other threads)
• Using Corona, Redshift, realflow, and tyflow (possible any of these cause similar issues to Vray, did uninstall Corona and problem persisted)
• User has full local administrator rights
• Scene states have worked on this machine in the past from a fresh max file, only need to use scene states on maybe 5% of projects, so it has been a while since it was used in a new project

We did identify that old scenes that had utilised scene states would correctly open the manager, however old scenes that didn't have scene states would refuse to open it, and of course newly created files would also refuse to open the manager. Interestingly, saving an old scene with the working scene state manager as a new file would retain the working scene state manager.

Here's our workaround after trying everything else. 

1. Close max entirely
2. Locate  C:\Program Files\Autodesk\3ds Max 2017\stdplugs  and find the  SceneStateUtil.dlu  file.
3. Move that file to a safe spot, desktop or something
4. Relaunch max, the Manage Scene States menu button should now show "file missing" or something, this is expected, close max again
5. Move the dlu file back into the folder, and relaunch max
6. If you have our luck the Manage Scene States window will now open! Be warned though, relaunching max it will be gone again
7. In order to preserve the window we found that repeating this process with loading the scene file directly instead of just max itself, then creating a scene state in the temporarily fixed state would mean that future opening on this scene will keep the fixed Scene State button

Hopefully this helps anyone that has run out of options, and maybe lead to a better fix.

Kind Regards

[MMDMedia]

Hi,

Just encountered this issue today with Max 2017. Never had this problem before but it appeared just at the least convenient time, after referring to this thread and many others around we tried nearly every fix including - Remaking ini files, deleting ENU folder, uninstalling renderers, resetting workspaces and UI, running as admin, trying on different users. We're not sure if our problem is the same as others, but we found a workaround so I figured it be worth sharing.

Some explanation of our setup.

• Did have 3Dconnexion mouse briefly installed on this computer years ago, but was uninstalled and corresponding max drivers removed at least a year ago (and scene states had worked since then)
• Never had Vray on this machine (identified as a culprit in other threads)
• Using Corona, Redshift, realflow, and tyflow (possible any of these cause similar issues to Vray, did uninstall Corona and problem persisted)
• User has full local administrator rights
• Scene states have worked on this machine in the past from a fresh max file, only need to use scene states on maybe 5% of projects, so it has been a while since it was used in a new project

We did identify that old scenes that had utilised scene states would correctly open the manager, however old scenes that didn't have scene states would refuse to open it, and of course newly created files would also refuse to open the manager. Interestingly, saving an old scene with the working scene state manager as a new file would retain the working scene state manager.

Here's our workaround after trying everything else. 

1. Close max entirely
2. Locate  C:\Program Files\Autodesk\3ds Max 2017\stdplugs  and find the  SceneStateUtil.dlu  file.
3. Move that file to a safe spot, desktop or something
4. Relaunch max, the Manage Scene States menu button should now show "file missing" or something, this is expected, close max again
5. Move the dlu file back into the folder, and relaunch max
6. If you have our luck the Manage Scene States window will now open! Be warned though, relaunching max it will be gone again
7. In order to preserve the window we found that repeating this process with loading the scene file directly instead of just max itself, then creating a scene state in the temporarily fixed state would mean that future opening on this scene will keep the fixed Scene State button

Hopefully this helps anyone that has run out of options, and maybe lead to a better fix.

Kind Regards