Join our discord community
Export Attributes in Alembic
No worries ? thanks for fixing it !
So if we want to keep our idea to process several Maya scenes, add some basic object and export it through the State Manager I should use a python process to run Maya and my Prism plugin code in it ? I'm a real newbie in the process/thread topic, I don't even know how I can run a Maya specific process from python... I will look for some details on that but maybe you have a very simple snippet example in mind to begin with ? ?
So as you can see the pop up thing is still faster than creating all the states by hand but be able to bypass that should save us even more time (there is only 6 assets for now so in a real production it will be very heavy to deal with...) ! If you have a solution in mind or even planned to work on that let us know 🙂
Quote from Augu on 16. July 2019, 9:20I should use a python process to run Maya and my Prism plugin code in it ?
You can execute your code a plugin in Prism standalone (which is a usual python process). This plugin would use the subprocess python module to launch the Maya executable. You would pass some python code to that process, which gets executed once maya has launched. That would be the example code from my previous post. You can launch the default Maya executable or the mayapy.exe, which would be preferred if you don't want user interaction. Maybe this example gives you an idea how to start this process: http://techartsurvival.blogspot.com/2014/05/what-happens-at-startup.html
You need to import PySide2 and construct a QApplication in order for Prism to run in mayapy. Here is an example with Pandora, but it should work similar with Prism: https://github.com/RichardFrangenberg/Pandora/issues/5
Great video, very nice to see what you plan to do 🙂
When you use mayapy Prism already recognizes that and doesn't show the publish and framerate dialogs (the import dialog would be still there at the moment). But I can add an option to suppress Prism dialogs even if you run Prism in a Maya UI. For the import dialog: Instead of letting your python script interact with the import dialog, I would prefer to add an option to specify the import settings in your python command. And if these settings are provided then Prism shouldn't even open the dialog. I'll look into that soon.