I just started having the same problem today, which sucks.

it appears many people have been having this problem

i can't reproduce this problem on either the main branch or x86-64, so it doesn't seem like a gmod issue, and it sounds like it started happening half a year after the last update to this tool, so the only remaining explanation i can think of is an addon conflict. does this issue still happen if you disable all other addons?

引用自 no loafing：

i can't reproduce this problem on either the main branch or x86-64, so it doesn't seem like a gmod issue, and it sounds like it started happening half a year after the last update to this tool, so the only remaining explanation i can think of is an addon conflict. does this issue still happen if you disable all other addons?

Ok, so after uninstalling ALL other mods, reinstalling them, and repeating it like 3 times, it now works again, which was both incredibly annoying and relieving at the same time

引用自 Luigi：

引用自 no loafing：

i can't reproduce this problem on either the main branch or x86-64, so it doesn't seem like a gmod issue, and it sounds like it started happening half a year after the last update to this tool, so the only remaining explanation i can think of is an addon conflict. does this issue still happen if you disable all other addons?

Ok, so after uninstalling ALL other mods, reinstalling them, and repeating it like 3 times, it now works again, which was both incredibly annoying and relieving at the same time

I've noticed that if you install the 64-bit version and then switch to the standard version, the add-on becomes obsolete or something like that. I wonder why that happens.