Hi everyone,
I’m encountering an issue with Unity’s IMGUI Debugger on Windows, specifically related to Unity’s own internal scripts. When using the IMGUI Debugger, I often see generic method names like “runtime_invoke_void_int_intptr_intptr&” instead of detailed information for Unity’s internal code. This makes it challenging to understand what’s happening within Unity’s processes, especially when debugging editor scripts or custom inspectors.
Interestingly, my friend who uses macOS doesn’t experience this issue—the IMGUI Debugger on their system provides detailed information even for Unity’s internal methods.
Any tips on how to get more detailed insights for Unity’s internal scripts in the IMGUI Debugger on Windows, or if anyone else has encountered this on Windows, would be greatly appreciated.
Thanks in advance!