-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rendering Image Sequence with 'Maximized Area' display replaces current interface #78
Comments
Hi @ilcane87, thank you for your detailed report, I really appreciate that. I can confirm this issue and working on it. In the worst case, we have to remove the 'Maximized Area' option or recreate the entire workspace because Blender seems to lose the reference to the previously used workspace when rendering more than one frame. Is Blenders 'Maximized Area' feature something you use on a daily basis? Cheers, |
I think that's the default behavior? That or I somehow got used to it when I started with Blender, so I've been sticking with it ever since, but honestly it's just habit, I could live without it if I had to. |
Hi @ilcane87, thanks for your feedback.
The default is 'New Window', I think I would have noticed this issue sooner otherwise.
I keep getting crashes when I try to load or even store the previous workspace while rendering, so yeah, I don't see a better option at the moment than to remove the item from the list: I hope you can live with it for now. If I see a good way to support "maximized area" in the future, I will look into it immediately and let you know. If you have the time, please clone or download Loom from the master branch and report back. Cheers, |
Tested it and everything works as expected, thanks a lot for the quick fix! |
Hi @ilcane87, great, thank you for testing the patch. Closing for now, can be reopened at any time. Cheers, |
Hello, I assume this isn't intended behavior, but when I render a couple frames with Render Image Sequence with 'Maximized Area' option selected, instead of just overlaying the rendering area over the current interface, it also overwrites the interface itself with another maximized area, so the original interface is lost.
This behavior is unaffected by the 'Lock Interface' setting.
What happens when normally rendering with Maximized Area is that after the rendering is done, you can close the overlayed area and go back to the original interface.
Running version 0.9.1 of the addon on Blender 3.5.0 (Windows 10).
The text was updated successfully, but these errors were encountered: