Essential Graphics Panel will not display in current version (24.3 Build 35)

Report · Feb 19, 2024

The essential Graphics Panel will not show een when selecting it from the Window menu...Essential Sounds does display

I have uninstalled this current beta version and installed previous and that worked correctly and does show the Essential Graphics.

Updated again to current beta and issue has returned.

Also on opening a project with Essential Graphics displayed it hangs Premier Pro. After restart of machine it will go in after it resets some workspace settings

Edition Windows 11 Pro
Version 23H2
Installed on ‎16/‎07/‎2023
OS build 22635.3209
Experience Windows Feature Experience Pack 1000.22687.1000.0

Report · Feb 19, 2024

I saw many reports of workspace/UI problems, most leading to crashes or hangs. Some reports just referred to latest version, and at least one build 33. I had just updated to build 33, and the UI just hung as soon as I created a new project. (I used the Shift key open to reset preferences and cache.)

I updated to Build 35, and it is working correctly so far. This includes changing workspaces, creating a transcript and captions, opening the Essential Graphics Panel and editing captions.

If you try Build 35 again, reset preferences and cache and create a new project. See if that works. Then import your old project to a new project.

Or wait for one more Build to post.

Stan

Report · Feb 20, 2024

No, sigue sin solucionarse... increible

Report · Feb 20, 2024

I see multiple reports of issues in Build 35. I see that Build 36 is now available but have not tested it.

As I suggested before, I recommend resetting preferences and cache, creating a new project, and importing your old project.

I tried a simple project from build 33 opened in build 35 and a more complicated one from Build 5, and they both worked correctly.

Such bugs happen from time to time in the Beta. They are usually fixed quickly.

Stan

Report · Feb 20, 2024

Thanks for reporting this issue! The Motion Graphics team believes that this bug is fixed with the latest beta build (24.3x36). It would be immensly helpful to us if you could check if the problem has in fact been resolved on your end.