Post #5280: It seems you’ve already conducted a detailed investigation, so you might have an
📋 Metadata
- Author: Pluglug
- Date: 2024-11-19 22:38:28
- Type:
answer - Quality Score: 8/10
- Reply to: post_05278
- Replies (1): post_05282
🏷️ Tags
troubleshooting intermediate solved
⚙️ Related PME Features
- Macro Editor
- Menu Editor
- Custom Icons
💬 Content
It seems you’ve already conducted a detailed investigation, so you might have anticipated this already, but this issue is not caused by PME itself. Instead, it is likely due to the custom menus or macros you are using.
For example, if you create a menu using a Node Wrangler operator in a Blender 4.1 environment, PME will store the identifier node.nw_preview_node. However, keep in mind that this is saved as plain text information. If the NW developers on a whim decide to change the identifier, node.nw_preview_node will no longer be found. As a result, you will have to grumble about it and update it to node.connect_to_output in accordance with the changes.
The EXCEPTION_ACCESS_VIOLATION error indicates that Blender crashed because it attempted to access an invalid memory region. Whether this was caused by PME or the menus created with PME is unclear, but perhaps you could start by rewriting or recreating the outdated commands in your menus.
❤️ 2 likes